On Sun, Jun 02, 2019 at 10:35:22PM +0200, Linus Walleij wrote: > On Sun, Jun 2, 2019 at 3:51 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > > On Wed, May 29, 2019 at 4:53 PM Thierry Reding <thierry.reding@xxxxxxxxx> wrote: > > > > > From: Thierry Reding <treding@xxxxxxxxxx> > > > > > > Hierarchical IRQ domains can be used to stack different IRQ controllers > > > on top of each other. One specific use-case where this can be useful is > > > if a power management controller has top-level controls for wakeup > > > interrupts. In such cases, the power management controller can be a > > > parent to other interrupt controllers and program additional registers > > > when an IRQ has its wake capability enabled or disabled. > > > > > > Signed-off-by: Thierry Reding <treding@xxxxxxxxxx> > > > --- > > > Changes in v3: > > > - use irq_create_fwspec_mapping() instead of irq_domain_alloc_irqs() > > > - add missing kerneldoc for new parent_domain field > > > - keep IRQ_DOMAIN dependency for clarity > > > > Actually I applied the patch, and dropped the two lines making > > it possible to override .to_irq() for now, so I can illustrate my > > idea on top. If I manage. > > Bah I rewrote the whole think as I want it, maybe my ideas are stupid > but take a look at it, also very interested in input from the irqchip > maintainers. > > Sending it out as RFC in a moment. Okay, taking a look. Thierry
Attachment:
signature.asc
Description: PGP signature
