lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 2 Jun 2019 15:51:51 +0200
From:   Linus Walleij <>
To:     Thierry Reding <>
Cc:     Thomas Gleixner <>,
        Lina Iyer <>,
        Jon Hunter <>,
        Sowjanya Komatineni <>,
        Bitan Biswas <>,
        "open list:GPIO SUBSYSTEM" <>,,
        "" <>
Subject: Re: [PATCH v3 1/2] gpio: Add support for hierarchical IRQ domains

On Wed, May 29, 2019 at 4:53 PM Thierry Reding <> wrote:

> From: Thierry Reding <>
> 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 <>
> ---
> 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.

Linus Walleij

Powered by blists - more mailing lists