summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/vc.h
diff options
context:
space:
mode:
authorKevin Hilman <khilman@ti.com>2011-06-02 17:28:13 -0700
committerKevin Hilman <khilman@ti.com>2011-09-15 12:08:58 -0700
commit8abc0b58fdb89124d8278f110f523b27c666d36c (patch)
tree7f48f3ab775b32adb21f1a1941fdeb18bd0e23e8 /arch/arm/mach-omap2/vc.h
parentf5395480f5088a86cc8594d29b5c2f07f6995c3d (diff)
downloadlinux-8abc0b58fdb89124d8278f110f523b27c666d36c.tar.gz
linux-8abc0b58fdb89124d8278f110f523b27c666d36c.tar.bz2
linux-8abc0b58fdb89124d8278f110f523b27c666d36c.zip
OMAP3+: PM: VC: handle mutant channel config for OMAP4 MPU channel
On OMAP3+, all VC channels have the the same bitfield ordering for all VC channels, except the OMAP4 MPU channel. This appears to be a freak accident as all other VC channel (including OMAP5) have the standard configuration. Handle the mutant case by adding a per-channel flag to signal the deformity and handle it during VC init. Special thanks to Nishanth Menon <nm@ti.com> for finding this problem and for proposing the initial solution. Cc: Nishanth Menon <nm@ti.com> Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'arch/arm/mach-omap2/vc.h')
-rw-r--r--arch/arm/mach-omap2/vc.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/mach-omap2/vc.h b/arch/arm/mach-omap2/vc.h
index c86301330b75..7ed70e07becf 100644
--- a/arch/arm/mach-omap2/vc.h
+++ b/arch/arm/mach-omap2/vc.h
@@ -66,6 +66,7 @@ struct omap_vc_common {
/* omap_vc_channel.flags values */
#define OMAP_VC_CHANNEL_DEFAULT BIT(0)
+#define OMAP_VC_CHANNEL_CFG_MUTANT BIT(1)
/**
* struct omap_vc_channel - VC per-instance data