ARM: OMAP4: HWMOD: Add HWMOD_CONTROL_OPT_CLKS_IN_RESET for dss_core
DSS needs all DSS clocks to be enabled to be able to finish reset properly. Before v3.1-rc1 the omapdss driver was managing clocks and resets correctly. However, when omapdss started using runtime PM at v3.1-rc1, the responsibility for the reset moved to HWMOD framework. HWMOD framework does not currently enable all the DSS clocks when resetting the DSS hardware. This causes the HWMOD frameworks boot-time reset to fail, possibly leaving the DSS hardware in undefined state. This patch sets HWMOD_CONTROL_OPT_CLKS_IN_RESET for dss_core. The flag is actually not used on OMAP4, because dss_core hardware does not have soft-reset functionality and thus the HWMOD framework never resets nor waits for the reset to finish. However, while the flag is not strictly needed currently, I think it represents the HW correctly: all the DSS clocks should be enabled after power-on to allow DSS hardware to finish its reset. A custom reset function will be added in the following patches which manages this correctly for OMAP4. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Signed-off-by: Paul Walmsley <paul@pwsan.com>
This commit is contained in:
parent
4247878efc
commit
37ad085527
|
@ -1245,6 +1245,7 @@ static struct omap_hwmod_opt_clk dss_opt_clks[] = {
|
||||||
|
|
||||||
static struct omap_hwmod omap44xx_dss_hwmod = {
|
static struct omap_hwmod omap44xx_dss_hwmod = {
|
||||||
.name = "dss_core",
|
.name = "dss_core",
|
||||||
|
.flags = HWMOD_CONTROL_OPT_CLKS_IN_RESET,
|
||||||
.class = &omap44xx_dss_hwmod_class,
|
.class = &omap44xx_dss_hwmod_class,
|
||||||
.clkdm_name = "l3_dss_clkdm",
|
.clkdm_name = "l3_dss_clkdm",
|
||||||
.main_clk = "dss_dss_clk",
|
.main_clk = "dss_dss_clk",
|
||||||
|
|
Loading…
Reference in New Issue