linux-kernel - Re: [RFC v1 2/4] pinctrl: add polarfire soc mssio pinctrl driver

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: <CAD++jLnDA69jZ=6a3QexWn_V+NBymMwTBuJ29RM+R8m51eWOQQ@mail.gmail.com>
Date: Tue, 25 Nov 2025 20:59:49 +0100
From: Linus Walleij <linusw@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: Linus Walleij <linus.walleij@...aro.org>, Conor Dooley <conor.dooley@...rochip.com>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, linux-kernel@...r.kernel.org, 
	linux-gpio@...r.kernel.org, devicetree@...r.kernel.org, 
	Valentina.FernandezAlanis@...rochip.com, Bartosz Golaszewski <brgl@...ev.pl>
Subject: Re: [RFC v1 2/4] pinctrl: add polarfire soc mssio pinctrl driver

On Tue, Nov 25, 2025 at 8:55 PM Conor Dooley <conor@...nel.org> wrote:

> Probably too vague, since it's gonna be pins + functions specific, but
> I'll do something along these lines. Where should I put it? Leave it in
> pinconf-generic, but do some gating of it to only be exposed for configs
> with GENERIC_PINMUX_FUNCTIONS enabled?

Yeah just add something new and a whole new file like that, we will
probably add more stuff there as time goes.

Yours,
Linus Walleij