summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c
diff options
context:
space:
mode:
authorPaul Walmsley <paul@pwsan.com>2010-12-21 23:30:53 +0100
committerPaul Walmsley <paul@pwsan.com>2010-12-22 04:01:53 +0100
commitf5f9d132d1c212bf3828c7926d95f79e0c20d243 (patch)
tree979937fd6eeb58a5599bf5b1222d81c6ba6e3f3d /arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c
parentOMAP3: control/PRCM: add omap3_ctrl_write_boot_mode() (diff)
downloadlinux-f5f9d132d1c212bf3828c7926d95f79e0c20d243.tar.xz
linux-f5f9d132d1c212bf3828c7926d95f79e0c20d243.zip
OMAP3: control/PRCM: move CONTROL_PADCONF_SYS_NIRQ save/restore to SCM code
For some reason, the PRCM context save/restore code also saves and restores a single System Control Module register, CONTROL_PADCONF_SYS_NIRQ. This is probably just an error -- the register should be handled by SCM code -- so this patch moves it there. If this register really does need to be saved and restored before the rest of the PRCM registers, the code to do so should live in the SCM code, and the PM code should call this separate function. This register pertains to devices with a stacked modem, so this patch is unlikely to affect most OMAP devices out there. Signed-off-by: Paul Walmsley <paul@pwsan.com> Cc: Kevin Hilman <khilman@deeprootsystems.com> Reviewed-by: Kevin Hilman <khilman@deeprootsystems.com> Tested-by: Kevin Hilman <khilman@deeprootsystems.com> Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Tested-by: Rajendra Nayak <rnayak@ti.com>
Diffstat (limited to 'arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c')
0 files changed, 0 insertions, 0 deletions