From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] arm64: tegra: Add support for P3768+P3767
Date: Tue, 14 Mar 2023 18:12:11 +0000 [thread overview]
Message-ID: <c9fb8b45-566d-c82d-7d13-cc0ad85c285b@nvidia.com> (raw)
In-Reply-To: <20230302093353.3873247-4-thierry.reding@gmail.com>
On 02/03/2023 09:33, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Add support for the combination of the NVIDIA Jetson Orin NX (P3767)
> module and the P3768 carrier board.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../nvidia/tegra234-p3768-0000+p3767-0000.dts | 218 ++++++++++++++++++
> .../boot/dts/nvidia/tegra234-p3768-0000.dtsi | 133 +++++++++++
> 2 files changed, 351 insertions(+)
> create mode 100644 arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0000.dts
> create mode 100644 arch/arm64/boot/dts/nvidia/tegra234-p3768-0000.dtsi
Looks like we are missing a Makefile update in this patch.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2023-03-14 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 9:33 [PATCH 1/4] dt-bindings: tegra: Document Jetson Orin NX Thierry Reding
2023-03-02 9:33 ` [PATCH 2/4] dt-bindings: tegra: Document P3768+P3767 reference platform Thierry Reding
2023-03-02 9:33 ` [PATCH 3/4] arm64: tegra: Add Jetson Orin NX support Thierry Reding
2023-03-02 9:33 ` [PATCH 4/4] arm64: tegra: Add support for P3768+P3767 Thierry Reding
2023-03-14 18:12 ` Jon Hunter [this message]
2023-03-28 15:23 ` Jon Hunter
2023-03-08 20:26 ` [PATCH 1/4] dt-bindings: tegra: Document Jetson Orin NX Rob Herring
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=c9fb8b45-566d-c82d-7d13-cc0ad85c285b@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.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).