From: Shubhi Garg <shgarg@nvidia.com>
To: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Cc: <shgarg@nvidia.com>
Subject: [PATCH v2 1/2] dt-bindings: tegra: Document compatible for IGX
Date: Mon, 8 May 2023 10:27:32 +0000 [thread overview]
Message-ID: <20230508102733.1751527-1-shgarg@nvidia.com> (raw)
Document the compatible strings used for Nvidia IGX Orin Development
kit which uses P3701 SKU8 and P3740 carrier board.
Signed-off-by: Shubhi Garg <shgarg@nvidia.com>
---
v2: sorted IGX Orin position as per part number. Since
P3740 is designed prior to P3768, it is placed before Orin NX.
Documentation/devicetree/bindings/arm/tegra.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/tegra.yaml b/Documentation/devicetree/bindings/arm/tegra.yaml
index 0df41f5b7e2a..6970ca1b8bd8 100644
--- a/Documentation/devicetree/bindings/arm/tegra.yaml
+++ b/Documentation/devicetree/bindings/arm/tegra.yaml
@@ -167,6 +167,11 @@ properties:
- const: nvidia,p3737-0000+p3701-0000
- const: nvidia,p3701-0000
- const: nvidia,tegra234
+ - description: NVIDIA IGX Orin Development Kit
+ items:
+ - const: nvidia,p3740-0002+p3701-0008
+ - const: nvidia,p3701-0008
+ - const: nvidia,tegra234
- description: Jetson Orin NX
items:
- const: nvidia,p3767-0000
--
2.17.1
next reply other threads:[~2023-05-08 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 10:27 Shubhi Garg [this message]
2023-05-08 10:27 ` [PATCH v2 2/2] arm64: tegra: Add support for IGX Orin Shubhi Garg
2023-05-08 11:27 ` [PATCH v2 1/2] dt-bindings: tegra: Document compatible for IGX Rob Herring
2023-05-08 16:22 ` Krzysztof Kozlowski
2023-05-08 16:21 ` Krzysztof Kozlowski
2023-05-15 15:11 ` 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=20230508102733.1751527-1-shgarg@nvidia.com \
--to=shgarg@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--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).