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 1/4] dt-bindings: Document additional Jetson Orin NX SKUs
Date: Tue, 4 Apr 2023 12:49:00 +0200 [thread overview]
Message-ID: <ZCwAnBbeYVVUMti8@orome> (raw)
In-Reply-To: <3a8724bc-fb44-0080-fd24-c04e3841385e@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 1447 bytes --]
On Fri, Mar 31, 2023 at 10:19:00PM +0200, Krzysztof Kozlowski wrote:
> On 31/03/2023 18:31, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Beyond the original 16 GiB SKU (0), additional SKUs exist, such as the 8
> > GiB SKU (1) and an internal-only SKU (2) that comes with an equipeed SD
>
> typo: equipped
>
> > card slot.
>
> Is there a point in documenting all of them if there is no DTS? Also,
> size of storage (eMMC?) pretty often is runtime-detectable, so you do no
> need a new DTS and new compatible.
This is for the sake of completeness since these compatible strings
correspond to the part numbers that will show up on stickers on these
modules. In practice, yes, most of the differences will be runtime-
detected and the DT updated to reflect the SKU differences by UEFI.
As far as I know, UEFI doesn't actually do anything with the compatible
strings themselves, but that's potentially something that could happen
at some point. The SKU numbers also show up in EEPROMs, so I think
having one place where these are documented might be helpful to people.
The 16 GiB in this case is actually DRAM, but it's also detected at
runtime. We don't actually plan on upstreaming DTS files for all of
these, since we don't expect all SKUs to be widely used (the internal
one, for example) so we should be able to cover pretty much all variants
with just two DTS files.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-04 10:50 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
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 [this message]
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=ZCwAnBbeYVVUMti8@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).