diff options
| author | Paul Walmsley <paul@pwsan.com> | 2010-12-21 15:30:56 -0700 |
|---|---|---|
| committer | Paul Walmsley <paul@pwsan.com> | 2010-12-21 20:56:50 -0700 |
| commit | f0611a5c220e50dec65041b10bd2fe9484f061a6 (patch) | |
| tree | f94ba2787f721a38ad57d22638c5561318d31f26 /arch/arm/mach-omap2/prm2xxx_3xxx.c | |
| parent | 59fb659b065f52fcc2deed293cfbfc58f890376c (diff) | |
| download | linux-f0611a5c220e50dec65041b10bd2fe9484f061a6.tar.gz linux-f0611a5c220e50dec65041b10bd2fe9484f061a6.tar.bz2 linux-f0611a5c220e50dec65041b10bd2fe9484f061a6.zip | |
OMAP3: PRM/CM: separate CM context save/restore; remove PRM context save/restore
The OMAP3 PRM module is in the WKUP powerdomain, which is always
powered when the chip is powered, so it shouldn't be necessary to save
and restore those PRM registers. Remove the PRM register save/restore
code, which should save several microseconds during off-mode
entry/exit, since PRM register accesses are relatively slow.
While doing so, move the CM register save/restore code into
CM-specific code. The CM module has been distinct from the PRM module
since 2430.
This patch includes some minor changes to pm34xx.c.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Tero Kristo <tero.kristo@nokia.com>
Cc: Kalle Jokiniemi <kalle.jokiniemi@digia.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/prm2xxx_3xxx.c')
| -rw-r--r-- | arch/arm/mach-omap2/prm2xxx_3xxx.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/mach-omap2/prm2xxx_3xxx.c b/arch/arm/mach-omap2/prm2xxx_3xxx.c index 064b52a3e202..3e1d36c83fc4 100644 --- a/arch/arm/mach-omap2/prm2xxx_3xxx.c +++ b/arch/arm/mach-omap2/prm2xxx_3xxx.c @@ -154,4 +154,3 @@ int omap2_prm_deassert_hardreset(s16 prm_mod, u8 shift) return (c == MAX_MODULE_HARDRESET_WAIT) ? -EBUSY : 0; } - |