linux-kernel - Re: [PATCH v2 0/3] pinctrl / gpio: Allow GPIO chips to use generic pinconfig

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]

Date:   Thu, 26 Jan 2017 15:25:05 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     Alexandre Courbot <gnurou@...il.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Neil Armstrong <narmstrong@...libre.com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] pinctrl / gpio: Allow GPIO chips to use generic pinconfig

On Mon, Jan 23, 2017 at 1:34 PM, Mika Westerberg
<mika.westerberg@...ux.intel.com> wrote:

> This series makes it possible to configure pins from GPIO chip drivers by
> implementing a new callback .set_config(). This callback replaces the
> existing .set_single_ended() and .set_debounce() simply because adding new
> callbacks for each possible configuration type does not scale. So instead
> we re-use the existing generic pinconf types and the packed format.
>
> This is a follow up of discussion on:
>
>   https://patchwork.ozlabs.org/patch/713289/

As you already know I'm a big fan of the series.

I applied the two patches to an immutable branch in the pin control
tree and pulled it into both pin control and GPIO devel branches.

Thanks a lot for your efforts!!

Yours,
Linus Walleij