summaryrefslogtreecommitdiffstats
path: root/drivers/base
diff options
context:
space:
mode:
authorMagnus Damm <damm@opensource.se>2011-07-10 10:39:32 +0200
committerRafael J. Wysocki <rjw@sisk.pl>2011-07-10 10:39:32 +0200
commit775b8ae8707592af9275b8b216c2bf056b3f5d82 (patch)
tree45547ece2b4012199e1a51f4cde3f9de640398fc /drivers/base
parent18b4f3f5d058b590e7189027eeb5d897742ade0a (diff)
downloadop-kernel-dev-775b8ae8707592af9275b8b216c2bf056b3f5d82.zip
op-kernel-dev-775b8ae8707592af9275b8b216c2bf056b3f5d82.tar.gz
ARM: mach-shmobile: sh7372 A3RV requires A4LC
Add a power domain workaround for the VPU and A3RV on sh7372. The sh7372 data sheet mentions that the VPU is located in the A3RV power domain. The A3RV power domain is not related to A4LC in any way, but testing shows that unless A3RV _and_ A4LC are powered on the VPU test program will bomb out. This issue may be caused by a more or less undocumented dependency on the MERAM block that happens to be located in A4LC. So now we know that the out-of-reset requirement of the VPU is that the MERAM is powered on. This patch adds a workaround for A3RV to make sure A4LC is powered on - this so we can use the VPU even though the LCDCs are in blanking state and A4LC is supposed to be off. Signed-off-by: Magnus Damm <damm@opensource.se> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud