public inbox for linux-tegra@vger.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 2/4] soc/tegra: Changes for v6.20-rc1
Date: Sun, 18 Jan 2026 09:03:01 +0100	[thread overview]
Message-ID: <20260118080304.2646387-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20260118080304.2646387-1-thierry.reding@gmail.com>

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(-)

  reply	other threads:[~2026-01-18  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18  8:03 [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1 Thierry Reding
2026-01-18  8:03 ` Thierry Reding [this message]
2026-01-18  8:03 ` [GIT PULL 3/4] ARM: tegra: Device tree changes " Thierry Reding
2026-01-18  8:03 ` [GIT PULL 4/4] arm64: tegra: Changes " Thierry Reding
2026-01-22 10:08 ` [GIT PULL 1/4] dt-bindings: " Krzysztof Kozlowski
2026-01-22 11:02   ` Geert Uytterhoeven
2026-01-22 12:20     ` Thierry Reding
2026-01-23  7:43       ` Krzysztof Kozlowski
2026-01-27  9:51         ` Thierry Reding
2026-01-23  7:47 ` Krzysztof Kozlowski
2026-01-23  7:52   ` Krzysztof Kozlowski
2026-01-27 10:05     ` Thierry Reding
2026-01-27 10:02   ` 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=20260118080304.2646387-2-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