linux-kernel - Re: [PATCH] pinctrl: at91: don't use the same irqchip with multiple gpiochips

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] [day] [month] [year] [list]

Message-ID: <CACRpkdZWoZ1YCP9eJbB0BgfgON=Zf8q4w=OV4w2nRxvkcd6VaQ@mail.gmail.com>
Date:   Fri, 14 Sep 2018 10:59:47 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Ludovic Desroches <ludovic.desroches@...rochip.com>
Cc:     Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
        Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [PATCH] pinctrl: at91: don't use the same irqchip with multiple gpiochips

On Thu, Sep 13, 2018 at 2:46 PM Ludovic Desroches
<ludovic.desroches@...rochip.com> wrote:

> Sharing the same irqchip with multiple gpiochips is not a good
> practice. For instance, when installing hooks, we change the state
> of the irqchip. The initial state of the irqchip for the second
> gpiochip to register is then disrupted.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@...rochip.com>

Patch applied.

Yours,
Linus Walleij