linux-kernel - Re: [PATCH v7 00/15] gpio: Tight IRQ chip integration

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: <CACRpkdbL2vz-Qj4yHK7Eado0914CjeEV+Fep9PFW5RpBfEYsvQ@mail.gmail.com>
Date:   Wed, 8 Nov 2017 14:30:22 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Thierry Reding <thierry.reding@...il.com>
Cc:     Grygorii Strashko <grygorii.strashko@...com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7 00/15] gpio: Tight IRQ chip integration

On Tue, Nov 7, 2017 at 7:15 PM, Thierry Reding <thierry.reding@...il.com> wrote:

> here's the latest series of patches that implement the tighter IRQ chip
> integration. I've dropped the banked infrastructure for now as per the
> discussion with Grygorii.
>
> The first couple of patches are mostly preparatory work in order to
> consolidate all IRQ chip related fields in a new structure and create
> the base functionality for adding IRQ chips.
>
> After that, I've added the Tegra186 GPIO support patch that makes use of
> the new tight integration.
>
> Changes in v7:
> - squashes in a few fixes pointed out by Grygorii
> - adds a couple of patches on top to support driver conversion

I put it on a separate branch in the GPIO tree (gpio-irqchip-rework)
then pulled that into the devel branch of both GPIO and
pin control. That should do it.

If there are compile bugs, we shake them out now, then we
stabilize this into v4.15.

THANKS A LOT MAN, this was really walking the extra mile for
the GPIO subsystem so it is much, much appreciated. I hope
this will be the silver bullet that make it possible to consolidate
and manage the "banked GPIO" controllers going forward so
I don't have to go crazy as maintainer.

Also thanks to Grygorii for reviewing and fixing stuff.

I hope we can switch a bunch of other drivers over to using
the banked IRQ infrastructure for v4.16.

Yours,
Linus Walleij