Linux SOC development
 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/4] soc/tegra: Changes for v7.3-rc1
Date: Sun,  2 Aug 2026 18:51:46 +0200	[thread overview]
Message-ID: <20260802165148.1259649-3-thierry.reding@kernel.org> (raw)
In-Reply-To: <20260802165148.1259649-1-thierry.reding@kernel.org>

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

Hi ARM SoC maintainers,

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 97ffe9cb67ccafb4644f820ef68662217b76c224:

  soc/tegra: Add PM dependency to SOC_TEGRA_PMC Kconfig (2026-07-31 17:56:37 +0200)

Thanks,
Thierry

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

Various small fixes for multi-socket devices, redundant error prints, a
Kconfig dependency as well as a patch to remove FUSE data as an entropy
source.

----------------------------------------------------------------
Jon Hunter (1):
      soc/tegra: pmc: Don't register sys-off handler for multi-socket devices

Kartik Rajput (2):
      soc/tegra: fuse: Do not use fuse data as entropy source
      soc/tegra: fuse: Use device-specific instance in suspend/resume

Pan Chuang (1):
      soc/tegra: cbb: Remove redundant dev_err()

Sasha Levin (1):
      soc/tegra: Add PM dependency to SOC_TEGRA_PMC Kconfig

 drivers/soc/tegra/Kconfig             |  1 +
 drivers/soc/tegra/cbb/tegra194-cbb.c  |  9 ++-------
 drivers/soc/tegra/fuse/fuse-tegra.c   |  5 +++++
 drivers/soc/tegra/fuse/fuse-tegra30.c | 24 ------------------------
 drivers/soc/tegra/pmc.c               | 21 ++++++++++++---------
 5 files changed, 20 insertions(+), 40 deletions(-)

  parent reply	other threads:[~2026-08-02 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 16:51 [GIT PULL 1/4] dt-bindings: Changes for v7.3-rc1 Thierry Reding
2026-08-02 16:51 ` [GIT PULL 2/4] ARM: Core Tegra changes " Thierry Reding
2026-08-02 16:51 ` Thierry Reding [this message]
2026-08-02 16:51 ` [GIT PULL 4/4] arm64: tegra: Device tree " Thierry Reding
2026-08-04 20:20 ` [GIT PULL 1/4] dt-bindings: Changes " patchwork-bot+linux-soc

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=20260802165148.1259649-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