From: Thierry Reding <thierry.reding@gmail.com>
To: Shubhi Garg <shgarg@nvidia.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
jonathanh@nvidia.com, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: tegra: Document compatible for IGX
Date: Tue, 2 May 2023 13:39:16 +0200 [thread overview]
Message-ID: <ZFD2ZPZdY-Lo_2Ox@orome> (raw)
In-Reply-To: <20230502105437.769350-1-shgarg@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
On Tue, May 02, 2023 at 10:54:36AM +0000, Shubhi Garg wrote:
> 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>
> ---
> Documentation/devicetree/bindings/arm/tegra.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/tegra.yaml b/Documentation/devicetree/bindings/arm/tegra.yaml
> index 0df41f5b7e2a..6a5e303fba08 100644
> --- a/Documentation/devicetree/bindings/arm/tegra.yaml
> +++ b/Documentation/devicetree/bindings/arm/tegra.yaml
> @@ -176,5 +176,11 @@ properties:
> - const: nvidia,p3768-0000+p3767-0000
> - const: nvidia,p3767-0000
> - const: nvidia,tegra234
> + - description: NVIDIA IGX Orin Development Kit
> + items:
> + - const: nvidia,p3740-0002+p3701-0008
> + - const: nvidia,p3740-0002
We don't usually list the carrier board here. The reasoning is that we
first list the most specific combination (carrier + module) that the
device tree describes, then the module (which theoretically the same
device tree should also be able to run on) and finally the SoC. The OS
wouldn't know what to do with just the SoC, but we list it to make it
clear what SoC family this is.
The carrier board, on the other hand, is not something that the OS can
run on standalone because it doesn't have a CPU, so we omit that from
the list of compatible strings.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-02 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 10:54 [PATCH 1/2] dt-bindings: tegra: Document compatible for IGX Shubhi Garg
2023-05-02 10:54 ` [PATCH 2/2] arm64: tegra: Add support for IGX Orin Shubhi Garg
2023-05-02 11:39 ` Thierry Reding [this message]
2023-05-03 6:30 ` [PATCH 1/2] dt-bindings: tegra: Document compatible for IGX Krzysztof Kozlowski
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=ZFD2ZPZdY-Lo_2Ox@orome \
--to=thierry.reding@gmail.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=shgarg@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