From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 5/7] dt-bindings: arm: tegra: pmc: Restructure pad configuration node schema
Date: Fri, 7 Jul 2023 16:35:03 -0600 [thread overview]
Message-ID: <20230707223503.GA1087110-robh@kernel.org> (raw)
In-Reply-To: <20230707131711.2997956-5-thierry.reding@gmail.com>
On Fri, Jul 07, 2023 at 03:17:09PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The pad configuration node schema in its current form can accidentally
> match other properties as well. Restructure the schema to better match
> how the device trees are using these.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../arm/tegra/nvidia,tegra20-pmc.yaml | 181 ++++++++++++------
> 1 file changed, 120 insertions(+), 61 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-pmc.yaml b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-pmc.yaml
> index 82070d47ac7c..271aa8f80a65 100644
> --- a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-pmc.yaml
> +++ b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-pmc.yaml
> @@ -245,69 +245,82 @@ properties:
> - resets
> - '#power-domain-cells'
>
> -patternProperties:
> - "^[a-f0-9]+-[a-f0-9]+$":
> + pinmux:
> type: object
> - description:
> - This is a Pad configuration node. On Tegra SOCs a pad is a set of
> - pins which are configured as a group. The pin grouping is a fixed
> - attribute of the hardware. The PMC can be used to set pad power state
> - and signaling voltage. A pad can be either in active or power down mode.
> - The support for power state and signaling voltage configuration varies
> - depending on the pad in question. 3.3V and 1.8V signaling voltages
> - are supported on pins where software controllable signaling voltage
> - switching is available.
> -
> - The pad configuration state nodes are placed under the pmc node and they
> - are referred to by the pinctrl client properties. For more information
> - see Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt.
> - The pad name should be used as the value of the pins property in pin
> - configuration nodes.
> -
> - The following pads are present on Tegra124 and Tegra132
> - audio, bb, cam, comp, csia, csb, cse, dsi, dsib, dsic, dsid, hdmi, hsic,
> - hv, lvds, mipi-bias, nand, pex-bias, pex-clk1, pex-clk2, pex-cntrl,
> - sdmmc1, sdmmc3, sdmmc4, sys_ddc, uart, usb0, usb1, usb2, usb_bias.
> -
> - The following pads are present on Tegra210
> - audio, audio-hv, cam, csia, csib, csic, csid, csie, csif, dbg,
> - debug-nonao, dmic, dp, dsi, dsib, dsic, dsid, emmc, emmc2, gpio, hdmi,
> - hsic, lvds, mipi-bias, pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1,
> - sdmmc3, spi, spi-hv, uart, usb0, usb1, usb2, usb3, usb-bias.
> -
> properties:
> - pins:
> - $ref: /schemas/types.yaml#/definitions/string
> - description: Must contain name of the pad(s) to be configured.
> -
> - low-power-enable:
> - $ref: /schemas/types.yaml#/definitions/flag
> - description: Configure the pad into power down mode.
> -
> - low-power-disable:
> - $ref: /schemas/types.yaml#/definitions/flag
> - description: Configure the pad into active mode.
> -
> - power-source:
> - $ref: /schemas/types.yaml#/definitions/uint32
> - description:
> - Must contain either TEGRA_IO_PAD_VOLTAGE_1V8 or
> - TEGRA_IO_PAD_VOLTAGE_3V3 to select between signaling voltages.
> - The values are defined in
> - include/dt-bindings/pinctrl/pinctrl-tegra-io-pad.h.
> - Power state can be configured on all Tegra124 and Tegra132
> - pads. None of the Tegra124 or Tegra132 pads support signaling
> - voltage switching.
> - All of the listed Tegra210 pads except pex-cntrl support power
> - state configuration. Signaling voltage switching is supported
> - on below Tegra210 pads.
> - audio, audio-hv, cam, dbg, dmic, gpio, pex-cntrl, sdmmc1,
> - sdmmc3, spi, spi-hv, and uart.
> -
> - required:
> - - pins
> -
> - additionalProperties: false
> + status: true
If you need this, that's a bug in dtschema.
> +
> + additionalProperties:
> + type: object
> + description: |
> + This is a pad configuration node. On Tegra SoCs a pad is a set of pins
> + which are configured as a group. The pin grouping is a fixed attribute
> + of the hardware. The PMC can be used to set pad power state and
> + signaling voltage. A pad can be either in active or power down mode.
> + The support for power state and signaling voltage configuration varies
> + depending on the pad in question. 3.3V and 1.8V signaling voltages are
> + supported on pins where software controllable signaling voltage
> + switching is available.
> +
> + The pad configuration state nodes are placed under the pmc node and
> + they are referred to by the pinctrl client properties. For more
> + information see:
> +
> + Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> +
> + The pad name should be used as the value of the pins property in pin
> + configuration nodes.
> +
> + The following pads are present on Tegra124 and Tegra132:
> +
> + audio, bb, cam, comp, csia, csb, cse, dsi, dsib, dsic, dsid, hdmi,
> + hsic, hv, lvds, mipi-bias, nand, pex-bias, pex-clk1, pex-clk2,
> + pex-cntrl, sdmmc1, sdmmc3, sdmmc4, sys_ddc, uart, usb0, usb1, usb2,
> + usb_bias
> +
> + The following pads are present on Tegra210:
> +
> + audio, audio-hv, cam, csia, csib, csic, csid, csie, csif, dbg,
> + debug-nonao, dmic, dp, dsi, dsib, dsic, dsid, emmc, emmc2, gpio,
> + hdmi, hsic, lvds, mipi-bias, pex-bias, pex-clk1, pex-clk2, pex-cntrl,
> + sdmmc1, sdmmc3, spi, spi-hv, uart, usb0, usb1, usb2, usb3, usb-bias
> + additionalProperties: false
> + properties:
> + pins:
> + $ref: /schemas/types.yaml#/definitions/string-array
> + description: Must contain name of the pad(s) to be configured.
> +
> + low-power-enable:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description: Configure the pad into power down mode.
> +
> + low-power-disable:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description: Configure the pad into active mode.
> +
> + power-source:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Must contain either TEGRA_IO_PAD_VOLTAGE_1V8 or
> + TEGRA_IO_PAD_VOLTAGE_3V3 to select between signaling voltages. The
> + values are defined in:
> +
> + include/dt-bindings/pinctrl/pinctrl-tegra-io-pad.h
> +
> + Power state can be configured on all Tegra124 and Tegra132 pads.
> + None of the Tegra124 or Tegra132 pads support signaling voltage
> + switching. All of the listed Tegra210 pads except pex-cntrl support
> + power state configuration. Signaling voltage switching is supported
> + on the following Tegra210 pads:
> +
> + audio, audio-hv, cam, dbg, dmic, gpio, pex-cntrl, sdmmc1, sdmmc3,
> + spi, spi-hv, uart
> +
> + phandle:
> + $ref: /schemas/types.yaml#/definitions/uint32
ditto
> +
> + required:
> + - pins
>
> required:
> - compatible
> @@ -316,6 +329,52 @@ required:
> - clocks
> - '#clock-cells'
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: nvidia,tegra124-pmc
> + then:
> + properties:
> + pinmux:
> + properties:
> + status: true
> +
> + additionalProperties:
> + type: object
> + properties:
> + pins:
> + items:
> + enum: [ audio, bb, cam, comp, csia, csb, cse, dsi, dsib,
> + dsic, dsid, hdmi, hsic, hv, lvds, mipi-bias, nand,
> + pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1,
> + sdmmc3, sdmmc4, sys_ddc, uart, usb0, usb1, usb2,
> + usb_bias ]
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: nvidia,tegra210-pmc
> + then:
> + properties:
> + pinmux:
> + properties:
> + status: true
> +
> + additionalProperties:
> + type: object
> + properties:
> + pins:
> + items:
> + enum: [ audio, audio-hv, cam, csia, csib, csic, csid, csie,
> + csif, dbg, debug-nonao, dmic, dp, dsi, dsib, dsic,
> + dsid, emmc, emmc2, gpio, hdmi, hsic, lvds, mipi-bias,
> + pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1,
> + sdmmc3, spi, spi-hv, uart, usb0, usb1, usb2, usb3,
> + usb-bias ]
> +
> additionalProperties: false
>
> dependencies:
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-07-07 22:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 13:17 [PATCH 1/7] dt-bindings: arm: tegra: pmc: Improve property descriptions Thierry Reding
2023-07-07 13:17 ` [PATCH 2/7] dt-bindings: arm: tegra: pmc: Remove useless boilerplate descriptions Thierry Reding
2023-07-07 22:30 ` Rob Herring
2023-07-07 13:17 ` [PATCH 3/7] dt-bindings: arm: tegra: pmc: Move additionalProperties Thierry Reding
2023-07-07 22:30 ` Rob Herring
2023-07-07 13:17 ` [PATCH 4/7] dt-bindings: arm: tegra: pmc: Increase maximum number of clocks per powergate Thierry Reding
2023-07-07 22:31 ` Rob Herring
2023-07-07 13:17 ` [PATCH 5/7] dt-bindings: arm: tegra: pmc: Restructure pad configuration node schema Thierry Reding
2023-07-07 22:35 ` Rob Herring [this message]
2023-07-10 13:57 ` Thierry Reding
2023-07-14 15:12 ` Thierry Reding
2023-07-07 13:17 ` [PATCH 6/7] dt-bindings: arm: tegra: pmc: Reformat example Thierry Reding
2023-07-07 22:35 ` Rob Herring
2023-07-07 13:17 ` [PATCH 7/7] dt-bindings: arm: tegra: pmc: Relicense and move into soc/tegra directory Thierry Reding
2023-07-07 22:35 ` Rob Herring
2023-07-07 22:29 ` [PATCH 1/7] dt-bindings: arm: tegra: pmc: Improve property descriptions Rob Herring
2023-07-10 13:19 ` 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=20230707223503.GA1087110-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.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).