Re: [PATCH v2] iio: adc: bcm_iproc_adc: swap primary and secondary isr handler's

On 16/05/17 07:52, Raveendra Padasalagi wrote: The third argument of devm_request_threaded_irq() is the primary handler. It is called in hardirq context and checks whether the interrupt is relevant to the device. If the primary handler returns IRQ_WAKE_THREAD, the secondary handler (a.k.a.

Re: [PATCH v2] iio: adc: bcm_iproc_adc: swap primary and secondary isr handler's

On 16/05/17 07:52, Raveendra Padasalagi wrote: The third argument of devm_request_threaded_irq() is the primary handler. It is called in hardirq context and checks whether the interrupt is relevant to the device. If the primary handler returns IRQ_WAKE_THREAD, the secondary handler (a.k.a.

[PATCH v2] iio: adc: bcm_iproc_adc: swap primary and secondary isr handler's

The third argument of devm_request_threaded_irq() is the primary handler. It is called in hardirq context and checks whether the interrupt is relevant to the device. If the primary handler returns IRQ_WAKE_THREAD, the secondary handler (a.k.a. handler thread) is scheduled to run in process

[PATCH v2] iio: adc: bcm_iproc_adc: swap primary and secondary isr handler's

The third argument of devm_request_threaded_irq() is the primary handler. It is called in hardirq context and checks whether the interrupt is relevant to the device. If the primary handler returns IRQ_WAKE_THREAD, the secondary handler (a.k.a. handler thread) is scheduled to run in process