Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-22 Thread Kevin Hilman
Tero Kristo t-kri...@ti.com writes: Introduce a chained interrupt handler mechanism for the PRCM interrupt, so that individual PRCM event can cleanly be handled by handlers in separate drivers. We do this by introducing PRCM event names, which are then matched to the particular PRCM interrupt

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-22 Thread Felipe Balbi
Hi, On Fri, Jul 22, 2011 at 03:58:26PM -0700, Kevin Hilman wrote: [snip] -static irqreturn_t prcm_interrupt_handler (int irq, void *dev_id) -{ - u32 irqenable_mpu, irqstatus_mpu; - int c = 0; - - irqenable_mpu = omap2_prm_read_mod_reg(OCP_MOD, -

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-18 Thread Tero Kristo
On Fri, 2011-07-15 at 18:40 +0200, Todd Poynor wrote: On Tue, Jul 05, 2011 at 01:27:47PM +0300, Tero Kristo wrote: Introduce a chained interrupt handler mechanism for the PRCM interrupt, so that individual PRCM event can cleanly be handled by handlers in separate drivers. We do this by

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-15 Thread Govindraj
On Tue, Jul 5, 2011 at 3:57 PM, Tero Kristo t-kri...@ti.com wrote: Introduce a chained interrupt handler mechanism for the PRCM interrupt, so that individual PRCM event can cleanly be handled by handlers in separate drivers. We do this by introducing PRCM event names, which are then matched to

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-15 Thread Todd Poynor
On Tue, Jul 05, 2011 at 01:27:47PM +0300, Tero Kristo wrote: Introduce a chained interrupt handler mechanism for the PRCM interrupt, so that individual PRCM event can cleanly be handled by handlers in separate drivers. We do this by introducing PRCM event names, which are then matched to the

[PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-05 Thread Tero Kristo
Introduce a chained interrupt handler mechanism for the PRCM interrupt, so that individual PRCM event can cleanly be handled by handlers in separate drivers. We do this by introducing PRCM event names, which are then matched to the particular PRCM interrupt bit depending on the specific OMAP SoC

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-05 Thread Felipe Balbi
Hi, On Tue, Jul 05, 2011 at 01:27:47PM +0300, Tero Kristo wrote: @@ -854,20 +802,35 @@ static int __init omap3_pm_init(void) /* XXX prcm_setup_regs needs to be before enabling hw * supervised mode for powerdomains */ prcm_setup_regs(); + ret = omap_prcm_irq_init(); +

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-05 Thread Tero Kristo
On Tue, 2011-07-05 at 13:18 +0200, Balbi, Felipe wrote: Hi, On Tue, Jul 05, 2011 at 01:27:47PM +0300, Tero Kristo wrote: @@ -854,20 +802,35 @@ static int __init omap3_pm_init(void) /* XXX prcm_setup_regs needs to be before enabling hw * supervised mode for powerdomains */

Re: [PATCHv5 01/11] OMAP: prcm: switch to a chained IRQ handler mechanism

2011-07-05 Thread Felipe Balbi
On Tue, Jul 05, 2011 at 02:32:18PM +0300, Tero Kristo wrote: On Tue, 2011-07-05 at 13:18 +0200, Balbi, Felipe wrote: Hi, On Tue, Jul 05, 2011 at 01:27:47PM +0300, Tero Kristo wrote: @@ -854,20 +802,35 @@ static int __init omap3_pm_init(void) /* XXX prcm_setup_regs needs to be