[PATCH 0/8] arm64: tegra: Clean up AHUB device tree nodes

Thierry Reding posted 8 patches 3 weeks, 2 days ago
arch/arm/boot/dts/nvidia/tegra124.dtsi   |  16 +-
arch/arm64/boot/dts/nvidia/tegra132.dtsi |  16 +-
arch/arm64/boot/dts/nvidia/tegra186.dtsi |  74 ++---
arch/arm64/boot/dts/nvidia/tegra194.dtsi |  74 ++---
arch/arm64/boot/dts/nvidia/tegra210.dtsi |   2 +-
arch/arm64/boot/dts/nvidia/tegra234.dtsi |  74 ++---
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 494 +++++++++++++++----------------
7 files changed, 364 insertions(+), 386 deletions(-)
[PATCH 0/8] arm64: tegra: Clean up AHUB device tree nodes
Posted by Thierry Reding 3 weeks, 2 days ago
This series was prompted by some discussion on this thread:

  https://lore.kernel.org/linux-tegra/20260705-nvidia-ahub-v3-1-bacb7e05bf68@gmail.com/

In a nutshell, yes, the AHUB can do with #address-cells = <1> and the
corresponding #size-cells = <1> since all of the children are in a
fairly small register region. I suspect the primary reason we stuck to
the #address-cells = <2> was so that the ranges property wasn't
required.

Anyway, this series attempts to rectify this by making the necessary
changes to the #address-cells, #size-cells and ranges properties across
all the impacted boards. After this, the AHUB bindings can simply use a
fixed #address-cells of 1.

On that note, I haven't seen any response from Charan on v3 and there
hasn't been a new revision either, so I'm thinking of adopting that
patch and make the #address-cells change so we can move things forward.

Thierry

Signed-off-by: Thierry Reding <treding@nvidia.com>
---
Thierry Reding (8):
      ARM: tegra: Clean up AHUB on Tegra124
      arm64: tegra: Clean up AHUB on Tegra132
      arm64: tegra: Adjust AHUB range on Tegra210
      arm64: tegra: Clean up AHUB on Tegra186
      arm64: tegra: Clean up AHUB on Tegra194
      arm64: tegra: Clean up AHUB on Tegra234
      arm64: tegra: Clean up AHUB on Tegra264
      arm64: tegra: Clean up some whitespace issues on Tegra264

 arch/arm/boot/dts/nvidia/tegra124.dtsi   |  16 +-
 arch/arm64/boot/dts/nvidia/tegra132.dtsi |  16 +-
 arch/arm64/boot/dts/nvidia/tegra186.dtsi |  74 ++---
 arch/arm64/boot/dts/nvidia/tegra194.dtsi |  74 ++---
 arch/arm64/boot/dts/nvidia/tegra210.dtsi |   2 +-
 arch/arm64/boot/dts/nvidia/tegra234.dtsi |  74 ++---
 arch/arm64/boot/dts/nvidia/tegra264.dtsi | 494 +++++++++++++++----------------
 7 files changed, 364 insertions(+), 386 deletions(-)
---
base-commit: 8b72f6626dc39b9e7e82b2721d4f7c3b86286012
change-id: 20260902-tegra-ahub-dt-cleanup-fa470032ab5a

Best regards,
--  
Thierry Reding <treding@nvidia.com>
Re: (subset) [PATCH 0/8] arm64: tegra: Clean up AHUB device tree nodes
Posted by Thierry Reding 2 weeks, 1 day ago
From: Thierry Reding <treding@nvidia.com>


On Wed, 02 Sep 2026 12:17:36 +0200, Thierry Reding wrote:
> This series was prompted by some discussion on this thread:
> 
>   https://lore.kernel.org/linux-tegra/20260705-nvidia-ahub-v3-1-bacb7e05bf68@gmail.com/
> 
> In a nutshell, yes, the AHUB can do with #address-cells = <1> and the
> corresponding #size-cells = <1> since all of the children are in a
> fairly small register region. I suspect the primary reason we stuck to
> the #address-cells = <2> was so that the ranges property wasn't
> required.
> 
> [...]

Applied, thanks!

[1/8] ARM: tegra: Clean up AHUB on Tegra124
      (no commit info)

Best regards,
-- 
Thierry Reding <treding@nvidia.com>