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: <CACRpkdbeuhNRE_-WmGeed0Sj4Zg3r+JnVKX-CET1s3SkD=k4=w@mail.gmail.com>
Date:   Tue, 1 Aug 2017 10:14:07 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/6] pinctrl: uniphier: clean up GPIO port muxing

On Mon, Jul 31, 2017 at 8:21 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:

> There are a bunch of GPIO muxing data, but most of them are actually
> unneeded because GPIO-to-pin mapping can be specified by "gpio-ranges"
> DT properties.
>
> Tables that contain a set of GPIO pins are still needed for the named
> mapping by "gpio-ranges-group-names".  This is a much cleaner way for
> UniPhier SoC family where GPIO numbers are not straight mapped to pin
> numbers.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>

Patch applied.

Yours,
Linus Walleij

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ