On Thu, Aug 06, 2020 at 12:20:52PM +0200, Thomas Gleixner wrote: > Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> writes: > > On Tue, Aug 04, 2020 at 11:16:03AM +0200, Ahmad Fatoum wrote: > >> Generic GPIO consumers like gpio-keys use request_any_context_irq() > >> to request a threaded handler if irq_settings_is_nested_thread() == > >> true or a hardirq handler otherwise. > >> > >> Drivers using handle_nested_irq() must be sure that the nested > >> IRQs were requested with threaded handlers, because the IRQ > >> is handled by calling action->thread_fn(). > >> > >> The gpio-siox driver dispatches IRQs via handle_nested_irq, > >> but has irq_settings_is_nested_thread() == false. > >> > >> Set gpio_irq_chip::threaded to remedy this. > > > > Sounds reasonable, but I have to keep this for others to judge if this > > is indeed how the irq stuff works. > > handle_nested_irq() documentation clearly says: "Handle a nested irq > from a irq thread". As a consequence the caller of this function must > run in an interrupt thread. This is an optimization to spare tons of > interrupt threads and context switches. > > So the solution for this driver is either to make the dispatch handler > threaded or use the hard interrupt variant of dispatching the > demultiplexed GPIO interrupts. The action item isn't entirely clear for me. There is no "parent" irq, I have for siox a kthread that does some IO and looks that the resulting data which effectively reports the current state of the GPIO line. And if this GPIO is configured to trigger an irq and the matching transition (or state) is seen, I want to trigger the irq action. So the caller has neither hard nor threaded irq context. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
Attachment:
signature.asc
Description: PGP signature
