Message ID | 1309338303-2086-8-git-send-email-t-kristo@ti.com (mailing list archive) |
---|---|
State | Changes Requested |
Delegated to: | Kevin Hilman |
Headers | show |
Tero Kristo <t-kristo@ti.com> writes: > PRCM chain interrupt registration is done now as part of > omap_hwmod_enable_wakeup() and omap_hwmod_disable_wakeup() calls. This > allows module ISR:s to be called when the module is idle but an IO_PAD > event is detected on the module input pads. These functions are the enable/disable for module-level wakeups, you need to use the proposed enable/disable functions for IO ring wakeups as proposed in the patch from Govindraj[1]. I'm hoping that patch will be queued for v3.1, but will wait for Paul's comments on that patch. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, Jul 2, 2011 at 3:48 AM, Kevin Hilman <khilman@ti.com> wrote: > Tero Kristo <t-kristo@ti.com> writes: > >> PRCM chain interrupt registration is done now as part of >> omap_hwmod_enable_wakeup() and omap_hwmod_disable_wakeup() calls. This >> allows module ISR:s to be called when the module is idle but an IO_PAD >> event is detected on the module input pads. > > These functions are the enable/disable for module-level wakeups, you > need to use the proposed enable/disable functions for IO ring wakeups as > proposed in the patch from Govindraj[1]. > Posted a new version rebased on 3.0-rc5 https://patchwork.kernel.org/patch/940332/ https://patchwork.kernel.org/patch/940322/ -- Thanks, Govindraj.R > I'm hoping that patch will be queued for v3.1, but will wait for Paul's > comments on that patch. > > Kevin > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c index 293fa6c..f12fe89 100644 --- a/arch/arm/mach-omap2/omap_hwmod.c +++ b/arch/arm/mach-omap2/omap_hwmod.c @@ -2123,6 +2123,7 @@ int omap_hwmod_enable_wakeup(struct omap_hwmod *oh) v = oh->_sysc_cache; _enable_wakeup(oh, &v); _write_sysconfig(v, oh); + omap_prcm_register_pad_irqs(oh->mux, oh->mpu_irqs[0].irq); spin_unlock_irqrestore(&oh->_lock, flags); return 0; @@ -2153,6 +2154,7 @@ int omap_hwmod_disable_wakeup(struct omap_hwmod *oh) v = oh->_sysc_cache; _disable_wakeup(oh, &v); _write_sysconfig(v, oh); + omap_prcm_unregister_pad_irqs(oh->mux); spin_unlock_irqrestore(&oh->_lock, flags); return 0;
PRCM chain interrupt registration is done now as part of omap_hwmod_enable_wakeup() and omap_hwmod_disable_wakeup() calls. This allows module ISR:s to be called when the module is idle but an IO_PAD event is detected on the module input pads. Signed-off-by: Tero Kristo <t-kristo@ti.com> --- arch/arm/mach-omap2/omap_hwmod.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)