From: Rob Herring <robh@kernel.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Luiz Angelo Daros de Luca <luizluca@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
Joe Perches <joe@perches.com>,
erkin.bozoglu@xeront.com, 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 v2 13/14] dt-bindings: pinctrl: add binding for Ralink RT305X pinctrl
Date: Tue, 19 Apr 2022 13:05:38 -0500 [thread overview]
Message-ID: <Yl758u9iIMnhYPz2@robh.at.kernel.org> (raw)
In-Reply-To: <20220414173916.5552-14-arinc.unal@arinc9.com>
On Thu, Apr 14, 2022 at 08:39:15PM +0300, Arınç ÜNAL wrote:
> Add binding for the Ralink RT305X pin controller for RT3050, RT3052,
> RT3350, RT3352 and RT5350 SoCs.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> .../pinctrl/ralink,rt305x-pinctrl.yaml | 92 +++++++++++++++++++
> 1 file changed, 92 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml
> new file mode 100644
> index 000000000000..425401c54269
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml
> @@ -0,0 +1,92 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/ralink,rt305x-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Ralink RT305X Pin Controller
> +
> +maintainers:
> + - Arınç ÜNAL <arinc.unal@arinc9.com>
> + - Sergio Paracuellos <sergio.paracuellos@gmail.com>
> +
> +description:
> + Ralink RT305X pin controller for RT3050, RT3052, RT3350, RT3352 and RT5350
> + SoCs.
> + The pin controller can only set the muxing of pin groups. Muxing individual
> + pins is not supported. There is no pinconf support.
> +
> +properties:
> + compatible:
> + const: ralink,rt305x-pinctrl
You should have a compatible for each SoC unless these are all just
fused or package varients of the same chip.
> +
> +patternProperties:
> + '-pins$':
> + type: object
> + patternProperties:
> + '^(.*-)?pinmux$':
> + type: object
> + description: node for pinctrl.
> + $ref: pinmux-node.yaml#
> +
> + properties:
> + groups:
> + description: The pin group to select.
> + enum: [
> + # For RT3050, RT3052 and RT3350 SoCs
> + i2c, jtag, mdio, rgmii, sdram, spi, uartf, uartlite,
> +
> + # For RT3352 SoC
> + i2c, jtag, led, lna, mdio, pa, rgmii, spi, spi_cs1, uartf,
> + uartlite,
> +
> + # For RT5350 SoC
> + i2c, jtag, led, spi, spi_cs1, uartf, uartlite,
> + ]
> +
> + function:
> + description: The mux function to select.
> + enum: [
> + # For RT3050, RT3052 and RT3350 SoCs
> + gpio, gpio i2s, gpio uartf, i2c, i2s uartf, jtag, mdio, pcm gpio,
> + pcm i2s, pcm uartf, rgmii, sdram, spi, uartf, uartlite,
> +
> + # For RT3352 SoC
> + gpio, gpio i2s, gpio uartf, i2c, i2s uartf, jtag, led, lna, mdio,
> + pa, pcm gpio, pcm i2s, pcm uartf, rgmii, spi, spi_cs1, uartf,
> + uartlite, wdg_cs1,
> +
> + # For RT5350 SoC
> + gpio, gpio i2s, gpio uartf, i2c, i2s uartf, jtag, led, pcm gpio,
> + pcm i2s, pcm uartf, spi, spi_cs1, uartf, uartlite, wdg_cs1,
> + ]
> +
> + required:
> + - groups
> + - function
> +
> + additionalProperties: false
> +
> + additionalProperties: false
> +
> +allOf:
> + - $ref: "pinctrl.yaml#"
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +examples:
> + # Pinmux controller node
> + - |
> + pinctrl {
> + compatible = "ralink,rt305x-pinctrl";
> +
> + i2c_pins: i2c0-pins {
> + pinmux {
> + groups = "i2c";
> + function = "i2c";
> + };
> + };
> + };
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2022-04-19 18:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 17:39 [PATCH v2 00/14] Refactor Ralink Pinctrl and Add Documentation Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 01/14] pinctrl: ralink: rename MT7628(an) functions to MT76X8 Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 02/14] pinctrl: ralink: rename pinctrl-rt2880 to pinctrl-ralink Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 03/14] pinctrl: ralink: rename pinmux functions to pinctrl Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 04/14] pinctrl: ralink: rename pinctrl-rt288x to pinctrl-rt2880 Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 05/14] pinctrl: ralink: rename variable names for functions on MT7620 and MT7621 Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 06/14] pinctrl: ralink: rename driver names to subdrivers Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 07/14] pinctrl: ralink: add new compatible strings for each pinctrl subdriver Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 08/14] MAINTAINERS: add Ralink pinctrl driver Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 09/14] mips: dts: ralink: mt7621: use the new compatible string for MT7621 pinctrl Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 10/14] dt-bindings: pinctrl: rt2880: fix binding name, pin groups and functions Arınç ÜNAL
2022-04-19 18:02 ` Rob Herring
2022-04-14 17:39 ` [PATCH v2 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620 pinctrl Arınç ÜNAL
2022-04-19 18:03 ` Rob Herring
2022-04-14 17:39 ` [PATCH v2 12/14] dt-bindings: pinctrl: add binding for Ralink MT7621 pinctrl Arınç ÜNAL
2022-04-19 18:03 ` Rob Herring
2022-04-14 17:39 ` [PATCH v2 13/14] dt-bindings: pinctrl: add binding for Ralink RT305X pinctrl Arınç ÜNAL
2022-04-19 18:05 ` Rob Herring [this message]
2022-04-19 18:59 ` Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 14/14] dt-bindings: pinctrl: add binding for Ralink RT3883 pinctrl Arınç ÜNAL
2022-04-19 18:06 ` Rob Herring
2022-04-19 5:41 ` [PATCH v2 00/14] Refactor Ralink Pinctrl and Add Documentation Sergio Paracuellos
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=Yl758u9iIMnhYPz2@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=erkin.bozoglu@xeront.com \
--cc=joe@perches.com \
--cc=krzk+dt@kernel.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=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).