[GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings

for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:

  dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)

Thanks,
Thierry

----------------------------------------------------------------
dt-bindings: Changes for v7.1-rc1

This contains a few conversions to DT schema along with various
additions and fixes to reduce the amount of validation warnings.

Included are also a new binding for the PCIe controller found on
Tegra264 as well as compatible strings for the Jetson AGX Thor
Developer Kit.

----------------------------------------------------------------
Sumit Gupta (1):
      dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings

Svyatoslav Ryhel (1):
      dt-bindings: display: tegra: Document Tegra20 HDMI port

Thierry Reding (9):
      dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
      dt-bindings: phy: tegra-xusb: Document Type C support
      dt-bindings: clock: tegra124-dfll: Convert to json-schema
      dt-bindings: interrupt-controller: tegra: Fix reg entries
      dt-bindings: arm: tegra: Add missing compatible strings
      dt-bindings: phy: tegra: Document Tegra210 USB PHY
      dt-bindings: memory: Add Tegra210 memory controller bindings
      dt-bindings: memory: tegra210: Mark EMC as cooling device
      dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit

 Documentation/devicetree/bindings/arm/tegra.yaml   |  56 +++-
 .../bindings/arm/tegra/nvidia,tegra234-cbb.yaml    |   4 +
 .../bindings/clock/nvidia,tegra124-dfll.txt        | 155 -----------
 .../bindings/clock/nvidia,tegra124-dfll.yaml       | 290 +++++++++++++++++++++
 .../display/tegra/nvidia,tegra20-hdmi.yaml         |  13 +-
 .../interrupt-controller/nvidia,tegra20-ictlr.yaml |  23 +-
 .../memory-controllers/nvidia,tegra210-emc.yaml    |   6 +-
 .../memory-controllers/nvidia,tegra210-mc.yaml     |  77 ++++++
 .../bindings/pci/nvidia,tegra264-pcie.yaml         | 149 +++++++++++
 .../bindings/phy/nvidia,tegra194-xusb-padctl.yaml  |  39 ++-
 .../bindings/phy/nvidia,tegra20-usb-phy.yaml       |   1 +
 11 files changed, 649 insertions(+), 164 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.txt
 create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.yaml
 create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml
 create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml

[GIT PULL 2/7] soc/tegra: Changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-soc

for you to fetch changes up to 4b23febb6b11cd06183bed3d21b87ba7d6a8a1e0:

  MAINTAINERS: Change email address for Thierry Reding (2026-03-28 01:41:07 +0100)

Thanks,
Thierry

----------------------------------------------------------------
soc/tegra: Changes for v7.1-rc1

A number of fixes went into this for the PMC and CBB drivers. The PMC
driver also gains support for Tegra264 and a Kconfig symbol for the
upcoming Tegra238 is added. The various per-generation Kconfig symbols
are now also enabled by default for ARCH_TEGRA in order to reduce the
number of configuration options that need to be explicitly enabled.

----------------------------------------------------------------
Jon Hunter (10):
      soc/tegra: pmc: Add kerneldoc for reboot notifier
      soc/tegra: pmc: Correct function names in kerneldoc
      soc/tegra: pmc: Add kerneldoc for wake-up variables
      soc/tegra: pmc: Remove unused AOWAKE definitions
      soc/tegra: pmc: Add support for SoC specific AOWAKE offsets
      soc/tegra: pmc: Add AOWAKE regs for Tegra264
      soc/tegra: pmc: Add Tegra264 wake events
      soc/tegra: pmc: Refactor IO pad voltage control
      soc/tegra: pmc: Rename has_impl_33v_pwr flag
      soc/tegra: pmc: Add IO pads for Tegra264

Krzysztof Kozlowski (1):
      soc/tegra: Make ARCH_TEGRA_SOC_FOO defaults for NVIDIA Tegra

Sumit Gupta (4):
      soc/tegra: cbb: Add support for CBB fabrics in Tegra238
      soc/tegra: cbb: Set ERD on resume for err interrupt
      soc/tegra: cbb: Fix incorrect ARRAY_SIZE in fabric lookup tables
      soc/tegra: cbb: Fix cross-fabric target timeout lookup

Svyatoslav Ryhel (2):
      soc/tegra: pmc: Enable core domain support for Tegra114
      soc/tegra: common: Add Tegra114 support to devm_tegra_core_dev_init_opp_table

Thierry Reding (2):
      soc/tegra: Add Tegra238 Kconfig symbol
      MAINTAINERS: Change email address for Thierry Reding

 MAINTAINERS                          |  14 +-
 drivers/soc/tegra/Kconfig            |  20 ++
 drivers/soc/tegra/cbb/tegra234-cbb.c | 169 ++++++++-
 drivers/soc/tegra/common.c           |   5 +-
 drivers/soc/tegra/pmc.c              | 662 ++++++++++++++++++++++-------------
 5 files changed, 611 insertions(+), 259 deletions(-)

[GIT PULL 3/7] firmware: tegra: Changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-firmware

for you to fetch changes up to e68d494b8946e9060e60427f365107194f90ba0d:

  soc/tegra: bpmp: Use ENODEV instead of ENOTSUPP (2026-03-27 16:30:54 +0100)

Thanks,
Thierry

----------------------------------------------------------------
firmware: tegra: Changes for v7.1-rc1

This introduces a new API for the BPMP to be pass along a specifier from
DT when getting a reference from a phandle. This is used to reference
specific instances of the PCI controller on Tegra264. The ABI header for
BPMP is updated to the latest version and BPMP APIs now use the more
intuitive ENODEV instead of the non SUSV4 ENOTSUPP error code for stub
implementations.

----------------------------------------------------------------
Thierry Reding (4):
      firmware: tegra: bpmp: Rename Tegra239 to Tegra238
      soc/tegra: Update BPMP ABI header
      firmware: tegra: bpmp: Add tegra_bpmp_get_with_id() function
      soc/tegra: bpmp: Use ENODEV instead of ENOTSUPP

 drivers/firmware/tegra/bpmp.c |   34 +
 include/soc/tegra/bpmp-abi.h  | 4573 +++++++++++++++++++++++++++++++++--------
 include/soc/tegra/bpmp.h      |   20 +-
 3 files changed, 3725 insertions(+), 902 deletions(-)

[GIT PULL 4/7] ARM: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm-dt

for you to fetch changes up to ce74a6c6d88ba9ee29a6b99ac97ffcded577c85d:

  ARM: tegra: paz00: Configure WiFi rfkill switch through device tree (2026-03-28 00:56:36 +0100)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Device tree changes for v7.1-rc1

Various improvements for Tegra114 boards, as well as some legacy cleanup
for PAZ00 and Transformers devices.

----------------------------------------------------------------
Dmitry Torokhov (1):
      ARM: tegra: paz00: Configure WiFi rfkill switch through device tree

Svyatoslav Ryhel (8):
      ARM: tegra: Add SOCTHERM support on Tegra114
      ARM: tn7: Adjust panel node
      ARM: tegra: lg-x3: Add panel and bridge nodes
      ARM: tegra: lg-x3: Add USB and power related nodes
      ARM: tegra: lg-x3: Add node for capacitive buttons
      ARM: tegra: Add ACTMON node to Tegra114 device tree
      ARM: tegra: Add External Memory Controller node on Tegra114
      ARM: tegra: transformers: Add connector node

 arch/arm/boot/dts/nvidia/tegra114-tn7.dts        |  13 +-
 arch/arm/boot/dts/nvidia/tegra114.dtsi           | 221 +++++++++++++++++++++++
 arch/arm/boot/dts/nvidia/tegra20-paz00.dts       |   8 +
 arch/arm/boot/dts/nvidia/tegra30-asus-tf600t.dts |  21 ++-
 arch/arm/boot/dts/nvidia/tegra30-lg-p880.dts     |  23 +++
 arch/arm/boot/dts/nvidia/tegra30-lg-p895.dts     |  33 ++++
 arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi      | 174 +++++++++++++++++-
 arch/arm/mach-tegra/Makefile                     |   2 -
 arch/arm/mach-tegra/board-paz00.c                |  56 ------
 arch/arm/mach-tegra/board.h                      |   2 -
 arch/arm/mach-tegra/tegra.c                      |   4 -
 11 files changed, 482 insertions(+), 75 deletions(-)
 delete mode 100644 arch/arm/mach-tegra/board-paz00.c

Re: [GIT PULL 4/7] ARM: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 29/03/2026 17:10, Thierry Reding wrote:
> ----------------------------------------------------------------
> ARM: tegra: Device tree changes for v7.1-rc1
> 
> Various improvements for Tegra114 boards, as well as some legacy cleanup
> for PAZ00 and Transformers devices.
> 
> ----------------------------------------------------------------
> Dmitry Torokhov (1):
>       ARM: tegra: paz00: Configure WiFi rfkill switch through device tree
> 
> Svyatoslav Ryhel (8):
>       ARM: tegra: Add SOCTHERM support on Tegra114
>       ARM: tn7: Adjust panel node
>       ARM: tegra: lg-x3: Add panel and bridge nodes
>       ARM: tegra: lg-x3: Add USB and power related nodes
>       ARM: tegra: lg-x3: Add node for capacitive buttons
>       ARM: tegra: Add ACTMON node to Tegra114 device tree
>       ARM: tegra: Add External Memory Controller node on Tegra114
>       ARM: tegra: transformers: Add connector node
> 
>  arch/arm/boot/dts/nvidia/tegra114-tn7.dts        |  13 +-
>  arch/arm/boot/dts/nvidia/tegra114.dtsi           | 221 +++++++++++++++++++++++
>  arch/arm/boot/dts/nvidia/tegra20-paz00.dts       |   8 +
>  arch/arm/boot/dts/nvidia/tegra30-asus-tf600t.dts |  21 ++-
>  arch/arm/boot/dts/nvidia/tegra30-lg-p880.dts     |  23 +++
>  arch/arm/boot/dts/nvidia/tegra30-lg-p895.dts     |  33 ++++
>  arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi      | 174 +++++++++++++++++-
>  arch/arm/mach-tegra/Makefile                     |   2 -
>  arch/arm/mach-tegra/board-paz00.c                |  56 ------
>  arch/arm/mach-tegra/board.h                      |   2 -
>  arch/arm/mach-tegra/tegra.c                      |   4 -

Why does the DTS branch has mach code? Tag message mentions legacy
cleanup only and such cleanup should not cause mixing independent
hardware description (DTS) with drivers.

Best regards,
Krzysztof

Re: [GIT PULL 4/7] ARM: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

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

On Mon, Mar 30, 2026 at 01:46:32PM +0200, Krzysztof Kozlowski wrote:
> On 29/03/2026 17:10, Thierry Reding wrote:
> > ----------------------------------------------------------------
> > ARM: tegra: Device tree changes for v7.1-rc1
> > 
> > Various improvements for Tegra114 boards, as well as some legacy cleanup
> > for PAZ00 and Transformers devices.
> > 
> > ----------------------------------------------------------------
> > Dmitry Torokhov (1):
> >       ARM: tegra: paz00: Configure WiFi rfkill switch through device tree
> > 
> > Svyatoslav Ryhel (8):
> >       ARM: tegra: Add SOCTHERM support on Tegra114
> >       ARM: tn7: Adjust panel node
> >       ARM: tegra: lg-x3: Add panel and bridge nodes
> >       ARM: tegra: lg-x3: Add USB and power related nodes
> >       ARM: tegra: lg-x3: Add node for capacitive buttons
> >       ARM: tegra: Add ACTMON node to Tegra114 device tree
> >       ARM: tegra: Add External Memory Controller node on Tegra114
> >       ARM: tegra: transformers: Add connector node
> > 
> >  arch/arm/boot/dts/nvidia/tegra114-tn7.dts        |  13 +-
> >  arch/arm/boot/dts/nvidia/tegra114.dtsi           | 221 +++++++++++++++++++++++
> >  arch/arm/boot/dts/nvidia/tegra20-paz00.dts       |   8 +
> >  arch/arm/boot/dts/nvidia/tegra30-asus-tf600t.dts |  21 ++-
> >  arch/arm/boot/dts/nvidia/tegra30-lg-p880.dts     |  23 +++
> >  arch/arm/boot/dts/nvidia/tegra30-lg-p895.dts     |  33 ++++
> >  arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi      | 174 +++++++++++++++++-
> >  arch/arm/mach-tegra/Makefile                     |   2 -
> >  arch/arm/mach-tegra/board-paz00.c                |  56 ------
> >  arch/arm/mach-tegra/board.h                      |   2 -
> >  arch/arm/mach-tegra/tegra.c                      |   4 -
> 
> Why does the DTS branch has mach code? Tag message mentions legacy
> cleanup only and such cleanup should not cause mixing independent
> hardware description (DTS) with drivers.

The DT additions for PAZ00 replace the legacy code, so it makes sense to
replace it in one patch, otherwise we'd be introducing a bisectability
problem.

Thierry

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

Re: [GIT PULL 4/7] ARM: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 31/03/2026 09:38, Thierry Reding wrote:
>> Why does the DTS branch has mach code? Tag message mentions legacy
>> cleanup only and such cleanup should not cause mixing independent
>> hardware description (DTS) with drivers.
> 
> The DT additions for PAZ00 replace the legacy code, so it makes sense to
> replace it in one patch, otherwise we'd be introducing a bisectability
> problem.

OK, please mention it in the tag message in the future.

Best regards,
Krzysztof

Re: [GIT PULL 4/7] ARM: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On Sun, Mar 29, 2026 at 05:10:41PM +0200, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm-dt
> 
> for you to fetch changes up to ce74a6c6d88ba9ee29a6b99ac97ffcded577c85d:
> 
>   ARM: tegra: paz00: Configure WiFi rfkill switch through device tree (2026-03-28 00:56:36 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> ARM: tegra: Device tree changes for v7.1-rc1
> 
> Various improvements for Tegra114 boards, as well as some legacy cleanup
> for PAZ00 and Transformers devices.
> 

Thanks, applied

Best regards,
Krzysztof

[GIT PULL 5/7] ARM: tegra: Default configuration changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm-defconfig

for you to fetch changes up to 21e380f272415387454d81788f2d62642e1fe93a:

  ARM: tegra: defconfig: Drop redundant ARCH_TEGRA_foo_SOC (2026-03-25 10:49:00 +0100)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Default configuration changes for v7.1-rc1

Drop the various ARCH_TEGRA_*_SOC options from the default configurations
since they are now enabled by default for ARCH_TEGRA.

----------------------------------------------------------------
Krzysztof Kozlowski (2):
      soc/tegra: Make ARCH_TEGRA_SOC_FOO defaults for NVIDIA Tegra
      ARM: tegra: defconfig: Drop redundant ARCH_TEGRA_foo_SOC

Thierry Reding (1):
      Merge branch 'for-7.1/soc' into for-7.1/arm/defconfig

 arch/arm/configs/multi_v7_defconfig |  4 ----
 arch/arm/configs/tegra_defconfig    |  4 ----
 drivers/soc/tegra/Kconfig           | 11 +++++++++++
 3 files changed, 11 insertions(+), 8 deletions(-)

[GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt

for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:

  arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)

Thanks,
Thierry

----------------------------------------------------------------
arm64: tegra: Device tree changes for v7.1-rc1

Various fixes and new additions across a number of devices. GPIO and PCI
are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
it to boot via network and mass storage.

----------------------------------------------------------------
Diogo Ivo (1):
      arm64: tegra: smaug: Enable SPI-NOR flash

Jon Hunter (1):
      arm64: tegra: Fix RTC aliases

Prathamesh Shete (1):
      arm64: tegra: Add Tegra264 GPIO controllers

Thierry Reding (6):
      dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
      Merge branch for-7.1/dt-bindings into for-7.1/pci
      arm64: tegra: Fix snps,blen properties
      arm64: tegra: Drop redundant clock and reset names for TSEC
      arm64: tegra: Add PCI controllers on Tegra264
      arm64: tegra: Add Jetson AGX Thor Developer Kit support

 .../bindings/pci/nvidia,tegra264-pcie.yaml         | 149 +++++++++
 arch/arm64/boot/dts/nvidia/Makefile                |   2 +
 arch/arm64/boot/dts/nvidia/tegra210-smaug.dts      |  12 +
 arch/arm64/boot/dts/nvidia/tegra210.dtsi           |   2 -
 arch/arm64/boot/dts/nvidia/tegra234-p3701.dtsi     |   1 +
 arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi     |   1 +
 arch/arm64/boot/dts/nvidia/tegra234.dtsi           |   6 +-
 .../dts/nvidia/tegra264-p4071-0000+p3834-0008.dts  |  11 +
 .../boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi |  12 +
 arch/arm64/boot/dts/nvidia/tegra264.dtsi           | 336 +++++++++++++++++++--
 10 files changed, 500 insertions(+), 32 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
 create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834-0008.dts
 create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 29/03/2026 17:10, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
> 
> for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
> 
>   arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> arm64: tegra: Device tree changes for v7.1-rc1
> 
> Various fixes and new additions across a number of devices. GPIO and PCI
> are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
> it to boot via network and mass storage.
> 
> ----------------------------------------------------------------
> Diogo Ivo (1):
>       arm64: tegra: smaug: Enable SPI-NOR flash
> 
> Jon Hunter (1):
>       arm64: tegra: Fix RTC aliases
> 
> Prathamesh Shete (1):
>       arm64: tegra: Add Tegra264 GPIO controllers
> 
> Thierry Reding (6):
>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller


This is unreviewed/unacked binding where PCI maintainers had 1 day to
react to your v3. Maybe they had more time for previous versions, but
nevertheless it is also part of other patchset, so it will get into the
kernel other tree and nothing on v3 posting:
https://lore.kernel.org/all/20260326135855.2795149-4-thierry.reding@kernel.org/
gives hints that there will be cross tree merge.

So no, that branch cannot be taken.

Please get your code first reviewed with subsystem maintainers.

Best regards,
Krzysztof

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

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

On Mon, Mar 30, 2026 at 01:45:24PM +0200, Krzysztof Kozlowski wrote:
> On 29/03/2026 17:10, Thierry Reding wrote:
> > From: Thierry Reding <thierry.reding@gmail.com>
> > 
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> > 
> >   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
> > 
> > for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
> > 
> >   arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
> > 
> > Thanks,
> > Thierry
> > 
> > ----------------------------------------------------------------
> > arm64: tegra: Device tree changes for v7.1-rc1
> > 
> > Various fixes and new additions across a number of devices. GPIO and PCI
> > are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
> > it to boot via network and mass storage.
> > 
> > ----------------------------------------------------------------
> > Diogo Ivo (1):
> >       arm64: tegra: smaug: Enable SPI-NOR flash
> > 
> > Jon Hunter (1):
> >       arm64: tegra: Fix RTC aliases
> > 
> > Prathamesh Shete (1):
> >       arm64: tegra: Add Tegra264 GPIO controllers
> > 
> > Thierry Reding (6):
> >       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
> 
> 
> This is unreviewed/unacked binding where PCI maintainers had 1 day to
> react to your v3.

Rob gave a reviewed-by on this about a week ago:

  https://lore.kernel.org/linux-tegra/177440189257.2451552.18196101830235626115.robh@kernel.org/

In my experience the PCI maintainers typically defer review of the DT
bindings to DT maintainers, so I considered Rob's R-b sufficient.

>                   Maybe they had more time for previous versions, but
> nevertheless it is also part of other patchset, so it will get into the
> kernel other tree and nothing on v3 posting:
> https://lore.kernel.org/all/20260326135855.2795149-4-thierry.reding@kernel.org/
> gives hints that there will be cross tree merge.

Maybe look at the cover letter:

  https://lore.kernel.org/all/20260326135855.2795149-1-thierry.reding@kernel.org/

I clearly pointed out the build dependencies and suggested a shared
branch to resolve them in both trees. Given that the bindings were
reviewed by Rob and they are needed in both the subsystem tree
(according to your own rules) as well as the DT tree (for validation),
I included the bindings in the shared branch as well.

Thierry

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

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 31/03/2026 09:53, Thierry Reding wrote:
> On Mon, Mar 30, 2026 at 01:45:24PM +0200, Krzysztof Kozlowski wrote:
>> On 29/03/2026 17:10, Thierry Reding wrote:
>>> From: Thierry Reding <thierry.reding@gmail.com>
>>>
>>> Hi ARM SoC maintainers,
>>>
>>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>>
>>>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>>
>>> are available in the Git repository at:
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
>>>
>>> for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
>>>
>>>   arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
>>>
>>> Thanks,
>>> Thierry
>>>
>>> ----------------------------------------------------------------
>>> arm64: tegra: Device tree changes for v7.1-rc1
>>>
>>> Various fixes and new additions across a number of devices. GPIO and PCI
>>> are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
>>> it to boot via network and mass storage.
>>>
>>> ----------------------------------------------------------------
>>> Diogo Ivo (1):
>>>       arm64: tegra: smaug: Enable SPI-NOR flash
>>>
>>> Jon Hunter (1):
>>>       arm64: tegra: Fix RTC aliases
>>>
>>> Prathamesh Shete (1):
>>>       arm64: tegra: Add Tegra264 GPIO controllers
>>>
>>> Thierry Reding (6):
>>>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
>>
>>
>> This is unreviewed/unacked binding where PCI maintainers had 1 day to
>> react to your v3.
> 
> Rob gave a reviewed-by on this about a week ago:
> 
>   https://lore.kernel.org/linux-tegra/177440189257.2451552.18196101830235626115.robh@kernel.org/

Rob, although knows a lot about PCI, is not a formally a PCI subsystem
maintainer.

> 
> In my experience the PCI maintainers typically defer review of the DT
> bindings to DT maintainers, so I considered Rob's R-b sufficient.

Sure and they acknowledge this, that review is done and patch can go
other way, with "Ack".

Where is the Ack?

> 
>>                   Maybe they had more time for previous versions, but
>> nevertheless it is also part of other patchset, so it will get into the
>> kernel other tree and nothing on v3 posting:
>> https://lore.kernel.org/all/20260326135855.2795149-4-thierry.reding@kernel.org/
>> gives hints that there will be cross tree merge.
> 
> Maybe look at the cover letter:
> 
>   https://lore.kernel.org/all/20260326135855.2795149-1-thierry.reding@kernel.org/
> 
> I clearly pointed out the build dependencies and suggested a shared
> branch to resolve them in both trees. Given that the bindings were

No problem, that's a valid solution. Can you point me with a lore link
to the shared branch posting (these tags/pull requests must be posted on
the lists)? Or to an ack from PCI maintainers?

The commit itself does not have an Ack, but maybe was just missed.

> reviewed by Rob and they are needed in both the subsystem tree
> (according to your own rules) as well as the DT tree (for validation),
> I included the bindings in the shared branch as well.



Best regards,
Krzysztof

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

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

On Tue, Mar 31, 2026 at 10:00:01AM +0200, Krzysztof Kozlowski wrote:
> On 31/03/2026 09:53, Thierry Reding wrote:
> > On Mon, Mar 30, 2026 at 01:45:24PM +0200, Krzysztof Kozlowski wrote:
> >> On 29/03/2026 17:10, Thierry Reding wrote:
> >>> From: Thierry Reding <thierry.reding@gmail.com>
> >>>
> >>> Hi ARM SoC maintainers,
> >>>
> >>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> >>>
> >>>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> >>>
> >>> are available in the Git repository at:
> >>>
> >>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
> >>>
> >>> for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
> >>>
> >>>   arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
> >>>
> >>> Thanks,
> >>> Thierry
> >>>
> >>> ----------------------------------------------------------------
> >>> arm64: tegra: Device tree changes for v7.1-rc1
> >>>
> >>> Various fixes and new additions across a number of devices. GPIO and PCI
> >>> are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
> >>> it to boot via network and mass storage.
> >>>
> >>> ----------------------------------------------------------------
> >>> Diogo Ivo (1):
> >>>       arm64: tegra: smaug: Enable SPI-NOR flash
> >>>
> >>> Jon Hunter (1):
> >>>       arm64: tegra: Fix RTC aliases
> >>>
> >>> Prathamesh Shete (1):
> >>>       arm64: tegra: Add Tegra264 GPIO controllers
> >>>
> >>> Thierry Reding (6):
> >>>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
> >>
> >>
> >> This is unreviewed/unacked binding where PCI maintainers had 1 day to
> >> react to your v3.
> > 
> > Rob gave a reviewed-by on this about a week ago:
> > 
> >   https://lore.kernel.org/linux-tegra/177440189257.2451552.18196101830235626115.robh@kernel.org/
> 
> Rob, although knows a lot about PCI, is not a formally a PCI subsystem
> maintainer.
> 
> > 
> > In my experience the PCI maintainers typically defer review of the DT
> > bindings to DT maintainers, so I considered Rob's R-b sufficient.
> 
> Sure and they acknowledge this, that review is done and patch can go
> other way, with "Ack".

No they don't. The vast majority of the PCI DT bindings patches are
indeed applied by the PCI maintainers, but for those that aren't (there
are, admittedly, only a handful over the last few years) there were no
Acked-bys from the PCI maintainers.

> Where is the Ack?

Again, this is where your rules start to fail to meet demands. As it is,
the only option that we have is to get DT and drivers merged, then wait
for an entire cycle before we can merge the DT parts, otherwise we break
DT validation.

> > 
> >>                   Maybe they had more time for previous versions, but
> >> nevertheless it is also part of other patchset, so it will get into the
> >> kernel other tree and nothing on v3 posting:
> >> https://lore.kernel.org/all/20260326135855.2795149-4-thierry.reding@kernel.org/
> >> gives hints that there will be cross tree merge.
> > 
> > Maybe look at the cover letter:
> > 
> >   https://lore.kernel.org/all/20260326135855.2795149-1-thierry.reding@kernel.org/
> > 
> > I clearly pointed out the build dependencies and suggested a shared
> > branch to resolve them in both trees. Given that the bindings were
> 
> No problem, that's a valid solution. Can you point me with a lore link
> to the shared branch posting (these tags/pull requests must be posted on
> the lists)? Or to an ack from PCI maintainers?
> 
> The commit itself does not have an Ack, but maybe was just missed.

Yes, the DT bindings patch does not have an Acked-by, but again, I
didn't think that was necessary, especially since we were going to have
a cross-merge anyway.

Here's the PR for PCI:

	https://lore.kernel.org/linux-tegra/20260329155040.1448158-1-thierry.reding@kernel.org/

Thierry

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

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 31/03/2026 10:43, Thierry Reding wrote:
>>>>                   Maybe they had more time for previous versions, but
>>>> nevertheless it is also part of other patchset, so it will get into the
>>>> kernel other tree and nothing on v3 posting:
>>>> https://lore.kernel.org/all/20260326135855.2795149-4-thierry.reding@kernel.org/
>>>> gives hints that there will be cross tree merge.
>>>
>>> Maybe look at the cover letter:
>>>
>>>   https://lore.kernel.org/all/20260326135855.2795149-1-thierry.reding@kernel.org/
>>>
>>> I clearly pointed out the build dependencies and suggested a shared
>>> branch to resolve them in both trees. Given that the bindings were
>>
>> No problem, that's a valid solution. Can you point me with a lore link
>> to the shared branch posting (these tags/pull requests must be posted on
>> the lists)? Or to an ack from PCI maintainers?
>>
>> The commit itself does not have an Ack, but maybe was just missed.
> 
> Yes, the DT bindings patch does not have an Acked-by, but again, I
> didn't think that was necessary, especially since we were going to have
> a cross-merge anyway.
> 
> Here's the PR for PCI:
> 
> 	https://lore.kernel.org/linux-tegra/20260329155040.1448158-1-thierry.reding@kernel.org/

Thanks, this solves my question. A note in the pull message (not
necessarily in the tag) would also solve it, BTW.

Best regards,
Krzysztof

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 29/03/2026 17:10, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 

I guess related to my question why patches were applied one day after
the list:

Days in linux-next:
----------------------------------------
 0 | ++++++++ (8)

Commits with 0 days in linux-next (8 of 8: 100.0%):
...

So you exposed soc tree to all sort of integration issues. No, please
keep them for some days in the next before you send them to soc, to
allow people to test and eventually complain/report issues.


Best regards,
Krzysztof

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

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

On Tue, Mar 31, 2026 at 09:59:07AM +0200, Krzysztof Kozlowski wrote:
> On 29/03/2026 17:10, Thierry Reding wrote:
> > From: Thierry Reding <thierry.reding@gmail.com>
> > 
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> > 
> >   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> > 
> 
> I guess related to my question why patches were applied one day after
> the list:
> 
> Days in linux-next:
> ----------------------------------------
>  0 | ++++++++ (8)
> 
> Commits with 0 days in linux-next (8 of 8: 100.0%):
> ...
> 
> So you exposed soc tree to all sort of integration issues. No, please
> keep them for some days in the next before you send them to soc, to
> allow people to test and eventually complain/report issues.

Most issues would've been caught by daily bots already. A lot of these
probably were in linux-next but changed SHAs because I rebased them on
top of the PCI bindings patch to keep the shared branch as small as
possible.

I also do fairly extensive build testing on my side before sending those
pull requests, so I don't think I've exposed the SoC tree to an unfair
amount of integration issues.

Thierry

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

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Thierry Reding]

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

On Sun, Mar 29, 2026 at 05:10:43PM +0200, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
> 
> for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
> 
>   arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> arm64: tegra: Device tree changes for v7.1-rc1
> 
> Various fixes and new additions across a number of devices. GPIO and PCI
> are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
> it to boot via network and mass storage.
> 
> ----------------------------------------------------------------
> Diogo Ivo (1):
>       arm64: tegra: smaug: Enable SPI-NOR flash
> 
> Jon Hunter (1):
>       arm64: tegra: Fix RTC aliases
> 
> Prathamesh Shete (1):
>       arm64: tegra: Add Tegra264 GPIO controllers
> 
> Thierry Reding (6):
>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
>       Merge branch for-7.1/dt-bindings into for-7.1/pci
>       arm64: tegra: Fix snps,blen properties
>       arm64: tegra: Drop redundant clock and reset names for TSEC
>       arm64: tegra: Add PCI controllers on Tegra264
>       arm64: tegra: Add Jetson AGX Thor Developer Kit support
> 
>  .../bindings/pci/nvidia,tegra264-pcie.yaml         | 149 +++++++++
>  arch/arm64/boot/dts/nvidia/Makefile                |   2 +
>  arch/arm64/boot/dts/nvidia/tegra210-smaug.dts      |  12 +
>  arch/arm64/boot/dts/nvidia/tegra210.dtsi           |   2 -
>  arch/arm64/boot/dts/nvidia/tegra234-p3701.dtsi     |   1 +
>  arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi     |   1 +
>  arch/arm64/boot/dts/nvidia/tegra234.dtsi           |   6 +-
>  .../dts/nvidia/tegra264-p4071-0000+p3834-0008.dts  |  11 +
>  .../boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi |  12 +
>  arch/arm64/boot/dts/nvidia/tegra264.dtsi           | 336 +++++++++++++++++++--
>  10 files changed, 500 insertions(+), 32 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
>  create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834-0008.dts
>  create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi

Hi ARM SoC maintainers,

DT maintainers objected to the way I wanted to handle the DT bindings
dependency here, so I'll drop the whole PCI stuff from this and redo the
PR.

Thierry

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

Re: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1

[Krzysztof Kozlowski]

On 02/04/2026 14:02, Thierry Reding wrote:
> On Sun, Mar 29, 2026 at 05:10:43PM +0200, Thierry Reding wrote:
>> From: Thierry Reding <thierry.reding@gmail.com>
>>
>> Hi ARM SoC maintainers,
>>
>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>
>>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
>>
>> for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
>>
>>   arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
>>
>> Thanks,
>> Thierry
>>
>> ----------------------------------------------------------------
>> arm64: tegra: Device tree changes for v7.1-rc1
>>
>> Various fixes and new additions across a number of devices. GPIO and PCI
>> are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
>> it to boot via network and mass storage.
>>
>> ----------------------------------------------------------------
>> Diogo Ivo (1):
>>       arm64: tegra: smaug: Enable SPI-NOR flash
>>
>> Jon Hunter (1):
>>       arm64: tegra: Fix RTC aliases
>>
>> Prathamesh Shete (1):
>>       arm64: tegra: Add Tegra264 GPIO controllers
>>
>> Thierry Reding (6):
>>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
>>       Merge branch for-7.1/dt-bindings into for-7.1/pci
>>       arm64: tegra: Fix snps,blen properties
>>       arm64: tegra: Drop redundant clock and reset names for TSEC
>>       arm64: tegra: Add PCI controllers on Tegra264
>>       arm64: tegra: Add Jetson AGX Thor Developer Kit support
>>
>>  .../bindings/pci/nvidia,tegra264-pcie.yaml         | 149 +++++++++
>>  arch/arm64/boot/dts/nvidia/Makefile                |   2 +
>>  arch/arm64/boot/dts/nvidia/tegra210-smaug.dts      |  12 +
>>  arch/arm64/boot/dts/nvidia/tegra210.dtsi           |   2 -
>>  arch/arm64/boot/dts/nvidia/tegra234-p3701.dtsi     |   1 +
>>  arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi     |   1 +
>>  arch/arm64/boot/dts/nvidia/tegra234.dtsi           |   6 +-
>>  .../dts/nvidia/tegra264-p4071-0000+p3834-0008.dts  |  11 +
>>  .../boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi |  12 +
>>  arch/arm64/boot/dts/nvidia/tegra264.dtsi           | 336 +++++++++++++++++++--
>>  10 files changed, 500 insertions(+), 32 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
>>  create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834-0008.dts
>>  create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi
> 
> Hi ARM SoC maintainers,
> 
> DT maintainers objected to the way I wanted to handle the DT bindings
> dependency here, so I'll drop the whole PCI stuff from this and redo the
> PR.

It took me ages to get that information from you but finally you pointed
me that this is shared with PCI, so it is fine.

Best regards,
Krzysztof

[GIT PULL 7/7] arm64: tegra: Default configuration changes for v7.1-rc1

[Thierry Reding]

From: Thierry Reding <thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-defconfig

for you to fetch changes up to c655a14958363aea8a1d0bbf3358fcee7f89a210:

  arm64: tegra: defconfig: Drop redundant ARCH_TEGRA_foo_SOC (2026-03-25 10:49:46 +0100)

Thanks,
Thierry

----------------------------------------------------------------
arm64: tegra: Default configuration changes for v7.1-rc1

Drop the various ARCH_TEGRA_*_SOC options from the default configurations
since they are now enabled by default for ARCH_TEGRA.

----------------------------------------------------------------
Krzysztof Kozlowski (2):
      soc/tegra: Make ARCH_TEGRA_SOC_FOO defaults for NVIDIA Tegra
      arm64: tegra: defconfig: Drop redundant ARCH_TEGRA_foo_SOC

Thierry Reding (1):
      Merge branch 'for-7.1/soc' into for-7.1/arm64/defconfig

 arch/arm64/configs/defconfig |  7 -------
 drivers/soc/tegra/Kconfig    | 11 +++++++++++
 2 files changed, 11 insertions(+), 7 deletions(-)

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Krzysztof Kozlowski]

On 29/03/2026 17:10, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings
> 
> for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:
> 
>   dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> dt-bindings: Changes for v7.1-rc1
> 
> This contains a few conversions to DT schema along with various
> additions and fixes to reduce the amount of validation warnings.
> 
> Included are also a new binding for the PCIe controller found on
> Tegra264 as well as compatible strings for the Jetson AGX Thor
> Developer Kit.
> 
> ----------------------------------------------------------------
> Sumit Gupta (1):
>       dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
> 
> Svyatoslav Ryhel (1):
>       dt-bindings: display: tegra: Document Tegra20 HDMI port
> 
> Thierry Reding (9):
>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller

Why are you taking subsystem patches? This was posted on 26th of March
and was not acked by PCI maintainers.

How the bindings should go is already documented, so there is no
question here.

The question was whether you can take them if subsystem maintainer is
non-responsive and yes, you can. You gave PCI maintainers one day before
applying it.


>       dt-bindings: phy: tegra-xusb: Document Type C support

No acks, but that is waiting for one month so it is fine.

>       dt-bindings: clock: tegra124-dfll: Convert to json-schema
>       dt-bindings: interrupt-controller: tegra: Fix reg entries
>       dt-bindings: arm: tegra: Add missing compatible strings
>       dt-bindings: phy: tegra: Document Tegra210 USB PHY
>       dt-bindings: memory: Add Tegra210 memory controller bindings
>       dt-bindings: memory: tegra210: Mark EMC as cooling device

That's even my subsystem and I did not ack it. You did not even sent it
to me as requested by MAINTAINERS file (+dt is ignore alias), so
obviously I did not even had a chance to ack it.

And we even had few days ago talk were I explained you how these
bindings must go. Seeing pull request completely ignoring that
discussion is just huge surprise.

No, it cannot go in. Send patches to proper maintainers first.

Best regards,
Krzysztof

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Krzysztof Kozlowski]

On 30/03/2026 13:39, Krzysztof Kozlowski wrote:
> On 29/03/2026 17:10, Thierry Reding wrote:
>> From: Thierry Reding <thierry.reding@gmail.com>
>>
>> Hi ARM SoC maintainers,
>>
>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>
>>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings
>>
>> for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:
>>
>>   dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)
>>
>> Thanks,
>> Thierry
>>
>> ----------------------------------------------------------------
>> dt-bindings: Changes for v7.1-rc1
>>
>> This contains a few conversions to DT schema along with various
>> additions and fixes to reduce the amount of validation warnings.
>>
>> Included are also a new binding for the PCIe controller found on
>> Tegra264 as well as compatible strings for the Jetson AGX Thor
>> Developer Kit.
>>
>> ----------------------------------------------------------------
>> Sumit Gupta (1):
>>       dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
>>
>> Svyatoslav Ryhel (1):
>>       dt-bindings: display: tegra: Document Tegra20 HDMI port
>>
>> Thierry Reding (9):
>>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
> 
> Why are you taking subsystem patches? This was posted on 26th of March
> and was not acked by PCI maintainers.
> 
> How the bindings should go is already documented, so there is no
> question here.
> 
> The question was whether you can take them if subsystem maintainer is
> non-responsive and yes, you can. You gave PCI maintainers one day before
> applying it.
> 
> 
>>       dt-bindings: phy: tegra-xusb: Document Type C support
> 
> No acks, but that is waiting for one month so it is fine.

Ha, no, you did not even send it to maintainers, so how they could ack it?

Nothing here was sent to the right people.

Best regards,
Krzysztof

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Thierry Reding]

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

On Mon, Mar 30, 2026 at 01:39:49PM +0200, Krzysztof Kozlowski wrote:
> On 29/03/2026 17:10, Thierry Reding wrote:
> > From: Thierry Reding <thierry.reding@gmail.com>
> > 
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> > 
> >   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings
> > 
> > for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:
> > 
> >   dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)
> > 
> > Thanks,
> > Thierry
> > 
> > ----------------------------------------------------------------
> > dt-bindings: Changes for v7.1-rc1
> > 
> > This contains a few conversions to DT schema along with various
> > additions and fixes to reduce the amount of validation warnings.
> > 
> > Included are also a new binding for the PCIe controller found on
> > Tegra264 as well as compatible strings for the Jetson AGX Thor
> > Developer Kit.
> > 
> > ----------------------------------------------------------------
> > Sumit Gupta (1):
> >       dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
> > 
> > Svyatoslav Ryhel (1):
> >       dt-bindings: display: tegra: Document Tegra20 HDMI port
> > 
> > Thierry Reding (9):
> >       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
> 
> Why are you taking subsystem patches? This was posted on 26th of March
> and was not acked by PCI maintainers.
> 
> How the bindings should go is already documented, so there is no
> question here.

We've discussed this in the past and I still think your rule about DT
bindings needing to go in through the driver tree is impractical. Yes,
it means you get around the checkpatch warning about undocumented
compatible strings, but at the expense of a new warning in the Tegra
tree because the bindings aren't there.

> The question was whether you can take them if subsystem maintainer is
> non-responsive and yes, you can. You gave PCI maintainers one day before
> applying it.

I did not get a response to my suggestion about creating a shared
branch, which was included in v1 already. So I went ahead and did what
I thought was best. PCI maintainers are free to not pull this if they
don't want to. I also offered to address any further review comments if
there were any.

> >       dt-bindings: phy: tegra-xusb: Document Type C support
> 
> No acks, but that is waiting for one month so it is fine.

It's got a Reviewed-by from Rob and there were no corresponding driver
changes associated with it. There's literally no reason for this to go
in through a subsystem tree.

> >       dt-bindings: clock: tegra124-dfll: Convert to json-schema
> >       dt-bindings: interrupt-controller: tegra: Fix reg entries
> >       dt-bindings: arm: tegra: Add missing compatible strings
> >       dt-bindings: phy: tegra: Document Tegra210 USB PHY
> >       dt-bindings: memory: Add Tegra210 memory controller bindings
> >       dt-bindings: memory: tegra210: Mark EMC as cooling device
> 
> That's even my subsystem and I did not ack it. You did not even sent it
> to me as requested by MAINTAINERS file (+dt is ignore alias), so
> obviously I did not even had a chance to ack it.

Ugh... really? I was Cc'ed to you as a DT maintainer as well as the
devicetree mailing list, so I'm sure you've seen it. This had also been
reviewed by Rob a long time ago, and honestly, it's also quite trivial.
It's been on the list for a month and there were no objections, so it
does pass all of the criteria you mentioned before.

> And we even had few days ago talk were I explained you how these
> bindings must go. Seeing pull request completely ignoring that
> discussion is just huge surprise.
> 
> No, it cannot go in. Send patches to proper maintainers first.

Stop making these baseless accusations, Krzysztof. You were on Cc and
DT maintainers have seen and reviewed these patches. You're grasping at
straws to somehow try to make my life miserable and I don't know why.

Thierry

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

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Krzysztof Kozlowski]

On 31/03/2026 10:25, Thierry Reding wrote:
> 
>>>       dt-bindings: phy: tegra-xusb: Document Type C support
>>
>> No acks, but that is waiting for one month so it is fine.
> 
> It's got a Reviewed-by from Rob and there were no corresponding driver
> changes associated with it. There's literally no reason for this to go
> in through a subsystem tree.

There are reasons - process and technical:
1. It's a subsystem maintainer's patch, not yours. You rather should
have reason to take someone else's patches.

2. Conflict in that file.


> 
>>>       dt-bindings: clock: tegra124-dfll: Convert to json-schema
>>>       dt-bindings: interrupt-controller: tegra: Fix reg entries
>>>       dt-bindings: arm: tegra: Add missing compatible strings
>>>       dt-bindings: phy: tegra: Document Tegra210 USB PHY
>>>       dt-bindings: memory: Add Tegra210 memory controller bindings
>>>       dt-bindings: memory: tegra210: Mark EMC as cooling device
>>
>> That's even my subsystem and I did not ack it. You did not even sent it
>> to me as requested by MAINTAINERS file (+dt is ignore alias), so
>> obviously I did not even had a chance to ack it.
> 
> Ugh... really? I was Cc'ed to you as a DT maintainer as well as the
> devicetree mailing list, so I'm sure you've seen it. This had also been

Really, you are supposed to use get_maintainers.pl. Not invent the CC
list, not come with own filtered list.

I understand that my non dt address disappears when running
get_maintainers.pl on entire set.

But if you sent that patch targetting subsystem instead of combining 6
or 7 subsystems at once, it would pop up.

And yes, you are not supposed to mix 7 different subsystems in single
patchset. That's basic!

But sure, let's skip memory controllers patch cc list and:

> reviewed by Rob a long time ago, and honestly, it's also quite trivial.
> It's been on the list for a month and there were no objections, so it
> does pass all of the criteria you mentioned before.

No objections because you did not cc people. How can you claim "no
objections from person foo" if you do not cc person "foo", because you
do not use get_maintainers.pl?

Look, find me here phy mantainers:

https://lore.kernel.org/all/20260223143305.3771383-7-thierry.reding@kernel.org/

> 
>> And we even had few days ago talk were I explained you how these
>> bindings must go. Seeing pull request completely ignoring that
>> discussion is just huge surprise.
>>
>> No, it cannot go in. Send patches to proper maintainers first.
> 
> Stop making these baseless accusations, Krzysztof. You were on Cc and

Not using get_maintainers.pl so not ccing right address is not baseless.
This is the fact.

Neither phy, nor interrupts, nor clocks were sent to right people.

You mixed 6 or 7 different subsystems in on patchset, but you call my
remarks as baseless. You use several adjectives "trivial", "baseless",
but no actual facts.

Final commentary:
Stop taking patches from other subsystems, just because you want to
streamline your DTS. You are bypassing other subsystems review, other
people trees, and that's not acceptable.

Best regards,
Krzysztof

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Thierry Reding]

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

On Tue, Mar 31, 2026 at 11:50:18AM +0200, Krzysztof Kozlowski wrote:
> On 31/03/2026 10:25, Thierry Reding wrote:
> > 
> >>>       dt-bindings: phy: tegra-xusb: Document Type C support
> >>
> >> No acks, but that is waiting for one month so it is fine.
> > 
> > It's got a Reviewed-by from Rob and there were no corresponding driver
> > changes associated with it. There's literally no reason for this to go
> > in through a subsystem tree.
> 
> There are reasons - process and technical:
> 1. It's a subsystem maintainer's patch, not yours. You rather should
> have reason to take someone else's patches.
> 
> 2. Conflict in that file.
> 
> 
> > 
> >>>       dt-bindings: clock: tegra124-dfll: Convert to json-schema
> >>>       dt-bindings: interrupt-controller: tegra: Fix reg entries
> >>>       dt-bindings: arm: tegra: Add missing compatible strings
> >>>       dt-bindings: phy: tegra: Document Tegra210 USB PHY
> >>>       dt-bindings: memory: Add Tegra210 memory controller bindings
> >>>       dt-bindings: memory: tegra210: Mark EMC as cooling device
> >>
> >> That's even my subsystem and I did not ack it. You did not even sent it
> >> to me as requested by MAINTAINERS file (+dt is ignore alias), so
> >> obviously I did not even had a chance to ack it.
> > 
> > Ugh... really? I was Cc'ed to you as a DT maintainer as well as the
> > devicetree mailing list, so I'm sure you've seen it. This had also been
> 
> Really, you are supposed to use get_maintainers.pl. Not invent the CC
> list, not come with own filtered list.
> 
> I understand that my non dt address disappears when running
> get_maintainers.pl on entire set.
> 
> But if you sent that patch targetting subsystem instead of combining 6
> or 7 subsystems at once, it would pop up.
> 
> And yes, you are not supposed to mix 7 different subsystems in single
> patchset. That's basic!

Pft... you're being unreasonable. These are all relatively trivial
changes that have at one point or another been already reviewed. Do you
seriously expect me to turn these into 7 different patch series so that
everyone gets to spend even more time dealing with these?

> But sure, let's skip memory controllers patch cc list and:
> 
> > reviewed by Rob a long time ago, and honestly, it's also quite trivial.
> > It's been on the list for a month and there were no objections, so it
> > does pass all of the criteria you mentioned before.
> 
> No objections because you did not cc people. How can you claim "no
> objections from person foo" if you do not cc person "foo", because you
> do not use get_maintainers.pl?
> 
> Look, find me here phy mantainers:
> 
> https://lore.kernel.org/all/20260223143305.3771383-7-thierry.reding@kernel.org/

It's an extremely trivial, one-line change to an existing binding. There
is no interaction with the driver whatsoever, why would anyone outside
of the DT and Tegra maintainers even want to look at this?

> >> And we even had few days ago talk were I explained you how these
> >> bindings must go. Seeing pull request completely ignoring that
> >> discussion is just huge surprise.
> >>
> >> No, it cannot go in. Send patches to proper maintainers first.
> > 
> > Stop making these baseless accusations, Krzysztof. You were on Cc and
> 
> Not using get_maintainers.pl so not ccing right address is not baseless.
> This is the fact.

I use get_maintainers.pl but filter down based on common sense.

> Neither phy, nor interrupts, nor clocks were sent to right people.

Again, these are patches that were all on the list previously, sent to
the right people at the time. They hadn't been picked up by now, so I
resent them, to the DT maintainers only, to give you guys a chance to
object in case there were any new things you were looking for since the
original submissions.

> You mixed 6 or 7 different subsystems in on patchset, but you call my
> remarks as baseless. You use several adjectives "trivial", "baseless",
> but no actual facts.
> 
> Final commentary:
> Stop taking patches from other subsystems, just because you want to
> streamline your DTS. You are bypassing other subsystems review, other
> people trees, and that's not acceptable.

You know, I'll do just that. In fact, I'll just stop working on these
cleanup patches. It's a shame because I really wanted to get off your
wall of shame by this year's LPC, but you're making this needlessly
complicated and I'm out of patience.

Thierry

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

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Krzysztof Kozlowski]

On 31/03/2026 13:09, Thierry Reding wrote:
> On Tue, Mar 31, 2026 at 11:50:18AM +0200, Krzysztof Kozlowski wrote:
>> On 31/03/2026 10:25, Thierry Reding wrote:
>>>
>>>>>       dt-bindings: phy: tegra-xusb: Document Type C support
>>>>
>>>> No acks, but that is waiting for one month so it is fine.
>>>
>>> It's got a Reviewed-by from Rob and there were no corresponding driver
>>> changes associated with it. There's literally no reason for this to go
>>> in through a subsystem tree.
>>
>> There are reasons - process and technical:
>> 1. It's a subsystem maintainer's patch, not yours. You rather should
>> have reason to take someone else's patches.
>>
>> 2. Conflict in that file.
>>
>>
>>>
>>>>>       dt-bindings: clock: tegra124-dfll: Convert to json-schema
>>>>>       dt-bindings: interrupt-controller: tegra: Fix reg entries
>>>>>       dt-bindings: arm: tegra: Add missing compatible strings
>>>>>       dt-bindings: phy: tegra: Document Tegra210 USB PHY
>>>>>       dt-bindings: memory: Add Tegra210 memory controller bindings
>>>>>       dt-bindings: memory: tegra210: Mark EMC as cooling device
>>>>
>>>> That's even my subsystem and I did not ack it. You did not even sent it
>>>> to me as requested by MAINTAINERS file (+dt is ignore alias), so
>>>> obviously I did not even had a chance to ack it.
>>>
>>> Ugh... really? I was Cc'ed to you as a DT maintainer as well as the
>>> devicetree mailing list, so I'm sure you've seen it. This had also been
>>
>> Really, you are supposed to use get_maintainers.pl. Not invent the CC
>> list, not come with own filtered list.
>>
>> I understand that my non dt address disappears when running
>> get_maintainers.pl on entire set.
>>
>> But if you sent that patch targetting subsystem instead of combining 6
>> or 7 subsystems at once, it would pop up.
>>
>> And yes, you are not supposed to mix 7 different subsystems in single
>> patchset. That's basic!
> 
> Pft... you're being unreasonable. These are all relatively trivial
> changes that have at one point or another been already reviewed. Do you
> seriously expect me to turn these into 7 different patch series so that
> everyone gets to spend even more time dealing with these?

That's what everyone else is doing, including Qualcomm which is
upstreaming multiple new SoCs per year, multiple patchsets, multiple
patches.

But no, I do not expect you to split it but I expect to use
get_maintainers.pl, unless that would cause a patchbomb cc-ing 50
addresses (I don't suggest that you created such patchbomb -
hypothetical). Removing maintainers from Cc list is not the way to solve
patchbomb problem, if such arises. Splitting a hypothetical patchbomb
would be the solution.

> 
>> But sure, let's skip memory controllers patch cc list and:
>>
>>> reviewed by Rob a long time ago, and honestly, it's also quite trivial.
>>> It's been on the list for a month and there were no objections, so it
>>> does pass all of the criteria you mentioned before.
>>
>> No objections because you did not cc people. How can you claim "no
>> objections from person foo" if you do not cc person "foo", because you
>> do not use get_maintainers.pl?
>>
>> Look, find me here phy mantainers:
>>
>> https://lore.kernel.org/all/20260223143305.3771383-7-thierry.reding@kernel.org/
> 
> It's an extremely trivial, one-line change to an existing binding. There
> is no interaction with the driver whatsoever, why would anyone outside
> of the DT and Tegra maintainers even want to look at this?

I explained in the beginning why someone could want to look:

1. It's a subsystem maintainer's patch, not yours.

2. Conflict in that file.

But regardless why someone would or would not want, get_maintainers.pl
asked you to Cc them.

> 
>>>> And we even had few days ago talk were I explained you how these
>>>> bindings must go. Seeing pull request completely ignoring that
>>>> discussion is just huge surprise.
>>>>
>>>> No, it cannot go in. Send patches to proper maintainers first.
>>>
>>> Stop making these baseless accusations, Krzysztof. You were on Cc and
>>
>> Not using get_maintainers.pl so not ccing right address is not baseless.
>> This is the fact.
> 
> I use get_maintainers.pl but filter down based on common sense.

Filtering means you don't use. Following this logic (although not
exactly "common sense" but writing bindings point you that common sense
for driver bindings is driver subsystem):
1. I use get_maintainers.pl on my patch.
2. Then I remove all addresses except linux-kernel@vger.kernel.org.
3. All good and I claim I am using get_maintainers.pl.


> 
>> Neither phy, nor interrupts, nor clocks were sent to right people.
> 
> Again, these are patches that were all on the list previously, sent to
> the right people at the time. They hadn't been picked up by now, so I

No, they were not sent to the right people at the time. The right people
at the time are pointed by get_maintainers.pl which you filtered out.

Look again, this is the v1:
https://lore.kernel.org/all/20260223143305.3771383-7-thierry.reding@kernel.org/

Where is any phy maintainer or the phy mailing list Cc-ed?

Instead of again using "baseless" arguments, please provide the actual
fact for that claim that you cc-ed right list and right people on that
patch.

> resent them, to the DT maintainers only, to give you guys a chance to

This is not a resent, this is the v1. Do you see "RESEND" in the
subject? I don't.

I am pointing out the facts now. If you disagree, please point me to the
original posting of phy patch with the 'right' people in CC list, as
requested by get_maintainers.pl.


Best regards,
Krzysztof

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Thierry Reding]

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

On Sun, Mar 29, 2026 at 05:10:38PM +0200, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings
> 
> for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:
> 
>   dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> dt-bindings: Changes for v7.1-rc1
> 
> This contains a few conversions to DT schema along with various
> additions and fixes to reduce the amount of validation warnings.
> 
> Included are also a new binding for the PCIe controller found on
> Tegra264 as well as compatible strings for the Jetson AGX Thor
> Developer Kit.
> 
> ----------------------------------------------------------------
> Sumit Gupta (1):
>       dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
> 
> Svyatoslav Ryhel (1):
>       dt-bindings: display: tegra: Document Tegra20 HDMI port
> 
> Thierry Reding (9):
>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
>       dt-bindings: phy: tegra-xusb: Document Type C support
>       dt-bindings: clock: tegra124-dfll: Convert to json-schema
>       dt-bindings: interrupt-controller: tegra: Fix reg entries
>       dt-bindings: arm: tegra: Add missing compatible strings
>       dt-bindings: phy: tegra: Document Tegra210 USB PHY
>       dt-bindings: memory: Add Tegra210 memory controller bindings
>       dt-bindings: memory: tegra210: Mark EMC as cooling device
>       dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit
> 
>  Documentation/devicetree/bindings/arm/tegra.yaml   |  56 +++-
>  .../bindings/arm/tegra/nvidia,tegra234-cbb.yaml    |   4 +
>  .../bindings/clock/nvidia,tegra124-dfll.txt        | 155 -----------
>  .../bindings/clock/nvidia,tegra124-dfll.yaml       | 290 +++++++++++++++++++++
>  .../display/tegra/nvidia,tegra20-hdmi.yaml         |  13 +-
>  .../interrupt-controller/nvidia,tegra20-ictlr.yaml |  23 +-
>  .../memory-controllers/nvidia,tegra210-emc.yaml    |   6 +-
>  .../memory-controllers/nvidia,tegra210-mc.yaml     |  77 ++++++
>  .../bindings/pci/nvidia,tegra264-pcie.yaml         | 149 +++++++++++
>  .../bindings/phy/nvidia,tegra194-xusb-padctl.yaml  |  39 ++-
>  .../bindings/phy/nvidia,tegra20-usb-phy.yaml       |   1 +
>  11 files changed, 649 insertions(+), 164 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.txt
>  create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.yaml
>  create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml
>  create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml

Hi ARM SoC maintainers,

Please ignore this for now. I'm dropping my set of patches from this
because they upset the DT maintainers. I'll send another version with
only Sumit and Svyatoslav's patches.

Thierry


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

Re: [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1

[Krzysztof Kozlowski]

On 02/04/2026 14:00, Thierry Reding wrote:
> On Sun, Mar 29, 2026 at 05:10:38PM +0200, Thierry Reding wrote:
>> From: Thierry Reding <thierry.reding@gmail.com>
>>
>> Hi ARM SoC maintainers,
>>
>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>
>>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-dt-bindings
>>
>> for you to fetch changes up to bed2f5b4de6c6fd8f8928f6373ad92e8795c370f:
>>
>>   dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit (2026-03-28 01:05:24 +0100)
>>
>> Thanks,
>> Thierry
>>
>> ----------------------------------------------------------------
>> dt-bindings: Changes for v7.1-rc1
>>
>> This contains a few conversions to DT schema along with various
>> additions and fixes to reduce the amount of validation warnings.
>>
>> Included are also a new binding for the PCIe controller found on
>> Tegra264 as well as compatible strings for the Jetson AGX Thor
>> Developer Kit.
>>
>> ----------------------------------------------------------------
>> Sumit Gupta (1):
>>       dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
>>
>> Svyatoslav Ryhel (1):
>>       dt-bindings: display: tegra: Document Tegra20 HDMI port
>>
>> Thierry Reding (9):
>>       dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
>>       dt-bindings: phy: tegra-xusb: Document Type C support
>>       dt-bindings: clock: tegra124-dfll: Convert to json-schema
>>       dt-bindings: interrupt-controller: tegra: Fix reg entries
>>       dt-bindings: arm: tegra: Add missing compatible strings
>>       dt-bindings: phy: tegra: Document Tegra210 USB PHY
>>       dt-bindings: memory: Add Tegra210 memory controller bindings
>>       dt-bindings: memory: tegra210: Mark EMC as cooling device
>>       dt-bindings: arm: tegra: Document Jetson AGX Thor DevKit
>>
>>  Documentation/devicetree/bindings/arm/tegra.yaml   |  56 +++-
>>  .../bindings/arm/tegra/nvidia,tegra234-cbb.yaml    |   4 +
>>  .../bindings/clock/nvidia,tegra124-dfll.txt        | 155 -----------
>>  .../bindings/clock/nvidia,tegra124-dfll.yaml       | 290 +++++++++++++++++++++
>>  .../display/tegra/nvidia,tegra20-hdmi.yaml         |  13 +-
>>  .../interrupt-controller/nvidia,tegra20-ictlr.yaml |  23 +-
>>  .../memory-controllers/nvidia,tegra210-emc.yaml    |   6 +-
>>  .../memory-controllers/nvidia,tegra210-mc.yaml     |  77 ++++++
>>  .../bindings/pci/nvidia,tegra264-pcie.yaml         | 149 +++++++++++
>>  .../bindings/phy/nvidia,tegra194-xusb-padctl.yaml  |  39 ++-
>>  .../bindings/phy/nvidia,tegra20-usb-phy.yaml       |   1 +
>>  11 files changed, 649 insertions(+), 164 deletions(-)
>>  delete mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.txt
>>  create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.yaml
>>  create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml
>>  create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
> 
> Hi ARM SoC maintainers,
> 
> Please ignore this for now. I'm dropping my set of patches from this
> because they upset the DT maintainers. I'll send another version with
> only Sumit and Svyatoslav's patches.

I plan to take this, because rejecting it won't improve anything and
patches seems to be non-conflicting. In the future, please do not filter
out addresses of other maintainers and their lists from
get_maintainers.pl output for patches belonging to their subsystems. If
the patchset becomes 50-Cc-patch-bomb, then standard rule of submitting
patches applies - should be split.


Best regards,
Krzysztof