mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regulator fixes for v7.4-merge-window
Date: Fri, 30 Oct 2026 17:09:57 +0000	[thread overview]
Message-ID: <ce8f48c8b130b27c6baaf6757dee28e5@kernel.org> (raw)

The following changes since commit ba83dd4a47bb47da3d2791b2ad6cd816a851b5d0:

  regulator: rpi-panel-attiny: Fix probe failure after a host cold boot (2026-10-16 20:59:46 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.4-merge-window

for you to fetch changes up to 8a6d73e316f95e398a1de1d1f58314b6d3e7f641:

  regulator: irq: freeze deferred hardware access during suspend (2026-10-23 18:40:07 +0100)

----------------------------------------------------------------
regulator: Fix for v7.4

One fix here, we had an issue with deferred hardware disables where if
we were deferring while suspend was happening we would let the workqueue
run which could result in us trying to access hardware after it or the
buses used to access it were suspended.  We fix this by completing any
work as we suspend the individual regulators.

----------------------------------------------------------------
Jiale Yao (1):
      regulator: irq: freeze deferred hardware access during suspend

 drivers/regulator/irq_helpers.c | 38 ++++++++++++++++++++++----------------
 1 file changed, 22 insertions(+), 16 deletions(-)

             reply	other threads:[~2026-10-30 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 17:09 Mark Brown [this message]
2026-10-30 18:35 ` pr-tracker-bot

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=ce8f48c8b130b27c6baaf6757dee28e5@kernel.org \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®