All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 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 1/8] ARM: tegra: Clean up AHUB on Tegra124
Date: Fri, 18 Sep 2026 14:19:36 +0200	[thread overview]
Message-ID: <aq0sR4k96fGs1MY-@orome> (raw)
In-Reply-To: <1114db1e-55fa-4056-bcdd-f1512bac70c5@nvidia.com>

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

On Thu, Sep 17, 2026 at 09:01:54PM +0100, Jon Hunter wrote:
> Hi Thierry,
> 
> 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/arm/boot/dts/nvidia/tegra124.dtsi | 16 ++++++++--------
> >   1 file changed, 8 insertions(+), 8 deletions(-)
> > 
> > diff --git a/arch/arm/boot/dts/nvidia/tegra124.dtsi b/arch/arm/boot/dts/nvidia/tegra124.dtsi
> > index ce4efa1de509..7a71dba42dc0 100644
> > --- a/arch/arm/boot/dts/nvidia/tegra124.dtsi
> > +++ b/arch/arm/boot/dts/nvidia/tegra124.dtsi
> > @@ -1114,13 +1114,13 @@ ahub@70300000 {
> >   			    "rx3", "tx3", "rx4", "tx4", "rx5", "tx5",
> >   			    "rx6", "tx6", "rx7", "tx7", "rx8", "tx8",
> >   			    "rx9", "tx9";
> > -		ranges;
> > -		#address-cells = <2>;
> > -		#size-cells = <2>;
> > +		ranges = <0x7030000 0x0 0x70300000 0x10000>;
> 
> 
> I noticed a regression on Tegra124 Jetson TK1 today and I am seeing ...
> 
>  tegra30-i2s 70300000.ahub:i2s@70301100: error -EINVAL: invalid resource (null)
>  tegra30-i2s 70300000.ahub:i2s@70301100: probe with driver tegra30-i2s failed with error -22
> 
> Looks like the first address in the above is missing a 0 and we
> should have 0x70300000 and not 0x7030000.
> 
> Let me know if you want to fix up or what a patch to fix.

Should be fixed now, thanks for reporting this.

Thierry

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

  reply	other threads:[~2026-09-18 12:19 UTC|newest]

Thread overview: 16+ 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-17 20:01   ` Jon Hunter
2026-09-18 12:19     ` Thierry Reding [this message]
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
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=aq0sR4k96fGs1MY-@orome \
    --to=thierry.reding@kernel.org \
    --cc=charan.pedumuru@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.