Linux SOC development
 help / color / mirror / Atom feed
From: Thierry Reding <treding@nvidia.com>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] Device tree bindings updates for v6.16-rc1
Date: Fri,  9 May 2025 23:26:00 +0200	[thread overview]
Message-ID: <20250509212604.2849901-1-treding@nvidia.com> (raw)

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

Hi ARM SoC maintainers,

The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:

  Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 0d4d6e699a4acff8d15f83185d269ab59c02107a:

  media: dt-bindings: Document Tegra186 and Tegra194 cec (2025-05-08 23:57:54 +0200)

Thanks,
Thierry

----------------------------------------------------------------
Device tree bindings updates for v6.16-rc1

Convert the legacy interrupt controller (LIC) and APBDMA controller
device tree bindings from freeform text to dt-schema.

Document the ASUS Transformer Pad TF300TL compatible string and add
missing compatible strings for newer generations of the Tegra CEC.

----------------------------------------------------------------
Aaron Kling (1):
      media: dt-bindings: Document Tegra186 and Tegra194 cec

Charan Pedumuru (1):
      dt-bindings: dma: nvidia,tegra20-apbdma: convert text based binding to json schema

Rob Herring (Arm) (1):
      dt-bindings: interrupt-controller: Convert nvidia,tegra20-ictlr to DT schema

Svyatoslav Ryhel (2):
      dt-bindings: arm: tegra: Group Tegra30 based ASUS Transformers
      dt-bindings: arm: tegra: Add Asus Transformer Pad TF300TL

 Documentation/devicetree/bindings/arm/tegra.yaml   | 19 ++---
 .../bindings/dma/nvidia,tegra20-apbdma.txt         | 44 -----------
 .../bindings/dma/nvidia,tegra20-apbdma.yaml        | 90 ++++++++++++++++++++++
 .../interrupt-controller/nvidia,tegra20-ictlr.txt  | 41 ----------
 .../interrupt-controller/nvidia,tegra20-ictlr.yaml | 82 ++++++++++++++++++++
 .../bindings/media/cec/nvidia,tegra114-cec.yaml    | 14 +++-
 6 files changed, 190 insertions(+), 100 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra20-apbdma.txt
 create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra20-apbdma.yaml
 delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt
 create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.yaml

             reply	other threads:[~2025-05-09 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 21:26 Thierry Reding [this message]
2025-05-09 21:26 ` [GIT PULL 2/3] ARM: tegra: Device tree changes for v6.16-rc1 Thierry Reding
2025-05-09 21:26 ` [GIT PULL 3/3] arm64: " Thierry Reding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250509212604.2849901-1-treding@nvidia.com \
    --to=treding@nvidia.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=thierry.reding@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox