author | Rajendra Nayak <rnayak@ti.com> | |
Mon, 18 Feb 2013 10:34:27 +0000 (16:04 +0530) | ||
committer | Santosh Shilimkar <santosh.shilimkar@ti.com> | |
Mon, 25 Feb 2013 12:02:06 +0000 (17:32 +0530) | ||
commit | a18d55e36da863be5f44748366fab115bc489661 | |
tree | aba9b4ecfd6b4a09d4f89a608f42d98c589cf96a | tree | snapshot (tar.xz tar.gz zip) |
parent | 66898adc54d04978f9cbdd0ca407164ebec8d6dc | commit | diff |
ARM: OMAP2+: hwmod: Always have OCP_SYSCONFIG.ENAWAKEUP enabled
Get rid of all complexities around when to enable OCP_SYSCONFIG.ENAWAKEUP.
It should be safe to have this set *always* for all IP blocks which
have this control. It should be a *dont care* when the IP is in
NO/FORCE modes of sidle/mstandby. As for the SMART/SMART_WKUP modes
of sidle/mstandby the framework anyway sets this always.
Tested-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
Tested-by: Sourav Poddar <sourav.poddar@ti.com>
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Get rid of all complexities around when to enable OCP_SYSCONFIG.ENAWAKEUP.
It should be safe to have this set *always* for all IP blocks which
have this control. It should be a *dont care* when the IP is in
NO/FORCE modes of sidle/mstandby. As for the SMART/SMART_WKUP modes
of sidle/mstandby the framework anyway sets this always.
Tested-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
Tested-by: Sourav Poddar <sourav.poddar@ti.com>
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
arch/arm/mach-omap2/omap_hwmod.c | diff | blob | history |