From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: <linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, Wayne Chang <waynec@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH V5 3/5] dt-bindings: usb: tegra-xudc: Add Tegra234 XUDC support
Date: Thu, 19 Jan 2023 10:42:06 +0000 [thread overview]
Message-ID: <20230119104208.28726-4-jonathanh@nvidia.com> (raw)
In-Reply-To: <20230119104208.28726-1-jonathanh@nvidia.com>
From: Wayne Chang <waynec@nvidia.com>
Extend the Tegra XUSB controller device (XUDC) tree binding with
Tegra234 support.
Signed-off-by: Wayne Chang <waynec@nvidia.com>
Co-developed-by: Jon Hunter <jonathanh@nvidia.com>
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
V4 -> V5: added Krzysztof's ACK
V3 -> V4: added 'dma-coherent' for Tegra234
V2 -> V3: nothing has changed
V1 -> V2: address the issue on phy-names property
Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.yaml b/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.yaml
index 4ef88d38fa3a..e638f77658fc 100644
--- a/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.yaml
+++ b/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.yaml
@@ -22,6 +22,7 @@ properties:
- nvidia,tegra210-xudc # For Tegra210
- nvidia,tegra186-xudc # For Tegra186
- nvidia,tegra194-xudc # For Tegra194
+ - nvidia,tegra234-xudc # For Tegra234
reg:
minItems: 2
@@ -155,6 +156,7 @@ allOf:
enum:
- nvidia,tegra186-xudc
- nvidia,tegra194-xudc
+ - nvidia,tegra234-xudc
then:
properties:
reg:
@@ -172,6 +174,7 @@ allOf:
contains:
enum:
- nvidia,tegra194-xudc
+ - nvidia,tegra234-xudc
then:
required:
- dma-coherent
--
2.25.1
next prev parent reply other threads:[~2023-01-19 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 10:42 [PATCH V5 0/5] Tegra USB device support updates Jon Hunter
2023-01-19 10:42 ` [PATCH V5 1/5] dt-bindings: usb: tegra-xudc: Add dma-coherent for Tegra194 Jon Hunter
2023-01-22 14:12 ` Krzysztof Kozlowski
2023-01-24 13:58 ` Thierry Reding
2023-01-19 10:42 ` [PATCH V5 2/5] arm64: tegra: Add dma-coherent property for Tegra194 XUDC Jon Hunter
2023-01-19 10:42 ` Jon Hunter [this message]
2023-01-24 13:58 ` [PATCH V5 3/5] dt-bindings: usb: tegra-xudc: Add Tegra234 XUDC support Thierry Reding
2023-01-19 10:42 ` [PATCH V5 4/5] usb: gadget: tegra-xudc: Add Tegra234 support Jon Hunter
2023-01-24 13:58 ` Thierry Reding
2023-01-19 10:42 ` [PATCH V5 5/5] arm64: tegra: Populate the XUDC node for Tegra234 Jon Hunter
2023-01-24 13:57 ` [PATCH V5 0/5] Tegra USB device support updates Thierry Reding
2023-01-25 14:44 ` Greg Kroah-Hartman
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=20230119104208.28726-4-jonathanh@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=waynec@nvidia.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).