dt-bindings: regulator: Convert anatop regulator to json-schema
Subsystems (2)
PATCH v2 1/1 dt-bindings: regulator: Convert anatop regulator to json-schema
Convert the anatop regulator binding to DT schema format using json-schema.
---
Changes since V1:
- remove definition of "regulator-name" which is a standrad property;
- add "unevaluatedProperties: false".
--- .../bindings/regulator/anatop-regulator.txt | 40 --------- .../bindings/regulator/anatop-regulator.yaml | 94 ++++++++++++++++++++++ 2 files changed, 94 insertions(+), 40 deletions(-) delete mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.yaml
Documentation/devicetree/bindings/regulator/anatop-regulator.txt deleted +0 -40
@@ -1,40 +0,0 @@ -Anatop Voltage regulators - -Required properties: -- compatible: Must be "fsl,anatop-regulator" -- regulator-name: A string used as a descriptive name for regulator outputs -- anatop-reg-offset: Anatop MFD register offset -- anatop-vol-bit-shift: Bit shift for the register -- anatop-vol-bit-width: Number of bits used in the register -- anatop-min-bit-val: Minimum value of this register -- anatop-min-voltage: Minimum voltage of this regulator -- anatop-max-voltage: Maximum voltage of this regulator - -Optional properties: -- anatop-delay-reg-offset: Anatop MFD step time register offset -- anatop-delay-bit-shift: Bit shift for the step time register -- anatop-delay-bit-width: Number of bits used in the step time register -- vin-supply: The supply for this regulator -- anatop-enable-bit: Regulator enable bit offset - -Any property defined as part of the core regulator -binding, defined in regulator.txt, can also be used. - -Example: - - regulator-vddpu { - compatible = "fsl,anatop-regulator"; - regulator-name = "vddpu"; - regulator-min-microvolt = <725000>; - regulator-max-microvolt = <1300000>; - regulator-always-on; - anatop-reg-offset = <0x140>; - anatop-vol-bit-shift = <9>; - anatop-vol-bit-width = <5>; - anatop-delay-reg-offset = <0x170>; - anatop-delay-bit-shift = <24>; - anatop-delay-bit-width = <2>; - anatop-min-bit-val = <1>; - anatop-min-voltage = <725000>; - anatop-max-voltage = <1300000>; - };
Documentation/devicetree/bindings/regulator/anatop-regulator.yaml new file +94 -0
94 lines not on this page · raw message
Signature · 1 line
2.7.4
Quoted 7 lines · Anson Huang
Convert the anatop regulator binding to DT schema format using json-schema.
Signed-off-by Anson Huang <[email protected]>---
Changes since V1:
- remove definition of "regulator-name" which is a standrad property;
- add "unevaluatedProperties: false".
Quoted 7 lines
--- .../bindings/regulator/anatop-regulator.txt | 40 --------- .../bindings/regulator/anatop-regulator.yaml | 94 ++++++++++++++++++++++ 2 files changed, 94 insertions(+), 40 deletions(-) delete mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.yaml
Mark Brown
maintainerQuoted 1 line · Anson Huang
Convert the anatop regulator binding to DT schema format using json-schema.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] dt-bindings: regulator: Convert anatop regulator to json-schema
commit: 81227f49bd272cbcd9bb4650b250519c8aa22065
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