Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/7] soc/tegra: Changes for v7.4-rc1
Date: Sat,  3 Oct 2026 11:59:18 +0200	[thread overview]
Message-ID: <20261003095924.1370238-3-thierry.reding@kernel.org> (raw)
In-Reply-To: <20261003095924.1370238-1-thierry.reding@kernel.org>

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

Hi ARM SoC maintainers,

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 4eaed7ea6ab36e1160d660b05551702c36dfed6c:

  soc/tegra: flowctrl: Release OF node reference on error (2026-10-03 00:47:52 +0200)

Thanks,
Thierry

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

Adds various bits of core Tegra SoC support for Tegra410, Tegra264 and
Tegra210-B01. Tegra234 can now be woken up via PCIe. Some references
leak and other fixes round this off.

----------------------------------------------------------------
Aaron Kling (2):
      soc/tegra: fuse: Support revision B01
      soc/tegra: fuse: speedo-tegra210: Support revision B01

Alexandre Hamamdjian (1):
      soc/tegra: pmc: Add Tegra210B01 support

Geert Uytterhoeven (1):
      soc/tegra: pmc: Make sure clk_init_data is fully initialized

Jon Hunter (1):
      soc/tegra: fuse: Add Tegra264 support

Kartik Rajput (1):
      soc/tegra: pmc: Add PMC support for Tegra410

Manikanta Maddireddy (1):
      soc/tegra: pmc: Add PCIe wake event for Tegra234

Thierry Reding (1):
      soc/tegra: cbb: Fix loggger -> logger typo

Yuho Choi (1):
      soc/tegra: flowctrl: Release OF node reference on error

 drivers/soc/tegra/cbb/tegra194-cbb.c     |   2 +-
 drivers/soc/tegra/flowctrl.c             |   7 +-
 drivers/soc/tegra/fuse/fuse-tegra.c      |  12 ++-
 drivers/soc/tegra/fuse/fuse-tegra30.c    | 168 ++++++++++++++++++++++++++++++-
 drivers/soc/tegra/fuse/fuse.h            |   7 +-
 drivers/soc/tegra/fuse/speedo-tegra210.c |  22 +++-
 drivers/soc/tegra/fuse/tegra-apbmisc.c   |  51 ++++++----
 drivers/soc/tegra/pmc.c                  | 165 +++++++++++++++++++++++++++++-
 include/soc/tegra/fuse.h                 |   1 +
 9 files changed, 405 insertions(+), 30 deletions(-)


  parent reply	other threads:[~2026-10-03  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03  9:59 [GIT PULL 1/7] Device tree bindings changes for v7.4-rc1 Thierry Reding
2026-10-03  9:59 ` [GIT PULL 2/7] ARM: Core " Thierry Reding
2026-10-03  9:59 ` Thierry Reding [this message]
2026-10-03  9:59 ` [GIT PULL 4/7] firmware/tegra: Changes " Thierry Reding
2026-10-03  9:59 ` [GIT PULL 5/7] ARM: tegra: " Thierry Reding
2026-10-03  9:59 ` [GIT PULL 6/7] arm64: " Thierry Reding
2026-10-03  9:59 ` [GIT PULL 7/7] arm64: tegra: Default configuration changes " 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=20261003095924.1370238-3-thierry.reding@kernel.org \
    --to=thierry.reding@kernel.org \
    --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 \
    /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