From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
Prathamesh Shete <pshete@nvidia.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: pinctrl: Document Tegra234 pin controllers
Date: Sun, 4 Jun 2023 12:32:23 +0200 [thread overview]
Message-ID: <772cf729-e42d-14ac-f9d5-31cf071bd58d@linaro.org> (raw)
In-Reply-To: <20230602141445.3012550-2-thierry.reding@gmail.com>
On 02/06/2023 16:14, Thierry Reding wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
>
> Tegra234 contains two pin controllers. Document their compatible strings
> and describe the list of pins and functions that they provide.
>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v4:
> - move "$ref" and "required" properties into more standard locations
> - use "additionalProperties: true" for common bindings
> - use unevaluatedProperties for specific bindings
> - only allow valid per-SoC pin group properties
> - drop unnecessary or duplicated properties
>
> Changes in v3:
> - split up into multiple files (suggested by Krzysztof)
> - do not permit underscore in pinmux node names
> - reword commit message
>
> .../pinctrl/nvidia,tegra234-pinmux-aon.yaml | 59 ++++++++
> .../nvidia,tegra234-pinmux-common.yaml | 66 +++++++++
> .../pinctrl/nvidia,tegra234-pinmux.yaml | 139 ++++++++++++++++++
> 3 files changed, 264 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-aon.yaml
> create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-common.yaml
> create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux.yaml
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-aon.yaml b/Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-aon.yaml
> new file mode 100644
> index 000000000000..4ec969451eec
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-aon.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/nvidia,tegra234-pinmux-aon.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NVIDIA Tegra234 AON Pinmux Controller
> +
> +maintainers:
> + - Thierry Reding <thierry.reding@gmail.com>
> + - Jon Hunter <jonathanh@nvidia.com>
> +
> +$ref: nvidia,tegra234-pinmux-common.yaml
> +
> +properties:
> + compatible:
> + const: nvidia,tegra234-pinmux-aon
> +
> +patternProperties:
> + "^pinmux(-[a-z0-9-]+)?$":
> + type: object
> +
> + # pin groups
> + additionalProperties:
> + properties:
> + nvidia,pins:
> + items:
> + enum: [ can0_dout_paa0, can0_din_paa1, can1_dout_paa2,
> + can1_din_paa3, can0_stb_paa4, can0_en_paa5,
> + soc_gpio49_paa6, can0_err_paa7, can1_stb_pbb0,
> + can1_en_pbb1, soc_gpio50_pbb2, can1_err_pbb3,
> + spi2_sck_pcc0, spi2_miso_pcc1, spi2_mosi_pcc2,
> + spi2_cs0_pcc3, touch_clk_pcc4, uart3_tx_pcc5,
> + uart3_rx_pcc6, gen2_i2c_scl_pcc7, gen2_i2c_sda_pdd0,
> + gen8_i2c_scl_pdd1, gen8_i2c_sda_pdd2,
> + sce_error_pee0, vcomp_alert_pee1,
> + ao_retention_n_pee2, batt_oc_pee3, power_on_pee4,
> + soc_gpio26_pee5, soc_gpio27_pee6, bootv_ctl_n_pee7,
> + hdmi_cec_pgg0,
> + # drive groups
> + drive_touch_clk_pcc4, drive_uart3_rx_pcc6,
> + drive_uart3_tx_pcc5, drive_gen8_i2c_sda_pdd2,
> + drive_gen8_i2c_scl_pdd1, drive_spi2_mosi_pcc2,
> + drive_gen2_i2c_scl_pcc7, drive_spi2_cs0_pcc3,
> + drive_gen2_i2c_sda_pdd0, drive_spi2_sck_pcc0,
> + drive_spi2_miso_pcc1, drive_can1_dout_paa2,
> + drive_can1_din_paa3, drive_can0_dout_paa0,
> + drive_can0_din_paa1, drive_can0_stb_paa4,
> + drive_can0_en_paa5, drive_soc_gpio49_paa6,
> + drive_can0_err_paa7, drive_can1_stb_pbb0,
> + drive_can1_en_pbb1, drive_soc_gpio50_pbb2,
> + drive_can1_err_pbb3, drive_sce_error_pee0,
> + drive_batt_oc_pee3, drive_bootv_ctl_n_pee7,
> + drive_power_on_pee4, drive_soc_gpio26_pee5,
> + drive_soc_gpio27_pee6, drive_ao_retention_n_pee2,
> + drive_vcomp_alert_pee1, drive_hdmi_cec_pgg0 ]
> +
> +unevaluatedProperties: false
I missed in the previous review, apologies, can you add here example
DTS? Each device binding (except common parts) is expected to have example.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-04 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 14:14 [PATCH v4 0/3] pinctrl: tegra: Add Tegra234 pinmux driver Thierry Reding
2023-06-02 14:14 ` [PATCH v4 1/3] dt-bindings: pinctrl: Document Tegra234 pin controllers Thierry Reding
2023-06-04 10:32 ` Krzysztof Kozlowski [this message]
2023-06-02 14:14 ` [PATCH v4 2/3] pinctrl: tegra: Add Tegra234 pinmux driver Thierry Reding
2023-06-03 10:46 ` andy.shevchenko
2023-06-02 14:14 ` [PATCH v4 3/3] arm64: tegra: Add Tegra234 pin controllers Thierry Reding
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=772cf729-e42d-14ac-f9d5-31cf071bd58d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).