Re: [PATCH V1 09/15] spmi: pmic-arb: check apid enabled before calling the handler

2017-06-20 Thread kgunda
On 2017-06-17 02:41, Stephen Boyd wrote: On 06/14, kgu...@codeaurora.org wrote: On 2017-06-01 02:09, Stephen Boyd wrote: >On 05/30, Kiran Gunda wrote: >>From: Abhijeet Dharmapurikar >> >>The driver currently invokes the apid handler (periph_handler()) > >You mean periph_interrupt()? > Yes. >>on

Re: [PATCH V1 09/15] spmi: pmic-arb: check apid enabled before calling the handler

2017-06-16 Thread Stephen Boyd
On 06/14, kgu...@codeaurora.org wrote: > On 2017-06-01 02:09, Stephen Boyd wrote: > >On 05/30, Kiran Gunda wrote: > >>From: Abhijeet Dharmapurikar > >> > >>The driver currently invokes the apid handler (periph_handler()) > > > >You mean periph_interrupt()? > > > Yes. > >>once it sees that the summ

Re: [PATCH V1 09/15] spmi: pmic-arb: check apid enabled before calling the handler

2017-06-14 Thread kgunda
On 2017-06-01 02:09, Stephen Boyd wrote: On 05/30, Kiran Gunda wrote: From: Abhijeet Dharmapurikar The driver currently invokes the apid handler (periph_handler()) You mean periph_interrupt()? Yes. once it sees that the summary status bit for that apid is set. However the hardware is des

Re: [PATCH V1 09/15] spmi: pmic-arb: check apid enabled before calling the handler

2017-05-31 Thread Stephen Boyd
On 05/30, Kiran Gunda wrote: > From: Abhijeet Dharmapurikar > > The driver currently invokes the apid handler (periph_handler()) You mean periph_interrupt()? > once it sees that the summary status bit for that apid is set. > > However the hardware is designed to set that bit even if the apid >