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.13-merge-window
Date: Thu, 28 Nov 2024 13:54:36 +0000 [thread overview]
Message-ID: <4bfbd5a99af176813f7d8e165cb05dd7.broonie@kernel.org> (raw)
The following changes since commit 21ccadc64dae18bd092f1255bdbaf595f53381d5:
regulator: dt-bindings: qcom,rpmh: Correct PM8550VE supplies (2024-11-13 13:53:14 +0000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v6.13-merge-window
for you to fetch changes up to 351f2bfe6362c663f45f5c6111f14365cfd094ab:
regulator: core: Ignore unset max_uA constraints in current limit check (2024-11-21 14:48:25 +0000)
----------------------------------------------------------------
regulator: Fixes for v6.13
A couple of fixes that came in during the merge window, plus
documetation of a new device ID for the Qualcomm LABIBB driver. There's
a core fix for the rarely used current constraints and a fix for the
Qualcomm RPMH driver which had described only one of the two voltage
ranges that the hardware could control, creating a potential
incompatibility with the configuration left by firmware.
----------------------------------------------------------------
Kory Maincent (Dent Project) (1):
regulator: core: Ignore unset max_uA constraints in current limit check
Melody Olvera (1):
regulator: qcom-rpmh: Update ranges for FTSMPS525
Neil Armstrong (1):
dt-bindings: regulator: qcom-labibb-regulator: document the pmi8950 labibb regulator
.../bindings/regulator/qcom-labibb-regulator.yaml | 7 +-
drivers/regulator/core.c | 3 +-
drivers/regulator/qcom-rpmh-regulator.c | 83 ++++++++++------------
3 files changed, 44 insertions(+), 49 deletions(-)
next reply other threads:[~2024-11-28 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 13:54 Mark Brown [this message]
2024-11-28 19:19 ` 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=4bfbd5a99af176813f7d8e165cb05dd7.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®