[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYoECsAGwUno0b_nz-iBB=iwO0Js_6k4O5k+xhig2NYkg@mail.gmail.com>
Date: Wed, 1 Oct 2025 13:32:37 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Conor Dooley <conor@...nel.org>
Cc: 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
Subject: Re: [RFC 2/5] dt-bindings: pinctrl: add pic64gx "gpio2" pinmux
On Fri, Sep 26, 2025 at 4:33 PM Conor Dooley <conor@...nel.org> wrote:
> pin role (1/0)
> --- ----------
> E14 MAC_0_MDC/GPIO_2_0
> E15 MAC_0_MDIO/GPIO_2_1
> F16 MAC_1_MDC/GPIO_2_2
> F17 MAC_1_MDIO/GPIO_2_3
So this is a group you can name "mac_grp" and a function
you can name "mac".
> D19 SPI_0_CLK/GPIO_2_4
> B18 SPI_0_SS0/GPIO_2_5
(...)
> E19 SPI_0_DO/GPIO_2_10
> C7 SPI_0_DI/GPIO_2_11
These pins would be "spi0_grp", function "spi0".
etc. No need for "pinmux" properties just use classix
group and function strings.
Yours,
Linus Walleij
Powered by blists - more mailing lists