OMAP3+: PM: VC: handle mutant channel config for OMAP4 MPU channel

Browse source

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>

...

This commit is contained in:

Kevin Hilman 2011-06-02 17:28:13 -07:00

parent f5395480f5

commit 8abc0b58fd

3 changed files with 53 additions and 14 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

64

arch/arm/mach-omap2/vc.c

View file

1

arch/arm/mach-omap2/vc.h

View file

2

arch/arm/mach-omap2/vc44xx_data.c

View file