devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Add SBSA UART for Tegra234
Date: Mon, 24 Oct 2022 15:45:17 +0200	[thread overview]
Message-ID: <Y1aW7R/Yb440/fey@orome> (raw)
In-Reply-To: <20221019144700.170361-1-jonathanh@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

On Wed, Oct 19, 2022 at 03:47:00PM +0100, Jon Hunter wrote:
> Populate the SBSA UART for Tegra234 and enable this UART for Jetson AGX
> Orin.
> 
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
>  .../boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts     | 5 +++++
>  arch/arm64/boot/dts/nvidia/tegra234.dtsi                   | 7 +++++++
>  2 files changed, 12 insertions(+)

Applied, thanks. I noticed that the nodes have become a litte disordered
after the P2U nodes were added in commit ec142c44b026 ("arm64: tegra:
Add P2U and PCIe controller nodes to Tegra234 DT"), so I sorted the SBSA
UART node correctly and then reordered the remaining nodes correctly.

We should probably have a check for that. I'll see if I can come up with
something quickly.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-10-24 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 14:47 [PATCH] arm64: tegra: Add SBSA UART for Tegra234 Jon Hunter
2022-10-24 13:45 ` Thierry Reding [this message]

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=Y1aW7R/Yb440/fey@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 \
    /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).