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 v6.14-rc7
Date: Fri, 21 Mar 2025 14:38:53 +0000 [thread overview]
Message-ID: <50c80a2096aa0f389fffb34dfffc82ba.broonie@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
The following changes since commit 7eb172143d5508b4da468ed59ee857c6e5e01da6:
Linux 6.14-rc5 (2025-03-02 11:48:20 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v6.14-rc7
for you to fetch changes up to b65439d9015024c37c6b8a17c0569ec44675a979:
regulator: rtq2208: Fix the LDO DVS capability (2025-03-17 12:45:37 +0000)
----------------------------------------------------------------
regulator: Fixes for v6.14
More fixes than I'd like at this point, some of which is due to me
cooking things in -next for a bit and resetting that cooking time as
more fixes came in.
- Christian Eggers fixed some race conditions with the dummy regulator
not being available very early in boot due to the use of asynchronous
probing, both the provider side (ensuring that it's availalbe) and
consumer side (handling things if that goes wrong) are fixed.
- Ludvig Pärsson fixed some lockdep issues with the debugfs
registration for regulators holding more locks than it really needs
causing issues later when looking at the resulting debugfs.boot
- Some device specific fixes for incorrect descriptions of the RTQ2208
from ChiYuan Huang.
----------------------------------------------------------------
ChiYuan Huang (2):
regulator: rtq2208: Fix incorrect buck converter phase mapping
regulator: rtq2208: Fix the LDO DVS capability
Christian Eggers (2):
regulator: dummy: force synchronous probing
regulator: check that dummy regulator has been probed before using it
Ludvig Pärsson (1):
regulator: core: Fix deadlock in create_regulator()
drivers/regulator/core.c | 88 ++++++++------
drivers/regulator/dummy.c | 2 +-
drivers/regulator/rtq2208-regulator.c | 216 +++++++++++++++++++---------------
3 files changed, 178 insertions(+), 128 deletions(-)
next reply other threads:[~2025-03-21 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 14:38 Mark Brown [this message]
2025-03-21 21:27 ` 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=50c80a2096aa0f389fffb34dfffc82ba.broonie@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®