[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD++jLn8WOobPaoSrMLitFgFZc_6CH9BQbRy_Gdqq3BLhDXWQg@mail.gmail.com>
Date: Wed, 4 Feb 2026 00:34:36 +0100
From: Linus Walleij <linusw@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: Conor Dooley <conor.dooley@...rochip.com>, Xianwei Zhao <xianwei.zhao@...ogic.com>,
Neil Armstrong <neil.armstrong@...aro.org>, Kevin Hilman <khilman@...libre.com>,
Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>, linux-amlogic@...ts.infradead.org,
linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] pinctrl: pinconf-generic: move ..dt_node_to_map_pinmux() to
amlogic-am4 driver
On Tue, Feb 3, 2026 at 5:17 PM Conor Dooley <conor@...nel.org> wrote:
> From: Conor Dooley <conor.dooley@...rochip.com>
>
> pinconf_generic_dt_node_to_map_pinmux() is not actually a generic
> function, and really belongs in the amlogic-am4 driver. There are three
> reasons why.
(...)
> The other dt_node_to_map implementations accept a being called for
> either a node containing pin configuration properties or a node
> containing child nodes that each contain the configuration properties.
> IOW, they support the following two devicetree configurations:
>
> | cfg {
> | label: group {
> | pinmux = <asjhdasjhlajskd>;
> | config-item1;
> | };
> | };
>
> | label: cfg {
> | group1 {
> | pinmux = <dsjhlfka>;
> | config-item2;
> | };
> | group2 {
> | pinmux = <lsdjhaf>;
> | config-item1;
> | };
> | };
>
> pinconf_generic_dt_node_to_map_pinmux() only supports the latter.
This alone is a good reason to apply the patch.
I have a strong urge to apply this already for v7.0 despite its RFC state.
Anyone against?
Yours,
Linus Walleij
Powered by blists - more mailing lists