linux-kernel - Re: [RFC] gpio: about the need to manage irq mapping dynamically.

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdar9YwnMgLb1y1sP1Vbg-1MgPAOcRPcfNCtmpKuf+g+kQ@mail.gmail.com>
Date:   Thu, 29 Jun 2017 16:16:51 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Grygorii Strashko <grygorii.strashko@...com>
Cc:     Jerome Brunet <jbrunet@...libre.com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        Marc Zyngier <marc.zyngier@....com>,
        "open list:ARM/Amlogic Meson..." <linux-amlogic@...ts.infradead.org>,
        Kevin Hilman <khilman@...libre.com>,
        Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] gpio: about the need to manage irq mapping dynamically.

On Tue, Jun 27, 2017 at 10:43 PM, Grygorii Strashko
<grygorii.strashko@...com> wrote:

> And my opinion is still the same here - It should be perfectly valid to create
> mappings from gpio_to_irq() to handle properly orthogonality of gpiochip and
> gpio-irqchip functionality and satisfy SPARSE_IRQ goal (allocate Linux virq and
> irq descriptors on demand).

You are right.

I would rather say: GPIO drivers that have a 1-to-1 mapping between GPIO
lines and IRQs should not do it, they should map up them all at probe().

Drivers that actually have fewer IRQs than GPIO lines should be able to
create the mappings in gpio_to_irq().

Yours,
Linus Walleij