linux-kernel - Re: [PATCH v2 0/2] pinctrl: meson: prepare for new SoC

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: <7hshepfcgu.fsf@baylibre.com>
Date:   Wed, 11 Oct 2017 17:15:29 -0700
From:   Kevin Hilman <khilman@...libre.com>
To:     Jerome Brunet <jbrunet@...libre.com>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Carlo Caione <carlo@...one.org>, linux-gpio@...r.kernel.org,
        linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: meson: prepare for new SoC

Jerome Brunet <jbrunet@...libre.com> writes:

> The goal of this patchset is to prepare meson pinctrl driver to
> add a new meson SoC support. This new SoC will share the same pinconf/gpio
> registers but the pinmux part will be slightly different.
>
> First patch allows to compile and ship only the necessary pinctrl drivers,
> depending on the architecture and configuration needs. This should save
> a bit of memory.
>
> Second patch provide a way to deal with a different pinmux scheme, while
> reusing most of the meson pinctrl driver.
>
> Linus, FYI, this series depends on the meson changes you have already
> merged in this cycle.
>
> Change since v1: [0]
> * Use of_device_get_match_data() in patch
> * Change pmx naming scheme for the SoC parts
>
> [0]: https://lkml.kernel.org/r/20171009101747.16940-1-jbrunet@baylibre.com
>
> Jerome Brunet (2):
>   pinctrl: meson: separate soc drivers
>   pinctrl: meson: rework pinmux ops

Reviewed-by: Kevin Hilman <khilman@...libre.com>