From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] dt-bindings: tegra: Document Jetson Orin Nano
Date: Tue, 4 Apr 2023 12:59:16 +0200 [thread overview]
Message-ID: <ZCwDBO6317rGsAD4@orome> (raw)
In-Reply-To: <944bc557-7090-4b5a-e1bc-31b99fad06e5@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]
On Fri, Mar 31, 2023 at 10:20:16PM +0200, Krzysztof Kozlowski wrote:
> On 31/03/2023 18:31, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The Jetson Orin Nano is the little sibling of the Jetson Orin NX.
> > Document the corresponding compatible strings for these devices.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Documentation/devicetree/bindings/arm/tegra.yaml | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/tegra.yaml b/Documentation/devicetree/bindings/arm/tegra.yaml
> > index 61e638c9cad7..60c151da5e06 100644
> > --- a/Documentation/devicetree/bindings/arm/tegra.yaml
> > +++ b/Documentation/devicetree/bindings/arm/tegra.yaml
> > @@ -220,6 +220,13 @@ properties:
> > - nvidia,p3767-0001
> > - nvidia,p3767-0002
> > - const: nvidia,tegra234
> > + - description: Jetson Orin Nano
> > + items:
> > + - enum:
> > + - nvidia,p3767-0003
> > + - nvidia,p3767-0004
> > + - nvidia,p3767-0005
>
> Similar questions as for patch #1. Where are the DTSes? Where are the
> differences? If we keep documenting every SKU which is the same from
> user/OS perspective, this list would grow crazy.
Most of the differences will be user-noticeable, even if they can be
runtime detected. Besides the mentioned differences in DRAM size, things
like the number of CPUs, GPU compute units or video encoders/decoders
can vary depending on the SKU. While the OS should certainly be able to
abstract all of that away as best as possible, on user may still end up
with SKU 3 and another with SKU 5 and it's important for people to know
what they have.
So I think we have to find a way to both keep things simple from a DTS
point of view (as I said, we should be able to make do with one DTS file
for the Jetson Orin NX and one for the Jetson Orin Nano with UEFI taking
care of fixing up the DTS per SKU), and not lying to users. If users get
a SKU 3, then that's what we should report instead of 3 (or whatever
ends up being the SKU that we use in the DTS).
So I want to be as complete as possible in documenting these so that
when people go look for the part numbers, they can at least find some
reference to them.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-04 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 16:31 [PATCH 1/4] dt-bindings: Document additional Jetson Orin NX SKUs Thierry Reding
2023-03-31 16:31 ` [PATCH 2/4] dt-bindings: tegra: Document Jetson Orin Nano Thierry Reding
2023-03-31 20:20 ` Krzysztof Kozlowski
2023-04-04 10:59 ` Thierry Reding [this message]
2023-04-07 8:59 ` Krzysztof Kozlowski
2023-04-04 11:03 ` Thierry Reding
2023-03-31 16:31 ` [PATCH 3/4] dt-bindings: tegra: Document Jetson Orin Nano Developer Kit Thierry Reding
2023-03-31 16:31 ` [PATCH 4/4] arm64: tegra: Support " Thierry Reding
2023-03-31 20:19 ` [PATCH 1/4] dt-bindings: Document additional Jetson Orin NX SKUs Krzysztof Kozlowski
2023-04-04 10:49 ` Thierry Reding
2023-04-07 8:52 ` Krzysztof Kozlowski
2023-05-15 15:06 ` 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=ZCwDBO6317rGsAD4@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).