summaryrefslogtreecommitdiff
path: root/arch/ia64
diff options
context:
space:
mode:
authorKevin Hilman <khilman@ti.com>2011-03-30 02:57:16 +0400
committerKevin Hilman <khilman@ti.com>2011-09-15 23:08:57 +0400
commit24d3194a2c9bc4d2315117915d4d22c395c07fd5 (patch)
treed7a5848a3b67f8288fc974bb0b0eab6dacb7ea97 /arch/ia64
parent08d1c9a3e2dc7a285db7c689c42963d0f5271c1f (diff)
downloadlinux-24d3194a2c9bc4d2315117915d4d22c395c07fd5.tar.xz
OMAP3+: VC: abstract out channel configuration
VC channel configuration is programmed based on settings coming from the PMIC configuration. Currently, the VC channel to PMIC mapping is a simple one-to-one mapping. Whenever a VC channel parameter is configured (i2c slave addres, PMIC register address, on/ret/off command), the corresponding bits are enabled in the VC channel configuration register. If necessary, the programmability of channel configuration settings could be extended to board/PMIC files, however, because this patch changes the channel configuration to be programmed based on existing values from the PMIC settings, it may not be required. Also note that starting with OMAP4, where there are more than 2 channels, one channel is identified as the "default" channel. When any of the bits in the channel config for the other channels are zero, it means to use the default channel. The OMAP4 TRM (at least through NDA version Q) is wrong in describing which is the default channel. The default channel on OMAP4 is MPU, not CORE as decribed in the TRM. Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'arch/ia64')
0 files changed, 0 insertions, 0 deletions