| Message ID | 1573756521-27373-2-git-send-email-ilina@codeaurora.org (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Support wakeup capable GPIOs | expand |
Quoting Lina Iyer (2019-11-14 10:35:10) > A single controller can handle normal interrupts and wake-up interrupts > independently, with a different numbering space. It is thus crucial to > allow the driver for such a controller discriminate between the two. > > A simple way to do so is to tag the wake-up irqdomain with a "bus token" > that indicates the wake-up domain. This slightly abuses the notion of > bus, but also radically simplifies the design of such a driver. Between > two evils, we choose the least damaging. > > Suggested-by: Stephen Boyd <swboyd@chromium.org> > Signed-off-by: Lina Iyer <ilina@codeaurora.org> > --- Reviewed-by: Stephen Boyd <swboyd@chromium.org>
diff --git a/include/linux/irqdomain.h b/include/linux/irqdomain.h index 583e7ab..3c340db 100644 --- a/include/linux/irqdomain.h +++ b/include/linux/irqdomain.h @@ -83,6 +83,7 @@ enum irq_domain_bus_token { DOMAIN_BUS_IPI, DOMAIN_BUS_FSL_MC_MSI, DOMAIN_BUS_TI_SCI_INTA_MSI, + DOMAIN_BUS_WAKEUP, }; /**
A single controller can handle normal interrupts and wake-up interrupts independently, with a different numbering space. It is thus crucial to allow the driver for such a controller discriminate between the two. A simple way to do so is to tag the wake-up irqdomain with a "bus token" that indicates the wake-up domain. This slightly abuses the notion of bus, but also radically simplifies the design of such a driver. Between two evils, we choose the least damaging. Suggested-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Lina Iyer <ilina@codeaurora.org> --- include/linux/irqdomain.h | 1 + 1 file changed, 1 insertion(+)