Skip to contentSkip to conversation

regulator: sun20i: Add Allwinner D1 LDOs driver

PATCH In review Chen-Yu Tsai 2 participants 4 messages May 9, 2024 – May 10, 2024

Subsystems (3)
lore
Share & tools
lore

Chen-Yu Tsai

author maintainer
#0 lore raw

v6 cover regulator: sun20i: Add Allwinner D1 LDOs driver

From: Chen-Yu Tsai <[email protected]>

Hi,

This is v6 of the Allwinner D1 LDO driver series, separated by subsystem. I've picked up this work from Samuel. This part contains just the regulator driver bits. The sunxi SRAM binding part will be sent out after the merge window due to a conflict in next.

Unlike what the original cover letter mentioned, it is perfectly OK to merge this part separately. The SRAM driver changes were already merged some time ago, and the SRAM bindings depend on the regulator bindings, not the other way around.

Changes in v6:
- Include linux/of.h in the regulator driver to fix the "implicit declaration of function of_'device_get_match_data'" and unknown type 'struct of_device_id' errors.

Original cover letter:

This series adds the binding and driver for one of the two pairs of LDOs inside the Allwinner D1 SoC. I am splitting up the two pairs of LDOs to unblock merging the SoC devicetree; the analog LDOs depend on the audio codec binding, but they are not required to boot.

A binding and driver change is required for the SRAM controller, to accept the regulators device as its child node.

The example for the regulator device binding is in SRAM controller binding document, per Rob's request to keep MFD examples in one place.

Because of this, at least the first 3 patches need to be taken together through the regulator tree, though it should be fine to merge the whole series that way.

Changes in v5:
- Correct the voltage calculation for the non-linearity around 1.6 V.

Changes in v4:
- Fix the order of the maintainer/description sections
- Replace unevaluatedProperties with "additionalProperties: false"
- Drop the analog LDOs until the codec binding is ready
- Drop the analog LDOs until the codec binding is ready
- Remove unevaluatedProperties from regulators schema reference
- Check the compatible string instead of the node name

Changes in v3:
- Add "reg" property to bindings
- Add "unevaluatedProperties: true" to regulator nodes
- Minor changes to regulator node name patterns
- Remove system-ldos example (now added in the parent binding)
- Adjust control flow in sun20i_regulator_get_regmap() for clarity
- Require the regulators node to have a unit address
- Reference the regulator schema from the SRAM controller schema
- Move the system LDOs example to the SRAM controller schema
- Reorder the patches so the example passes validation

Changes in v2:
- Remove syscon property from bindings
- Update binding examples to fix warnings and provide context
- Use decimal numbers for .n_voltages instead of field widths
- Get the regmap from the parent device instead of a property/phandle

Samuel Holland (2):
regulator: dt-bindings: Add Allwinner D1 system LDOs
regulator: sun20i: Add Allwinner D1 LDOs driver

 .../allwinner,sun20i-d1-system-ldos.yaml      |  37 +++++
 drivers/regulator/Kconfig                     |   8 +
 drivers/regulator/Makefile                    |   1 +
 drivers/regulator/sun20i-regulator.c          | 157 ++++++++++++++++++
 4 files changed, 203 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system-ldos.yaml
 create mode 100644 drivers/regulator/sun20i-regulator.c
Signature · 1 line
2.39.2
author maintainer
#1 lore raw

PATCH v6 1/2 regulator: dt-bindings: Add Allwinner D1 system LDOs

From: Samuel Holland <[email protected]>

The Allwinner D1 SoC contains two pairs of in-package LDOs. The pair of "system" LDOs is for general purpose use. LDOA generally powers the board's 1.8 V rail. LDOB powers the in-package DRAM, where applicable.

---
 .../allwinner,sun20i-d1-system-ldos.yaml      | 37 +++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system-ldos.yaml
Documentation/devicetree/bindings/regulator/allwinner,sun20i-d1-system-ldos.yaml new file +37 -0
new file mode 100644
index 000000000000..ec6695c8d2e3
@@ -0,0 +1,37 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/regulator/allwinner,sun20i-d1-system-ldos.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Allwinner D1 System LDOs
+
+maintainers:
+  - Samuel Holland <[email protected]>
+
+description:
+  Allwinner D1 contains a pair of general-purpose LDOs which are designed to
+  supply power inside and outside the SoC. They are controlled by a register
+  within the system control MMIO space.
+
+properties:
+  compatible:
+    enum:
+      - allwinner,sun20i-d1-system-ldos
+
+  reg:
+    maxItems: 1
+
+patternProperties:
+  "^ldo[ab]$":
+    type: object
+    $ref: regulator.yaml#
+    unevaluatedProperties: false
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+...
Signature · 1 line
2.39.2
author maintainer
#2 lore raw

PATCH v6 2/2 regulator: sun20i: Add Allwinner D1 LDOs driver

In reply to Chen-Yu Tsai

From: Samuel Holland <[email protected]>

D1 contains two pairs of LDOs, "analog" LDOs and "system" LDOs. They are similar and can share a driver, but only the system LDOs have a DT binding defined so far.

The system LDOs have a single linear range. The voltage step is not an integer, so a custom .list_voltage is needed to get the rounding right.

---
 drivers/regulator/Kconfig            |   8 ++
 drivers/regulator/Makefile           |   1 +
 drivers/regulator/sun20i-regulator.c | 157 +++++++++++++++++++++++++++
 3 files changed, 166 insertions(+)
 create mode 100644 drivers/regulator/sun20i-regulator.c
drivers/regulator/Kconfig +8 -0
index 7db0a29b5b8d..acdb02a4ac0c 100644
@@ -1415,6 +1415,14 @@ config REGULATOR_STW481X_VMMC
 	  This driver supports the internal VMMC regulator in the STw481x
 	  PMIC chips.
 
+config REGULATOR_SUN20I
+	tristate "Allwinner D1 internal LDOs"
+	depends on ARCH_SUNXI || COMPILE_TEST
+	select MFD_SYSCON
+	default ARCH_SUNXI
+	help
+	  This driver supports the internal LDOs in the Allwinner D1 SoC.
+
 config REGULATOR_SY7636A
 	tristate "Silergy SY7636A voltage regulator"
 	depends on MFD_SY7636A
drivers/regulator/Makefile +1 -0
index 46fb569e6be8..ba15fa5f30ad 100644
@@ -163,6 +163,7 @@ obj-$(CONFIG_REGULATOR_STM32_VREFBUF) += stm32-vrefbuf.o
 obj-$(CONFIG_REGULATOR_STM32_PWR) += stm32-pwr.o
 obj-$(CONFIG_REGULATOR_STPMIC1) += stpmic1_regulator.o
 obj-$(CONFIG_REGULATOR_STW481X_VMMC) += stw481x-vmmc.o
+obj-$(CONFIG_REGULATOR_SUN20I) += sun20i-regulator.o
 obj-$(CONFIG_REGULATOR_SY7636A) += sy7636a-regulator.o
 obj-$(CONFIG_REGULATOR_SY8106A) += sy8106a-regulator.o
 obj-$(CONFIG_REGULATOR_SY8824X) += sy8824x.o
drivers/regulator/sun20i-regulator.c new file +157 -0

157 lines not on this page · raw message

Signature · 1 line
2.39.2
maintainer
#3 lore raw
In reply to Chen-Yu Tsai
Quoted 11 lines · Chen-Yu Tsai

This is v6 of the Allwinner D1 LDO driver series, separated by subsystem. I've picked up this work from Samuel. This part contains just the regulator driver bits. The sunxi SRAM binding part will be sent out after the merge window due to a conflict in next.

Unlike what the original cover letter mentioned, it is perfectly OK to merge this part separately. The SRAM driver changes were already merged some time ago, and the SRAM bindings depend on the regulator bindings, not the other way around.

[...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: Add Allwinner D1 system LDOs

      commit: 622bab1884847fcf3f9bfdf1d534fac3a5fe859f
[2/2] regulator: sun20i: Add Allwinner D1 LDOs driver
      commit: 4e70b26c873dfff317039458a6ea66314bbdce99

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