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 updates for v6.3
Date: Mon, 20 Feb 2023 14:33:49 +0000 [thread overview]
Message-ID: <20230220143357.C38C0C433EF@smtp.kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 5098 bytes --]
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-v6.3
for you to fetch changes up to 7f62cb8861190e7cc1018ff37597fc49b2eaafa8:
regulator: max597x: Align for simple_mfd_i2c driver (2023-02-16 15:54:02 +0000)
----------------------------------------------------------------
regulator: Updates for v6.3
This has been a very quiet release for the regulator API, there's one
new driver for the Maxim MAX20411, some DT schema conversions and some
small tweaks and improvements but really nothing major at all.
----------------------------------------------------------------
Axel Lin (1):
regulator: max20411: Fix off-by-one for n_voltages setting
Bjorn Andersson (2):
regulator: dt-bindings: Describe Maxim MAX20411
regulator: Introduce Maxim MAX20411 Step-Down converter
Cristian Marussi (1):
regulator: scmi: Allow for zero voltage domains
Jerome Neanne (1):
regulator: tps65219: use generic set_bypass()
Kees Cook (2):
regulator: max77802: Bounds check regulator id against opmode
regulator: s5m8767: Bounds check id indexing into arrays
Konrad Dybcio (1):
regulator: dt-bindings: qcom-labibb: Allow regulator-common properties
Krzysztof Kozlowski (1):
regulator: dt-bindings: fixed-regulator: allow gpios property
Luca Weiss (1):
regulator: dt-bindings: qcom,usb-vbus-regulator: change node name
Mark Brown (2):
regulator: Add Maxim MAX20411 support
regulator: max20411: Directly include bitfield.h
Naresh Solanki (2):
regulator: max597x: Remove unused variable
regulator: max597x: Align for simple_mfd_i2c driver
Neil Armstrong (1):
dt-bindings: regulators: convert non-smd RPM Regulators bindings to dt-schema
Paul Cercueil (1):
regulator: dt-bindings: Convert active-semi PMIC docs to YAML schemas
Randy Dunlap (4):
regulator: act8945a: fix non-kernel-doc comments
regulator: fixed-helper: use the correct function name in comment
regulator: mcp16502: add enum MCP16502_REG_HPM description
regulator: tps65219: use IS_ERR() to detect an error pointer
Rob Herring (1):
regulator: dt-bindings: Convert Fairchild FAN53555 to DT schema
Uwe Kleine-König (1):
regulator: max20411: Convert to i2c's .probe_new()
Wadim Egorov (1):
regulator: tps65219: Report regulator name if devm_regulator_register fails
.../bindings/regulator/act8865-regulator.txt | 117 ----------
.../bindings/regulator/act8945a-regulator.txt | 113 ---------
.../bindings/regulator/active-semi,act8600.yaml | 139 +++++++++++
.../bindings/regulator/active-semi,act8846.yaml | 205 ++++++++++++++++
.../bindings/regulator/active-semi,act8865.yaml | 158 +++++++++++++
.../bindings/regulator/active-semi,act8945a.yaml | 258 +++++++++++++++++++++
.../devicetree/bindings/regulator/fan53555.txt | 24 --
.../bindings/regulator/fcs,fan53555.yaml | 64 +++++
.../bindings/regulator/fixed-regulator.yaml | 7 +
.../bindings/regulator/maxim,max20411.yaml | 58 +++++
.../bindings/regulator/qcom,rpm-regulator.yaml | 128 ++++++++++
.../regulator/qcom,usb-vbus-regulator.yaml | 2 +-
.../bindings/regulator/qcom-labibb-regulator.yaml | 6 +-
drivers/regulator/Kconfig | 8 +
drivers/regulator/Makefile | 1 +
drivers/regulator/act8945a-regulator.c | 6 +-
drivers/regulator/fixed-helper.c | 2 +-
drivers/regulator/max20411-regulator.c | 163 +++++++++++++
drivers/regulator/max597x-regulator.c | 52 +++--
drivers/regulator/max77802-regulator.c | 34 ++-
drivers/regulator/mcp16502.c | 1 +
drivers/regulator/s5m8767.c | 6 +-
drivers/regulator/scmi-regulator.c | 16 +-
drivers/regulator/tps65219-regulator.c | 24 +-
24 files changed, 1269 insertions(+), 323 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/regulator/act8865-regulator.txt
delete mode 100644 Documentation/devicetree/bindings/regulator/act8945a-regulator.txt
create mode 100644 Documentation/devicetree/bindings/regulator/active-semi,act8600.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/active-semi,act8846.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/active-semi,act8865.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/active-semi,act8945a.yaml
delete mode 100644 Documentation/devicetree/bindings/regulator/fan53555.txt
create mode 100644 Documentation/devicetree/bindings/regulator/fcs,fan53555.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max20411.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/qcom,rpm-regulator.yaml
create mode 100644 drivers/regulator/max20411-regulator.c
next reply other threads:[~2023-02-20 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 14:33 Mark Brown [this message]
2023-02-22 19:53 ` [GIT PULL] regulator updates for v6.3 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=20230220143357.C38C0C433EF@smtp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.