[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4bfbd5a99af176813f7d8e165cb05dd7.broonie@kernel.org>
Date: Thu, 28 Nov 2024 13:54:36 +0000
From: Mark Brown <broonie@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: [GIT PULL] regulator fixes for v6.13-merge-window
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(-)
Powered by blists - more mailing lists