diff options
| author | Kevin Hilman <khilman@ti.com> | 2011-06-02 17:28:13 -0700 |
|---|---|---|
| committer | Kevin Hilman <khilman@ti.com> | 2011-09-15 12:08:58 -0700 |
| commit | 8abc0b58fdb89124d8278f110f523b27c666d36c (patch) | |
| tree | 7f48f3ab775b32adb21f1a1941fdeb18bd0e23e8 /security | |
| parent | f5395480f5088a86cc8594d29b5c2f07f6995c3d (diff) | |
| download | linux-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 'security')
0 files changed, 0 insertions, 0 deletions