[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD++jLku5_fyDXw+uJ8Gj_1nQxjq8egOh60X1ARGC5dmFAcV+g@mail.gmail.com>
Date: Wed, 7 Jan 2026 15:13:19 +0100
From: Linus Walleij <linusw@...nel.org>
To: Chen-Yu Tsai <wens@...nel.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Jernej Skrabec <jernej@...nel.org>,
Samuel Holland <samuel@...lland.org>, Mauro Carvalho Chehab <mchehab@...nel.org>, devicetree@...r.kernel.org,
linux-sunxi@...ts.linux.dev, linux-gpio@...r.kernel.org,
linux-media@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: pinctrl: sunxi: Allow pinmux sub-pattern
with leading numbers
On Thu, Dec 25, 2025 at 11:36 AM Chen-Yu Tsai <wens@...nel.org> wrote:
> The pattern for pinmux node names is typically the peripheral name and
> instance number, followed by pingroup name if there are multiple options.
>
> Normally the instance number is directly appended to the peripheral
> name, like "mmc0" or "i2c2". But if the peripheral name ends with a
> number, then it becomes confusing.
>
> On the A20, the PS2 interface controller has two instances. This
> produces pinmux node names like "ps2-0-pins". Make the sub-pattern
> "[0-9]-" valid to fit this pattern. Avoid having to confusing "ps20-pins"
> name.
>
> Signed-off-by: Chen-Yu Tsai <wens@...nel.org>
This patch 2/4 applied to the pin control tree.
Yours,
Linus Walleij
Powered by blists - more mailing lists