[PATCH v7 0/2] regulator: pf530x: NXP PF530x regulator driver

Woodrow Douglass via B4 Relay posted 2 patches 4 days, 13 hours ago
.../devicetree/bindings/regulator/nxp,pf5300.yaml  |  54 +++
MAINTAINERS                                        |   6 +
drivers/regulator/Kconfig                          |  12 +
drivers/regulator/Makefile                         |   1 +
drivers/regulator/pf530x-regulator.c               | 375 +++++++++++++++++++++
5 files changed, 448 insertions(+)
[PATCH v7 0/2] regulator: pf530x: NXP PF530x regulator driver
Posted by Woodrow Douglass via B4 Relay 4 days, 13 hours ago
I wrote this driver to read settings and state from the nxp pf530x
regulator. Please consider it for inclusion, any criticism is welcome.

Thanks,
Woodrow Douglass

--
2.39.5

---
Changes in v7:.
- make vrange and pf530x_range_desc const, removed unused driver_data pointer
- Drop "nxp,pf5301" and "nxp,pf5302" from of_device_id list, allow fallback
- Add Reviewed-by to the dt-binding from Krzysztof Kozlowski (Thanks!)
- Link to v6: https://lore.kernel.org/r/20250902-pf530x-v6-0-ae5efea2198d@carnegierobotics.com

Changes in v6:
- Make sure that the device tree binding properly references regulator.yaml
- Link to v5: https://lore.kernel.org/r/20250902-pf530x-v5-0-658c403e6a52@carnegierobotics.com

Changes in v5:
- Fixed compatibility match to properly fall back to pf5300
- Reordered patches so that devicetree schema comes before the driver itself
- Modified nxp,pf5300 schema to pass `make dt_binding_check`
- Link to v4: https://lore.kernel.org/r/20250902-pf530x-v4-0-4727f112424e@carnegierobotics.com

Changes in v4:
- Added REGULATOR_ERROR_OVER_TEMP_WARN to pf530x_get_error_flags
- Added EMREV to the info print
- Link to v3: https://lore.kernel.org/r/20250902-pf530x-v3-0-4242e7687761@carnegierobotics.com

Changes in v3:
- Replaced REGCACHE_RBTREE with REGCACHE_MAPLE
- Replaced pf530x_is_enabled function with regulator_is_enabled_regmap
- Added status bits from INT_SENSE1 to pf530x_get_status function
- Added extra context to info print upon chip identification
- Reworked devtree to not require nested "regulators" subnode
- Some minor reformatting of comment style and long lines
- Link to v2: https://lore.kernel.org/r/20250902-pf530x-v2-0-f105eb073cb1@carnegierobotics.com

---
Woodrow Douglass (2):
      regulator: dt-bindings: nxp,pf530x: Add NXP PF5300/PF5301/PF5302 PMICs
      regulator: pf530x: Add a driver for the NXP PF5300 Regulator

 .../devicetree/bindings/regulator/nxp,pf5300.yaml  |  54 +++
 MAINTAINERS                                        |   6 +
 drivers/regulator/Kconfig                          |  12 +
 drivers/regulator/Makefile                         |   1 +
 drivers/regulator/pf530x-regulator.c               | 375 +++++++++++++++++++++
 5 files changed, 448 insertions(+)
---
base-commit: b320789d6883cc00ac78ce83bccbfe7ed58afcf0
change-id: 20250902-pf530x-6db7b921120c

Best regards,
-- 
Woodrow Douglass <wdouglass@carnegierobotics.com>
Re: [PATCH v7 0/2] regulator: pf530x: NXP PF530x regulator driver
Posted by Mark Brown 4 days, 8 hours ago
On Fri, 05 Sep 2025 08:39:41 -0400, Woodrow Douglass wrote:
> I wrote this driver to read settings and state from the nxp pf530x
> regulator. Please consider it for inclusion, any criticism is welcome.
> 
> Thanks,
> Woodrow Douglass
> 
> --
> 2.39.5
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] regulator: dt-bindings: nxp,pf530x: Add NXP PF5300/PF5301/PF5302 PMICs
      commit: f5d15ff664a32593e0152d21ea747fb77e32ce7e
[2/2] regulator: pf530x: Add a driver for the NXP PF5300 Regulator
      commit: b497e1a1a2b10c4ddb28064fba229365ae03311a

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