This patch series adds support for RTQ2208 SubPMIC regulators.
The RTQ2208 is a multi-phase, programmable power management IC that
integrate with dual multi-configurable, synchronous buck converters
and two ldos. The bucks features wide output voltage range from 0.4V to 2.05V
and the capability to configure the corresponding power stages.
Thank you,
Alina yu
---
Change in v7:
- In Patch 2/2:
- Include missing <linux/mod_devicetable.h>
- Remove fixed_uV in self-defined structure and rtq2208_ldo_get_voltage
- Modify sizeof() parameter in rdesc = devm_kzalloc(..., sizeof().....)
- Add const to type casting in regulator_ops to avoid unexpected manipulation
- Remove rtq2208_of_parse_cb and use of_regulator_match to get constraints.min_uV
- Return devm_request_threaded_irq directly
- Remove __maybe_unused and redundant comma in rtq2208_device_tables
- Remove v2 in MODULE_LICENSE
Change in v6:
- In Patch 1/2:
- Add "additionalProperties: false" to regulator node
- In Patch 2/2:
- Remove Reported-by tag
Change in v5:
- In Patch 1/2:
- Revise filename from $id
- Remove "regulator-compatible" for ldos
- Add missing "high" for "richtek,mtp-sel-high"
- Remove "regulator-mode" property
- Add and modify "unevaluatedProperties: false" and "additionalProperties: false"
- Remove "richtek,fixed-uV"
- Remove redundant space in "buck-a" and "ldo2"
- In Patch 2/2:
- Modify 'rdesc->fixed_uV' get, becasue "richtek,fixed-uV" is removed from yaml
- Modify 'mtp_sel' get because read property is changed from "richtek,mtp-sel" to
"richtek,mtp-sel-high" in yaml
- Add missing regulators_node points to regulator node in yaml
- Include <linux/bitfield.h> for 'FIELD_PREP' reported by kernel test robot
Change in v4:
- In Patch 1/2:
- Modify filename to "richtek,rtq2208"
- Add more desciptions for "regulator-allowed-modes"
Change in v3:
- In Patch 1/2:
- Fix some typos
- Modify the descriptions for "richtek,mtp-sel"
- Modify the node name to lowercase and remove underscore
- Remove '|' from description
- Remove "regulator-compatible" from property
- Remove "regulator-state-mem" from pattern
- Modify node name to generic one
---
Alina Yu (2):
regulator: dt-bindings: rtq2208: Add Richtek RTQ2208 SubPMIC
regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver
.../bindings/regulator/richtek,rtq2208.yaml | 197 +++++++
drivers/regulator/Kconfig | 11 +
drivers/regulator/Makefile | 1 +
drivers/regulator/rtq2208-regulator.c | 583 +++++++++++++++++++++
4 files changed, 792 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rtq2208.yaml
create mode 100644 drivers/regulator/rtq2208-regulator.c
--
2.7.4
On Mon, 07 Aug 2023 14:28:05 +0800, Alina Yu wrote:
> This patch series adds support for RTQ2208 SubPMIC regulators.
> The RTQ2208 is a multi-phase, programmable power management IC that
> integrate with dual multi-configurable, synchronous buck converters
> and two ldos. The bucks features wide output voltage range from 0.4V to 2.05V
> and the capability to configure the corresponding power stages.
>
> Thank you,
> Alina yu
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] regulator: dt-bindings: rtq2208: Add Richtek RTQ2208 SubPMIC
commit: 4b591ed6971191134e331f02300b4ec4dee188ea
[2/2] regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver
commit: 85a11f55621a0c18b22b43ab4219450ac1d19386
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark