diff options
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2011-11-08 03:16:10 -0700 |
|---|---|---|
| committer | Paul Walmsley <paul@pwsan.com> | 2011-11-08 03:16:10 -0700 |
| commit | 8c3105ca1a42783b13930fbd375484ec8c72e608 (patch) | |
| tree | c677d30a8d41f8d8dec0867353b859359006c587 /scripts/Kbuild.include | |
| parent | b8ac10d8b75843c9ddd6aadf70a0cdf8aa783659 (diff) | |
| download | kernel_samsung_smdk4412-8c3105ca1a42783b13930fbd375484ec8c72e608.zip kernel_samsung_smdk4412-8c3105ca1a42783b13930fbd375484ec8c72e608.tar.gz kernel_samsung_smdk4412-8c3105ca1a42783b13930fbd375484ec8c72e608.tar.bz2 | |
ARM: OMAP3: HWMOD: Fix DSS reset
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 hasn't caused any problems so far, but
we may just have been lucky.
dss_core's opt-clocks is also missing dss_96m_fck, which is a DSS clock
present only on OMAP3430, and thus required on OMAP3430 to finish the
reset.
This patch sets HWMOD_CONTROL_OPT_CLKS_IN_RESET and adds the dss_96m_fck
opt-clock for dss_core in OMAP3 HWMOD data, fixing the issue.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
[paul@pwsan.com: merged duplicate .flags fields]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Diffstat (limited to 'scripts/Kbuild.include')
0 files changed, 0 insertions, 0 deletions