public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.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 4/8] soc/tegra: Changes for v6.19-rc1
Date: Sat, 15 Nov 2025 10:00:39 +0100	[thread overview]
Message-ID: <20251115090044.3140331-4-thierry.reding@gmail.com> (raw)
In-Reply-To: <20251115090044.3140331-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

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

for you to fetch changes up to dd03d34d6d8e7a3f62450fb7a1408d86fb35487c:

  soc/tegra: pmc: Add USB wake events for Tegra234 (2025-11-14 19:29:50 +0100)

Thanks,
Thierry

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

A couple of small fixes across the board: ACPI support on FUSE no longer
exposes duplicate SoC information, speedo IDs for Tegra210 are updated,
some comments see typo fixes or kerneldoc additions. Finally, support
for USB wake events is added on Tegra234, which allow these systems to
resume from suspend on USB activity.

----------------------------------------------------------------
Aaron Kling (2):
      soc/tegra: fuse: speedo-tegra210: Update speedo IDs
      soc/tegra: fuse: speedo-tegra210: Add SoC speedo 2

Bruno Sobreira França (1):
      soc/tegra: Resolve a spelling error in the tegra194-cbb.c

Haotien Hsu (1):
      soc/tegra: pmc: Add USB wake events for Tegra234

Kartik Rajput (1):
      soc/tegra: fuse: Do not register SoC device on ACPI boot

Prathamesh Shete (1):
      soc/tegra: pmc: Don't fail if "aotag" is not present

Thierry Reding (1):
      soc/tegra: pmc: Document tegra_pmc.syscore field

 drivers/soc/tegra/cbb/tegra194-cbb.c     |  2 +-
 drivers/soc/tegra/fuse/fuse-tegra.c      |  2 --
 drivers/soc/tegra/fuse/speedo-tegra210.c | 57 +++++++++++++++++++++++---------
 drivers/soc/tegra/pmc.c                  | 21 ++++++++++--
 4 files changed, 60 insertions(+), 22 deletions(-)

  parent reply	other threads:[~2025-11-15  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-15  9:00 [GIT PULL 1/8] syscore: Changes for v6.19-rc1 Thierry Reding
2025-11-15  9:00 ` [GIT PULL 2/8] dt-bindings: " Thierry Reding
2025-11-15  9:00 ` [GIT PULL 3/8] amba: Fixes " Thierry Reding
2025-11-15  9:00 ` Thierry Reding [this message]
2025-11-15  9:00 ` [GIT PULL 5/8] ARM: tegra: Device tree changes " Thierry Reding
2025-11-15  9:00 ` [GIT PULL 6/8] ARM: tegra: Default configuration " Thierry Reding
2025-11-17 12:56   ` Thierry Reding
2025-11-15  9:00 ` [GIT PULL 7/8] arm64: tegra: Device tree " Thierry Reding
2025-11-15  9:00 ` [GIT PULL 8/8] arm64: tegra: Default configuration " Thierry Reding
2025-11-21 20:21 ` [GIT PULL 1/8] syscore: Changes " patchwork-bot+linux-soc
2025-11-21 20:50 ` patchwork-bot+linux-soc
2025-11-25 13:50 ` 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=20251115090044.3140331-4-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.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 \
    /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