Devicetree
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Charan Pedumuru <charan.pedumuru@gmail.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH 7/8] arm64: tegra: Clean up AHUB on Tegra264
Date: Thu, 10 Sep 2026 17:36:41 +0100	[thread overview]
Message-ID: <c9ad15c1-10c0-4111-a143-baf72fccf1f2@nvidia.com> (raw)
In-Reply-To: <20260902-tegra-ahub-dt-cleanup-v1-7-028f3c5e72f6@nvidia.com>



On 02/09/2026 11:17, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Use #address-cells = <1> and #size-cells = <1> because we don't need
> 64-bit register addressing for this hardware. While at it, also adjust
> the ranges property to encompass the entire AHUB range as per the TRM.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>   arch/arm64/boot/dts/nvidia/tegra264.dtsi | 118 +++++++++++++++----------------
>   1 file changed, 59 insertions(+), 59 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/nvidia/tegra264.dtsi b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> index 6b2e3a6ab810..4ed7dabafee5 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> @@ -129,13 +129,13 @@ aconnect@9000000 {
>   			power-domains = <&bpmp TEGRA264_POWER_DOMAIN_AUD>;
>   			status = "disabled";

...

>   					ports {
> @@ -1584,7 +1584,7 @@ sfc1_cif_out: endpoint {
>   				tegra_sfc2: sfc@9710000 {
>   					compatible = "nvidia,tegra264-sfc",
>   							"nvidia,tegra210-sfc";
> -					reg = <0x0 0x9710000 0x0 0x10000>;
> +					reg = <0x9710000 x0 0x10000>;


Looks like a typo crept in here 'x0' which is what kernelci is
complaining about [0].

Jon

[0] https://lore.kernel.org/linux-tegra/178905234343.3919.16985173968804561026@kernelci.org/T/#u

-- 
nvpublic


  parent reply	other threads:[~2026-09-10 16:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 10:17 [PATCH 0/8] arm64: tegra: Clean up AHUB device tree nodes Thierry Reding
2026-09-02 10:17 ` [PATCH 1/8] ARM: tegra: Clean up AHUB on Tegra124 Thierry Reding
2026-09-02 10:23   ` sashiko-bot
2026-09-02 10:17 ` [PATCH 2/8] arm64: tegra: Clean up AHUB on Tegra132 Thierry Reding
2026-09-02 10:17 ` [PATCH 3/8] arm64: tegra: Adjust AHUB range on Tegra210 Thierry Reding
2026-09-02 10:17 ` [PATCH 4/8] arm64: tegra: Clean up AHUB on Tegra186 Thierry Reding
2026-09-02 10:17 ` [PATCH 5/8] arm64: tegra: Clean up AHUB on Tegra194 Thierry Reding
2026-09-02 10:17 ` [PATCH 6/8] arm64: tegra: Clean up AHUB on Tegra234 Thierry Reding
2026-09-02 10:17 ` [PATCH 7/8] arm64: tegra: Clean up AHUB on Tegra264 Thierry Reding
2026-09-02 10:31   ` sashiko-bot
2026-09-10 16:36   ` Jon Hunter [this message]
2026-09-11 10:32     ` Thierry Reding
2026-09-02 10:17 ` [PATCH 8/8] arm64: tegra: Clean up some whitespace issues " Thierry Reding
2026-09-10 13:31 ` (subset) [PATCH 0/8] arm64: tegra: Clean up AHUB device tree nodes 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=c9ad15c1-10c0-4111-a143-baf72fccf1f2@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=charan.pedumuru@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@kernel.org \
    --cc=treding@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