From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 2/6] dt-bindings: pinctrl: mt7620: add proper function muxing binding
Date: Wed, 14 Dec 2022 16:03:00 +0300 [thread overview]
Message-ID: <e4b6b334-44c3-9e73-adaa-9972ff9e6fd5@arinc9.com> (raw)
In-Reply-To: <4ffd94b2-e72c-a081-4326-5bc254603ddf@linaro.org>
On 14.12.2022 14:55, Krzysztof Kozlowski wrote:
> On 13/12/2022 14:04, Arınç ÜNAL wrote:
>> Not every function can be muxed to a group. Add proper binding which
>> documents which function can be muxed to a group or set of groups.
>>
>> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
>> ---
>> .../pinctrl/ralink,mt7620-pinctrl.yaml | 632 +++++++++++++++++-
>> 1 file changed, 596 insertions(+), 36 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
>> index 6f17f3991640..06880c80ba80 100644
>> --- a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
>> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
>> @@ -29,47 +29,608 @@ patternProperties:
>> $ref: pinmux-node.yaml#
>>
>> properties:
>> - groups:
>> - description: The pin group to select.
>> - enum: [
>> - # common
>> - i2c, spi, wdt,
>> -
>> - # For MT7620 SoC
>> - ephy, mdio, nd_sd, pa, pcie, rgmii1, rgmii2, spi refclk,
>> - uartf, uartlite, wled,
>> -
>> - # For MT7628 and MT7688 SoCs
>> - gpio, i2s, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an,
>> - p2led_kn, p3led_an, p3led_kn, p4led_an, p4led_kn, perst, pwm0,
>> - pwm1, refclk, sdmode, spi cs1, spis, uart0, uart1, uart2,
>> - wled_an, wled_kn,
>> - ]
>> -
>> function:
>> - description: The mux function to select.
>> - enum: [
>> - # common
>> - gpio, i2c, refclk, spi,
>> -
>> - # For MT7620 SoC
>> - ephy, gpio i2s, gpio uartf, i2s uartf, mdio, nand, pa,
>> - pcie refclk, pcie rst, pcm gpio, pcm i2s, pcm uartf,
>> - rgmii1, rgmii2, sd, spi refclk, uartf, uartlite, wdt refclk,
>> - wdt rst, wled,
>> -
>> - # For MT7628 and MT7688 SoCs
>> - antenna, debug, i2s, jtag, p0led_an, p0led_kn,
>> - p1led_an, p1led_kn, p2led_an, p2led_kn, p3led_an, p3led_kn,
>> - p4led_an, p4led_kn, pcie, pcm, perst, pwm, pwm0, pwm1, pwm_uart2,
>> - rsvd, sdxc, sdxc d5 d4, sdxc d6, sdxc d7, spi cs1,
>> - spis, sw_r, uart0, uart1, uart2, utif, wdt, wled_an, wled_kn, -,
>> - ]
>> + description:
>> + A string containing the name of the function to mux to the group.
>> + anyOf:
>> + - description: For MT7620 SoC
>> + enum: [ephy, gpio, gpio i2s, gpio uartf, i2c, i2s uartf, mdio, nand, pa,
>> + pcie refclk, pcie rst, pcm gpio, pcm i2s, pcm uartf, refclk,
>> + rgmii1, rgmii2, sd, spi, spi refclk, uartf, uartlite, wdt refclk,
>> + wdt rst, wled]
>> +
>> + - description: For MT7628 and MT7688 SoCs
>> + enum: [antenna, debug, gpio, i2c, i2s, jtag, p0led_an, p0led_kn,
>> + p1led_an, p1led_kn, p2led_an, p2led_kn, p3led_an, p3led_kn,
>> + p4led_an, p4led_kn, pcie, pcm, perst, pwm, pwm0, pwm1, pwm_uart2,
>> + refclk, rsvd, sdxc, sdxc d5 d4, sdxc d6, sdxc d7, spi, spi cs1,
>> + spis, sw_r, uart0, uart1, uart2, utif, wdt, wled_an, wled_kn, -]
>> +
>> + groups:
>> + description:
>> + An array of strings. Each string contains the name of a group.
>>
>> required:
>> - groups
>> - function
>>
>> + allOf:
>> + - if:
>> + properties:
>> + function:
>> + const: antenna
>> + then:
>> + properties:
>> + groups:
>> + enum: [i2s]
>
> I have doubts such setup is maintainable and readable. I would suggest
> to leave just few - maybe for gpio, jtag, refclk, utif.
These bindings are not going to change once all properly defined and I'm
here as a maintainer so I don't see an issue with maintaining the binding.
It's the whole pin configuration of an SoC squashed under a single
document. I guess this is the fate of the pinctrl bindings. The bindings
for mt7622 is not so different:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pinctrl/mediatek%2Cmt7622-pinctrl.yaml#n63
It's still much better than reading the code:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pinctrl/ralink/pinctrl-mt7620.c
Arınç
next prev parent reply other threads:[~2022-12-14 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 13:04 [PATCH 0/6] Enhance Ralink pinctrl documentation Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 1/6] pinctrl: ralink: rename variables which point out the pin group Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 2/6] dt-bindings: pinctrl: mt7620: add proper function muxing binding Arınç ÜNAL
2022-12-14 11:55 ` Krzysztof Kozlowski
2022-12-14 13:03 ` Arınç ÜNAL [this message]
2022-12-14 13:10 ` Krzysztof Kozlowski
2022-12-13 13:04 ` [PATCH 3/6] dt-bindings: pinctrl: mt7621: " Arınç ÜNAL
2022-12-14 13:13 ` Krzysztof Kozlowski
2022-12-13 13:04 ` [PATCH 4/6] dt-bindings: pinctrl: rt2880: " Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 5/6] dt-bindings: pinctrl: rt305x: " Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 6/6] dt-bindings: pinctrl: rt3883: " Arınç ÜNAL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4b6b334-44c3-9e73-adaa-9972ff9e6fd5@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®