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  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:   Wed, 29 Nov 2017 13:46:01 +0100
From:   Linus Walleij <>
To:     Mika Westerberg <>
Cc:     Andy Shevchenko <>,
        Heikki Krogerus <>,
        "Rafael J. Wysocki" <>,
        Hans de Goede <>,
        Takashi Iwai <>,
        ACPI Devel Maling List <>,
        "" <>
Subject: Re: [PATCH 2/3] pinctrl: intel: Allow custom GPIO base for pad groups

On Mon, Nov 27, 2017 at 2:54 PM, Mika Westerberg
<> wrote:

> Currently we always have direct mapping between GPIO numbers and the
> hardware pin numbers. However, there are cases where that's not the case
> anymore (more about this in the next patch). Instead we need to be able
> to specify custom GPIO base for certain pad groups.
> To support this, add a new field (gpio_base) to the pad group structure
> and update the core Intel pinctrl driver to handle this accordingly.
> Passing 0 as gpio_base will use direct mapping so the existing drivers
> do not need to be modified. Passing -1 excludes the whole pad group from
> having GPIO mapping.
> Signed-off-by: Mika Westerberg <>

Patch applied with Andy's ACK.

Linus Walleij

Powered by blists - more mailing lists