linux-kernel - Re: [PATCH v2] pinctrl: generic: Add output-enable property

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: <CAHp75VdAM2EWXtZfaBZ4U2eXL0oj82ipWQZier18jX93xhdUYQ@mail.gmail.com>
Date:   Thu, 29 Jun 2017 17:26:33 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Jacopo Mondi <jacopo+renesas@...ndi.org>,
        Dong Aisheng <dongas86@...il.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Chris Brandt <Chris.Brandt@...esas.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] pinctrl: generic: Add output-enable property

On Thu, Jun 29, 2017 at 3:33 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
> On Thu, Jun 22, 2017 at 12:00 PM, Jacopo Mondi
> <jacopo+renesas@...ndi.org> wrote:
>
>> Add output-enable generic pin configuration property.
>> This properties allows enabling/disabling pin's output capabilities
>> without actually driving any value on the line.

> I have applied the patch adding a few elaborations in the binding that
> the situation where you may use this is typically when enabling/disabling
> input or output buffers irrespective of the mode of the line as a whole.
>
> We might need even more documentation because this is really
> confusing.
>
> But for now it lets drivers work, which is nice.
>
> Rough consensus and running code should be our guide.

At least this looks much better than odd bi-directional thingy.
Thanks!

-- 
With Best Regards,
Andy Shevchenko