[GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Thierry Reding]

Hi ARM SoC maintainers,

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

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

for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:

  ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)

Thanks,
Thierry

----------------------------------------------------------------
dt-bindings: Changes for v6.20-rc1

This series updates various DT bindings for Tegra architecture,
primarily focusing on schema validation fixes and new feature
documentation for Tegra234 and Tegra264 SoCs. Key changes include
correcting realtek,rt5640 audio codec bindings (adding missing ports,
clocks, and jack-detect sources), converting Tegra20 NAND bindings to
YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
(introducing CMDQV and DBB clock support). Additionally, it resolves
legacy warnings for Tegra30/132 display and VI interfaces.

----------------------------------------------------------------
Ashish Mhetre (1):
      dt-bindings: iommu: Add NVIDIA Tegra CMDQV support

Charan Pedumuru (1):
      dt-bindings: mtd: nvidia,tegra20-nand: convert to DT schema

Jon Hunter (4):
      dt-bindings: tegra: pmc: Update aotag as an optional aperture
      ASoC: dt-bindings: realtek,rt5640: Document mclk
      ASoC: dt-bindings: realtek,rt5640: Update jack-detect
      ASoC: dt-bindings: realtek,rt5640: Document port node

Svyatoslav Ryhel (2):
      dt-bindings: display: tegra: document Tegra132 MIPI calibration device
      dt-bindings: display: tegra: document Tegra30 VI and VIP

Thierry Reding (1):
      dt-bindings: memory: tegra: Document DBB clock for Tegra264

sheetal (1):
      dt-bindings: dma: Update ADMA bindings for tegra264

 .../bindings/arm/tegra/nvidia,tegra186-pmc.yaml    |  11 ++-
 .../display/tegra/nvidia,tegra114-mipi.yaml        |   1 +
 .../bindings/display/tegra/nvidia,tegra20-vi.yaml  |  19 ++--
 .../bindings/display/tegra/nvidia,tegra20-vip.yaml |   9 +-
 .../bindings/dma/nvidia,tegra210-adma.yaml         |  15 ++-
 .../devicetree/bindings/iommu/arm,smmu-v3.yaml     |  27 +++++-
 .../bindings/iommu/nvidia,tegra264-cmdqv.yaml      |  42 +++++++++
 .../memory-controllers/nvidia,tegra186-mc.yaml     |  13 +++
 .../bindings/mtd/nvidia,tegra20-nand.yaml          | 102 +++++++++++++++++++++
 .../bindings/mtd/nvidia-tegra20-nand.txt           |  64 -------------
 .../devicetree/bindings/sound/realtek,rt5640.yaml  |  13 +++
 MAINTAINERS                                        |   2 +-
 12 files changed, 238 insertions(+), 80 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/iommu/nvidia,tegra264-cmdqv.yaml
 create mode 100644 Documentation/devicetree/bindings/mtd/nvidia,tegra20-nand.yaml
 delete mode 100644 Documentation/devicetree/bindings/mtd/nvidia-tegra20-nand.txt

[GIT PULL 2/4] soc/tegra: Changes for v6.20-rc1

[Thierry Reding]

Hi ARM SoC maintainers,

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

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

for you to fetch changes up to 70f752ebb08c85a5ea19471a5aaf26263e53dcb0:

  soc/tegra: pmc: Add PMC contextual functions (2026-01-18 08:48:30 +0100)

Thanks,
Thierry

----------------------------------------------------------------
soc/tegra: Changes for v6.20-rc1

This series primarily refactors the Tegra PMC driver to eliminate
reliance on a global variable, transitioning to passing the tegra_pmc
context explicitly across clocks, powergates, sysfs/debugfs interfaces,
and power management callbacks. Additionally, it resolves a warning
during system resume by deferring an unsafe generic_handle_irq() call to
a hard IRQ context using irq_work.

----------------------------------------------------------------
Prathamesh Shete (1):
      soc/tegra: pmc: Fix unsafe generic_handle_irq() call

Thierry Reding (10):
      soc/tegra: pmc: Use contextual data instead of global variable
      soc/tegra: pmc: Pass struct tegra_pmc to tegra_powergate_state()
      soc/tegra: pmc: Store PMC context in clocks
      soc/tegra: pmc: Embed reboot notifier in PMC context
      soc/tegra: pmc: Pass PMC context via sys-off callback data
      soc/tegra: pmc: Pass PMC context as debugfs data
      soc/tegra: pmc: Use PMC context embedded in powergates
      soc/tegra: pmc: Use driver-private data
      soc/tegra: pmc: Do not rely on global variable
      soc/tegra: pmc: Add PMC contextual functions

 drivers/soc/tegra/pmc.c | 425 ++++++++++++++++++++++++++++++++++++------------
 include/soc/tegra/pmc.h |  60 ++++++-
 2 files changed, 384 insertions(+), 101 deletions(-)

[GIT PULL 3/4] ARM: tegra: Device tree changes for v6.20-rc1

[Thierry Reding]

Hi ARM SoC maintainers,

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

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

for you to fetch changes up to 4d93678236678c4b6b0076fd11f4611a22b7e70b:

  ARM: tegra: Adjust DSI nodes for Tegra20/Tegra30 (2026-01-17 01:18:38 +0100)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Device tree changes for v6.20-rc1

This update corrects the DSI Device Tree nodes for Tegra20 and Tegra30
by adding missing properties (nvidia,mipi-calibrate and cell
definitions) to ensure proper MIPI calibration support.

----------------------------------------------------------------
Svyatoslav Ryhel (1):
      ARM: tegra: Adjust DSI nodes for Tegra20/Tegra30

 arch/arm/boot/dts/nvidia/tegra20.dtsi | 4 ++++
 arch/arm/boot/dts/nvidia/tegra30.dtsi | 8 ++++++++
 2 files changed, 12 insertions(+)

[GIT PULL 4/4] arm64: tegra: Changes for v6.20-rc1

[Thierry Reding]

Hi ARM SoC maintainers,

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

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

for you to fetch changes up to dfa93788dd8b2f9c59adf45ecf592082b1847b7b:

  arm64: tegra: smaug: Add usb-role-switch support (2026-01-17 01:15:26 +0100)

Thanks,
Thierry

----------------------------------------------------------------
arm64: tegra: Changes for v6.20-rc1

This update improves Device Tree support for 64-bit Tegra platforms,
specifically focusing on the Smaug board and the Tegra264 SoC. It
enables full USB-C functionality on Smaug by adding role-switching
support and enabling DisplayPort altmode. For Tegra264, it introduces
nodes for Command Queue Virtualization (CMDQV) in the SMMU, adds the
Data Backbone (DBB) clock for the memory controller, and corrects CPU
compatible strings to match the Neoverse V3AE core. Additionally, it
performs a cleanup by removing redundant status = "okay" properties
across Tegra186, Tegra194, Tegra234, and Tegra264 files.

----------------------------------------------------------------
Ashish Mhetre (1):
      arm64: tegra: Add nodes for CMDQV

Diogo Ivo (3):
      arm64: tegra: smaug: Enable DisplayPort via USB-C port
      arm64: tegra: smaug: Complete and enable tegra-udc node
      arm64: tegra: smaug: Add usb-role-switch support

Krzysztof Kozlowski (5):
      arm64: tegra: Drop unneeded status=okay on Tegra186
      arm64: tegra: Drop unneeded status=okay on Tegra194
      arm64: tegra: Drop unneeded status=okay on Tegra234
      arm64: tegra: Drop unneeded status=okay on Tegra264
      arm64: tegra: Correct CPU compatibles on Tegra264

Thierry Reding (1):
      arm64: tegra: Add DBB clock to EMC on Tegra264

 arch/arm64/boot/dts/nvidia/tegra186.dtsi       |  2 -
 arch/arm64/boot/dts/nvidia/tegra194.dtsi       | 15 ------
 arch/arm64/boot/dts/nvidia/tegra210-smaug.dts  | 25 ++++++++++
 arch/arm64/boot/dts/nvidia/tegra234.dtsi       | 15 ------
 arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi |  8 ++++
 arch/arm64/boot/dts/nvidia/tegra264.dtsi       | 64 ++++++++++++++++++++------
 6 files changed, 83 insertions(+), 46 deletions(-)

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Krzysztof Kozlowski]

On Sun, Jan 18, 2026 at 09:03:00AM +0100, Thierry Reding wrote:
> Hi ARM SoC maintainers,
> 
> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> 
>   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
> 
> for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
> 
>   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> dt-bindings: Changes for v6.20-rc1
> 
> This series updates various DT bindings for Tegra architecture,
> primarily focusing on schema validation fixes and new feature
> documentation for Tegra234 and Tegra264 SoCs. Key changes include
> correcting realtek,rt5640 audio codec bindings (adding missing ports,
> clocks, and jack-detect sources), converting Tegra20 NAND bindings to
> YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
> (introducing CMDQV and DBB clock support). Additionally, it resolves
> legacy warnings for Tegra30/132 display and VI interfaces.

Same comment as was for Geert, I am surprised to see DT bindings as
separate pull and I see drivers were alerady merged, so I will defer
entire Tegra pull to Arnd.

Best regards,
Krzysztof

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Geert Uytterhoeven]

Hi Krzysztof,

On Thu, 22 Jan 2026 at 11:08, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On Sun, Jan 18, 2026 at 09:03:00AM +0100, Thierry Reding wrote:
> > The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> >
> >   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> >
> > are available in the Git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
> >
> > for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
> >
> >   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
> >
> > Thanks,
> > Thierry
> >
> > ----------------------------------------------------------------
> > dt-bindings: Changes for v6.20-rc1
> >
> > This series updates various DT bindings for Tegra architecture,
> > primarily focusing on schema validation fixes and new feature
> > documentation for Tegra234 and Tegra264 SoCs. Key changes include
> > correcting realtek,rt5640 audio codec bindings (adding missing ports,
> > clocks, and jack-detect sources), converting Tegra20 NAND bindings to
> > YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
> > (introducing CMDQV and DBB clock support). Additionally, it resolves
> > legacy warnings for Tegra30/132 display and VI interfaces.
>
> Same comment as was for Geert, I am surprised to see DT bindings as
> separate pull and I see drivers were alerady merged, so I will defer
> entire Tegra pull to Arnd.

The soc tree used to have a separate branch for dt-bindings.
Hence several soc submaintainers still use that split for their PRs.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Thierry Reding]

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

On Thu, Jan 22, 2026 at 12:02:04PM +0100, Geert Uytterhoeven wrote:
> Hi Krzysztof,
> 
> On Thu, 22 Jan 2026 at 11:08, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > On Sun, Jan 18, 2026 at 09:03:00AM +0100, Thierry Reding wrote:
> > > The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> > >
> > >   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> > >
> > > are available in the Git repository at:
> > >
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
> > >
> > > for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
> > >
> > >   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
> > >
> > > Thanks,
> > > Thierry
> > >
> > > ----------------------------------------------------------------
> > > dt-bindings: Changes for v6.20-rc1
> > >
> > > This series updates various DT bindings for Tegra architecture,
> > > primarily focusing on schema validation fixes and new feature
> > > documentation for Tegra234 and Tegra264 SoCs. Key changes include
> > > correcting realtek,rt5640 audio codec bindings (adding missing ports,
> > > clocks, and jack-detect sources), converting Tegra20 NAND bindings to
> > > YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
> > > (introducing CMDQV and DBB clock support). Additionally, it resolves
> > > legacy warnings for Tegra30/132 display and VI interfaces.
> >
> > Same comment as was for Geert, I am surprised to see DT bindings as
> > separate pull and I see drivers were alerady merged, so I will defer
> > entire Tegra pull to Arnd.
> 
> The soc tree used to have a separate branch for dt-bindings.
> Hence several soc submaintainers still use that split for their PRs.

Yeah. I usually also only put things in the PR for ARM SoC that have no
related driver changes (fixups, conversions, ...) and therefore nobody
else feels responsible for picking up.

Thierry

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

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Krzysztof Kozlowski]

On 22/01/2026 13:20, Thierry Reding wrote:
> On Thu, Jan 22, 2026 at 12:02:04PM +0100, Geert Uytterhoeven wrote:
>> Hi Krzysztof,
>>
>> On Thu, 22 Jan 2026 at 11:08, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>> On Sun, Jan 18, 2026 at 09:03:00AM +0100, Thierry Reding wrote:
>>>> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
>>>>
>>>>   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
>>>>
>>>> are available in the Git repository at:
>>>>
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
>>>>
>>>> for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
>>>>
>>>>   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
>>>>
>>>> Thanks,
>>>> Thierry
>>>>
>>>> ----------------------------------------------------------------
>>>> dt-bindings: Changes for v6.20-rc1
>>>>
>>>> This series updates various DT bindings for Tegra architecture,
>>>> primarily focusing on schema validation fixes and new feature
>>>> documentation for Tegra234 and Tegra264 SoCs. Key changes include
>>>> correcting realtek,rt5640 audio codec bindings (adding missing ports,
>>>> clocks, and jack-detect sources), converting Tegra20 NAND bindings to
>>>> YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
>>>> (introducing CMDQV and DBB clock support). Additionally, it resolves
>>>> legacy warnings for Tegra30/132 display and VI interfaces.
>>>
>>> Same comment as was for Geert, I am surprised to see DT bindings as
>>> separate pull and I see drivers were alerady merged, so I will defer
>>> entire Tegra pull to Arnd.
>>
>> The soc tree used to have a separate branch for dt-bindings.
>> Hence several soc submaintainers still use that split for their PRs.
> 
> Yeah. I usually also only put things in the PR for ARM SoC that have no
> related driver changes (fixups, conversions, ...) and therefore nobody
> else feels responsible for picking up.

Why these are still separate? There are few options here:
1. These were needed by the drivers you sent in pull: should be in that
driver pull. It seems Geert confirmed this was the case with Renesas.
BTW, checkpatch asks for that somewhat - you will have checkpatch
warning of undocumented compatibles and you are not suppose to have such
warnings.

2. These were needed by the new DTS you sent in pull: should be in that
DTS pull.

3. These were not needed by anything yet or they document compatibles
already in the tree: that's the only case I imagine having them on
separate branch. You can take such bindings when subsystem maintainers
do not - they ignore them. 90% of bindings in this pull are not like that!

I will respond to that as well in separate email.

Best regards,
Krzysztof

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Krzysztof Kozlowski]

On 18/01/2026 09:03, Thierry Reding wrote:
> Hi ARM SoC maintainers,
> 
> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> 
>   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
> 
> for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
> 
>   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> dt-bindings: Changes for v6.20-rc1
> 
> This series updates various DT bindings for Tegra architecture,
> primarily focusing on schema validation fixes and new feature
> documentation for Tegra234 and Tegra264 SoCs. Key changes include
> correcting realtek,rt5640 audio codec bindings (adding missing ports,
> clocks, and jack-detect sources), converting Tegra20 NAND bindings to
> YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
> (introducing CMDQV and DBB clock support). Additionally, it resolves
> legacy warnings for Tegra30/132 display and VI interfaces.
> 
> ----------------------------------------------------------------
> Ashish Mhetre (1):
>       dt-bindings: iommu: Add NVIDIA Tegra CMDQV support
> 
> Charan Pedumuru (1):
>       dt-bindings: mtd: nvidia,tegra20-nand: convert to DT schema

This should go via MTD. I think Miquel is not ignoring bindings.

> 
> Jon Hunter (4):
>       dt-bindings: tegra: pmc: Update aotag as an optional aperture

...

>       ASoC: dt-bindings: realtek,rt5640: Document mclk
>       ASoC: dt-bindings: realtek,rt5640: Update jack-detect
>       ASoC: dt-bindings: realtek,rt5640: Document port node

No, Mark always promptly picks up bindings patches, so I do not
understand why these are here. These should go via subsystem maintainer.
> 
> Svyatoslav Ryhel (2):
>       dt-bindings: display: tegra: document Tegra132 MIPI calibration device
>       dt-bindings: display: tegra: document Tegra30 VI and VIP
> 
> Thierry Reding (1):
>       dt-bindings: memory: tegra: Document DBB clock for Tegra264

And this one was never publicly acknowledged that you applied it and
lead to ACTUAL warning/review comment from my side postponing your other
patch.

If you took this patch for DTS, then it must be on the DTS branch BEFORE
the DTS uses it. There is explicit rule about this in writing bindings.
You even sent it like that, look:
https://lore.kernel.org/all/176856655186.139432.6919318227218814446.b4-ty@nvidia.com/
1/3: DT binding
2/3: driver
3/3: DTS

so why a correct posting you would disorganize and break the
bisectability rule by applying binding separate?

> 
> sheetal (1):
>       dt-bindings: dma: Update ADMA bindings for tegra264

Vinod also picks up such bindings. If this is for DTS then should be in
DTS branch.

Best regards,
Krzysztof

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Krzysztof Kozlowski]

On 23/01/2026 08:47, Krzysztof Kozlowski wrote:
> 
>>
>> Jon Hunter (4):
>>       dt-bindings: tegra: pmc: Update aotag as an optional aperture
> 
> ...
> 
>>       ASoC: dt-bindings: realtek,rt5640: Document mclk
>>       ASoC: dt-bindings: realtek,rt5640: Update jack-detect
>>       ASoC: dt-bindings: realtek,rt5640: Document port node
> 
> No, Mark always promptly picks up bindings patches, so I do not
> understand why these are here. These should go via subsystem maintainer.

Heh, and Mark actually did take them on 9th of Jan, so you just
duplicated the patches by taking them one week later. Mark also sends TY
letters so you were notified these are picked up.

Also Rob was fixing the same in separate patchset and Mark also took
these, but then Mark handles the conflicts since its all in his own tree.

These should have never been picked up one week later after Mark to
Tegra soc tree. Please drop.

Best regards,
Krzysztof

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Thierry Reding]

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

On Fri, Jan 23, 2026 at 08:43:44AM +0100, Krzysztof Kozlowski wrote:
> On 22/01/2026 13:20, Thierry Reding wrote:
> > On Thu, Jan 22, 2026 at 12:02:04PM +0100, Geert Uytterhoeven wrote:
> >> Hi Krzysztof,
> >>
> >> On Thu, 22 Jan 2026 at 11:08, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >>> On Sun, Jan 18, 2026 at 09:03:00AM +0100, Thierry Reding wrote:
> >>>> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> >>>>
> >>>>   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> >>>>
> >>>> are available in the Git repository at:
> >>>>
> >>>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
> >>>>
> >>>> for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
> >>>>
> >>>>   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
> >>>>
> >>>> Thanks,
> >>>> Thierry
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> dt-bindings: Changes for v6.20-rc1
> >>>>
> >>>> This series updates various DT bindings for Tegra architecture,
> >>>> primarily focusing on schema validation fixes and new feature
> >>>> documentation for Tegra234 and Tegra264 SoCs. Key changes include
> >>>> correcting realtek,rt5640 audio codec bindings (adding missing ports,
> >>>> clocks, and jack-detect sources), converting Tegra20 NAND bindings to
> >>>> YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
> >>>> (introducing CMDQV and DBB clock support). Additionally, it resolves
> >>>> legacy warnings for Tegra30/132 display and VI interfaces.
> >>>
> >>> Same comment as was for Geert, I am surprised to see DT bindings as
> >>> separate pull and I see drivers were alerady merged, so I will defer
> >>> entire Tegra pull to Arnd.
> >>
> >> The soc tree used to have a separate branch for dt-bindings.
> >> Hence several soc submaintainers still use that split for their PRs.
> > 
> > Yeah. I usually also only put things in the PR for ARM SoC that have no
> > related driver changes (fixups, conversions, ...) and therefore nobody
> > else feels responsible for picking up.
> 
> Why these are still separate? There are few options here:
> 1. These were needed by the drivers you sent in pull: should be in that
> driver pull. It seems Geert confirmed this was the case with Renesas.
> BTW, checkpatch asks for that somewhat - you will have checkpatch
> warning of undocumented compatibles and you are not suppose to have such
> warnings.

Yes, most of the time they'll be in this type of pull request and I
don't usually apply them when they are in this category.

> 2. These were needed by the new DTS you sent in pull: should be in that
> DTS pull.

This happens sometimes. In that case what I will usually do is have them
on a separate branch that is merged into the branch with the DTS changes
so that they are separate but the dependency is explicit.

> 3. These were not needed by anything yet or they document compatibles
> already in the tree: that's the only case I imagine having them on
> separate branch. You can take such bindings when subsystem maintainers
> do not - they ignore them. 90% of bindings in this pull are not like that!

This is typically the majority of patches that end up in the Tegra
dt-bindings branch. It's random assortments of things that nobody seems
to feel responsible for and they concern primarily Tegra, so I consider
the Tegra tree to be the fallback and will vacuum these up.

In this particular case I was heavily relying on Patchwork and missed
that Mark had already applied them. Jon pointed it out to me, and so did
Rob, so I removed them. Unfortunately, I didn't send out an updated PR
in time, so Arnd ended up pulling this into ARM SoC.

Let me check in with Arnd to see if that one PR can be backed out, so we
can iron this out.

Thierry

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

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Thierry Reding]

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

On Fri, Jan 23, 2026 at 08:47:24AM +0100, Krzysztof Kozlowski wrote:
> On 18/01/2026 09:03, Thierry Reding wrote:
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> > 
> >   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings
> > 
> > for you to fetch changes up to b2788f6320722d6059f849f35a77eb082608c627:
> > 
> >   ASoC: dt-bindings: realtek,rt5640: Document port node (2026-01-17 01:58:18 +0100)
> > 
> > Thanks,
> > Thierry
> > 
> > ----------------------------------------------------------------
> > dt-bindings: Changes for v6.20-rc1
> > 
> > This series updates various DT bindings for Tegra architecture,
> > primarily focusing on schema validation fixes and new feature
> > documentation for Tegra234 and Tegra264 SoCs. Key changes include
> > correcting realtek,rt5640 audio codec bindings (adding missing ports,
> > clocks, and jack-detect sources), converting Tegra20 NAND bindings to
> > YAML, and updating memory, DMA, and IOMMU definitions for Tegra264
> > (introducing CMDQV and DBB clock support). Additionally, it resolves
> > legacy warnings for Tegra30/132 display and VI interfaces.
> > 
> > ----------------------------------------------------------------
> > Ashish Mhetre (1):
> >       dt-bindings: iommu: Add NVIDIA Tegra CMDQV support
> > 
> > Charan Pedumuru (1):
> >       dt-bindings: mtd: nvidia,tegra20-nand: convert to DT schema
> 
> This should go via MTD. I think Miquel is not ignoring bindings.

I think this was standalone and hadn't seen any response from MTD, so I
vacuumed it up like I usually do.

> > 
> > Jon Hunter (4):
> >       dt-bindings: tegra: pmc: Update aotag as an optional aperture
> 
> ...
> 
> >       ASoC: dt-bindings: realtek,rt5640: Document mclk
> >       ASoC: dt-bindings: realtek,rt5640: Update jack-detect
> >       ASoC: dt-bindings: realtek,rt5640: Document port node
> 
> No, Mark always promptly picks up bindings patches, so I do not
> understand why these are here. These should go via subsystem maintainer.

There's no clear pattern amongst subsystem maintainers, and given that I
make a final pass towards the end of the -rc5 week, I will usually look
at what patches haven't been picked up yet and apply them, provided that
they have a Reviewed-by/Acked-by from a DT maintainer.

In this case I missed Mark's reply since it was posted to the cover
letter and therefore didn't show up in Patchwork (I don't know if newer
versions of patchwork track this somehow, the instance on ozlabs
certainly doesn't). I'll work on a way to better track this.

> > Svyatoslav Ryhel (2):
> >       dt-bindings: display: tegra: document Tegra132 MIPI calibration device
> >       dt-bindings: display: tegra: document Tegra30 VI and VIP
> > 
> > Thierry Reding (1):
> >       dt-bindings: memory: tegra: Document DBB clock for Tegra264
> 
> And this one was never publicly acknowledged that you applied it and
> lead to ACTUAL warning/review comment from my side postponing your other
> patch.

Sometimes I forget to send out acknowledgements. I haven't found a good
and reliable way to automate this.

> If you took this patch for DTS, then it must be on the DTS branch BEFORE
> the DTS uses it. There is explicit rule about this in writing bindings.
> You even sent it like that, look:
> https://lore.kernel.org/all/176856655186.139432.6919318227218814446.b4-ty@nvidia.com/
> 1/3: DT binding
> 2/3: driver
> 3/3: DTS
> 
> so why a correct posting you would disorganize and break the
> bisectability rule by applying binding separate?

As I explained earlier, I usually do exactly that, except that I keep
the branch separate and pull the dt-bindings branch into the DTS branch
as a dependency. I might have missed the dependency this time.

> 
> > 
> > sheetal (1):
> >       dt-bindings: dma: Update ADMA bindings for tegra264
> 
> Vinod also picks up such bindings. If this is for DTS then should be in
> DTS branch.

Same as for the MTD patch, there were no related DTS or driver changes,
and there was no message that this was applied, so I picked it up while
I was going over the list of pending patches.

Thierry

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

Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1

[Thierry Reding]

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

On Fri, Jan 23, 2026 at 08:52:58AM +0100, Krzysztof Kozlowski wrote:
> On 23/01/2026 08:47, Krzysztof Kozlowski wrote:
> > 
> >>
> >> Jon Hunter (4):
> >>       dt-bindings: tegra: pmc: Update aotag as an optional aperture
> > 
> > ...
> > 
> >>       ASoC: dt-bindings: realtek,rt5640: Document mclk
> >>       ASoC: dt-bindings: realtek,rt5640: Update jack-detect
> >>       ASoC: dt-bindings: realtek,rt5640: Document port node
> > 
> > No, Mark always promptly picks up bindings patches, so I do not
> > understand why these are here. These should go via subsystem maintainer.
> 
> Heh, and Mark actually did take them on 9th of Jan, so you just
> duplicated the patches by taking them one week later. Mark also sends TY
> letters so you were notified these are picked up.
> 
> Also Rob was fixing the same in separate patchset and Mark also took
> these, but then Mark handles the conflicts since its all in his own tree.
> 
> These should have never been picked up one week later after Mark to
> Tegra soc tree. Please drop.

Okay, I'll apologize a third time for this. Sorry for neglecting to
double-check the mailing list and relying solely on Patchwork. I promise
to do better next time.

Thierry

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