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:   Fri, 10 Jul 2020 14:37:18 +0200
From:   Maxime Ripard <maxime@...no.tech>
To:     Ondřej Jirman <megous@...ous.com>,
        Frank Lee <frank@...winnertech.com>, robh+dt@...nel.org,
        wens@...e.org, mturquette@...libre.com, sboyd@...nel.org,
        gregory.clement@...tlin.com, tglx@...utronix.de,
        jason@...edaemon.net, maz@...nel.org,
        srinivas.kandagatla@...aro.org, linus.walleij@...aro.org,
        anarsoul@...il.com, tiny.windzz@...il.com, rui.zhang@...el.com,
        daniel.lezcano@...aro.org, amit.kucheria@...durent.com,
        lee.jones@...aro.org, p.zabel@...gutronix.de, clabbe@...libre.com,
        icenowy@...c.io, stefan@...mex.com, bage@...utronix.de,
        devicetree@...r.kernel.org, linux-pm@...r.kernel.org,
        liyong@...winnertech.com, linux-kernel@...r.kernel.org,
        linux-gpio@...r.kernel.org, huangshuosheng@...winnertech.com,
        linux-i2c@...r.kernel.org, linux-clk@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 04/16] dt-bindings: pinctrl: sunxi: make gpio banks
 supplies required

Hi,

On Thu, Jul 09, 2020 at 07:17:13PM +0200, Ondřej Jirman wrote:
> Hello,
> 
> On Wed, Jul 08, 2020 at 03:19:30PM +0800, Frank Lee wrote:
> > Since we don't really have to care about the existing DT for boards,
> > it would be great to make the gpio banks supplies required.
> 
> What if the borad doesn't use one of the banks? How would
> I describe such a board if defining supplies for all banks
> is required?

If that case ever comes up, we can always drop the requirement, it's going to be backward
compatible.

Maxime

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ