[PATCH v3 0/3] regulator: Add FP9931/JD9930

Andreas Kemnade posted 3 patches 1 month ago
.../bindings/regulator/fitipower,fp9931.yaml       | 110 ++++
.../devicetree/bindings/vendor-prefixes.yaml       |   2 +
drivers/regulator/Kconfig                          |  10 +
drivers/regulator/Makefile                         |   1 +
drivers/regulator/fp9931.c                         | 551 +++++++++++++++++++++
5 files changed, 674 insertions(+)
[PATCH v3 0/3] regulator: Add FP9931/JD9930
Posted by Andreas Kemnade 1 month ago
Add a driver for the FP9931/JD9930 regulator which provides the
comparatively high voltages needed for electronic paper displays.

Datasheet for the FP9931 is at
https://www.fitipower.com/dl/file/flXa6hIchVeu0W3K

Although it is in English, it seems to be only downloadable
from the Chinese part of that website. 
For the JD9930 there can be a datasheet found at
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/JD9930_2D00_0.7_2D00_JUN_2D00_2019.pdf

To simplify things, include the hwmon part directly which is only
one register read and there are not other functions besides
regulators in this chip.

Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
---
Changes in v3:
- cleanup indent in devicetree example
- remove unnecessary checks in hwmon part
- Link to v2: https://patch.msgid.link/20251114-fp9931-submit-v2-0-cd6998932c4c@kemnade.info

Changes in v2:
- vendor prefix fiti->fitipower
- tdly in ms with enum
- no #thermal-sensor-cells
- regulator node names lowercase and under regulators subnode
- s/ts-en/en-ts/
- remove duplicate v3p3 of_match
- remove ancient driver.owner assignmed
- some style cleanup
- Link to v1: https://patch.msgid.link/20251107-fp9931-submit-v1-0-aa7b79d9abb6@kemnade.info

---
Andreas Kemnade (3):
      dt-bindings: vendor-prefixes: Add Fitipower
      dt-bindings: regulator: Add Fitipower FP9931/JD9930
      regulator: Add FP9931/JD9930 driver

 .../bindings/regulator/fitipower,fp9931.yaml       | 110 ++++
 .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
 drivers/regulator/Kconfig                          |  10 +
 drivers/regulator/Makefile                         |   1 +
 drivers/regulator/fp9931.c                         | 551 +++++++++++++++++++++
 5 files changed, 674 insertions(+)
---
base-commit: dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa
change-id: 20251107-fp9931-submit-0ac249b5d6b0

Best regards,
--  
Andreas Kemnade <andreas@kemnade.info>
Re: [PATCH v3 0/3] regulator: Add FP9931/JD9930
Posted by Mark Brown 4 weeks ago
On Sat, 15 Nov 2025 07:50:48 +0100, Andreas Kemnade wrote:
> Add a driver for the FP9931/JD9930 regulator which provides the
> comparatively high voltages needed for electronic paper displays.
> 
> Datasheet for the FP9931 is at
> https://www.fitipower.com/dl/file/flXa6hIchVeu0W3K
> 
> Although it is in English, it seems to be only downloadable
> from the Chinese part of that website.
> For the JD9930 there can be a datasheet found at
> https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/JD9930_2D00_0.7_2D00_JUN_2D00_2019.pdf
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: vendor-prefixes: Add Fitipower
      commit: 0d360d54ea6d0fb3928205d6c67801d1719dd958
[2/3] dt-bindings: regulator: Add Fitipower FP9931/JD9930
      commit: 80bbdefdfb4174ff7e5d4f17658c845ef8f0b623
[3/3] regulator: Add FP9931/JD9930 driver
      commit: 12d821bd13d42e6de3ecb1c13918b1f06a3ee213

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