linux-kernel - Re: [PATCH v2 0/3] pinctrl: single: bit-per-mux DT flexibility, probe robustness, and consistent pinconf offsets

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAD++jLkB26XNAosUdD2BigLw+=Hd6+VBsmv0fHawQ25e8rQhrQ@mail.gmail.com>
Date: Mon, 9 Feb 2026 10:50:47 +0100
From: Linus Walleij <linusw@...nel.org>
To: Billy Tsai <billy_tsai@...eedtech.com>
Cc: Tony Lindgren <tony@...mide.com>, Haojian Zhuang <haojian.zhuang@...aro.org>, 
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, 
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>, 
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, 
	"andrew@...econstruct.com.au" <andrew@...econstruct.com.au>, BMC-SW <BMC-SW@...eedtech.com>
Subject: Re: [PATCH v2 0/3] pinctrl: single: bit-per-mux DT flexibility, probe
 robustness, and consistent pinconf offsets

On Mon, Feb 9, 2026 at 3:25 AM Billy Tsai <billy_tsai@...eedtech.com> wrote:

> To make sure I align with your expectations:
> 1) Would you prefer the new driver to be fully standalone (using the
>    GENERIC_PIN* helpers + syscon/regmap-mmio), rather than trying to
>    refactor/export helpers from pinctrl-single?

Yes. Conor improved these helpers so now it should be possible
to use these to do a very simple and slim driver for what you
want to do.

>    Action item: Introduce a new pinctrl-single-bit.c driver and DT
>    binding, which can also cover the existing bit-per-mux logic currently
>    in pinctrl-single.c.

Sounds about right.

> 2) For the syscon/regmap hookup, is it acceptable to add a syscon phandle
>    property in DT (e.g. "syscon = <&scu>;") for the new driver to obtain
>    the regmap, or do you prefer a different binding/property name?

This works for me.

Yours,
Linus Walleij