Skip to contentSkip to conversation

dt-bindings: regulator: Convert sy8824x to json-schema

PATCH In review Jisheng Zhang 3 participants 3 messages Aug 3, 2020 – Aug 18, 2020

Subsystems (2)
Device tree bindings Voltage and current regulator framework
lore
Share & tools
lore

Jisheng Zhang

author
#0 lore raw

PATCH v3 1/1 dt-bindings: regulator: Convert sy8824x to json-schema

Convert the sy8824x binding to DT schema format using json-schema.

Signed-off-by Jisheng Zhang <[email protected]>

---
Since v2:
- add $ref to regulator.yaml
- add unevaluatedProperties

Since v1:
- It seems there's something wrong with my last email, so send out a v2 with another email account

 .../bindings/regulator/silergy,sy8824x.yaml   | 45 +++++++++++++++++++
 .../devicetree/bindings/regulator/sy8824x.txt | 24 ----------
 2 files changed, 45 insertions(+), 24 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/regulator/silergy,sy8824x.yaml
 delete mode 100644 Documentation/devicetree/bindings/regulator/sy8824x.txt
Documentation/devicetree/bindings/regulator/silergy,sy8824x.yaml new file +45 -0
new file mode 100644
index 000000000000..82af4d656177
@@ -0,0 +1,45 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/regulator/silergy,sy8824x.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: silergy sy8824c,sy8824e,sy20276 and sy20278 PMIC
+
+maintainers:
+  - Jisheng Zhang <[email protected]>
+
+allOf:
+  - $ref: regulator.yaml#
+
+properties:
+  compatible:
+    enum:
+      - silergy,sy8824c
+      - silergy,sy8824e
+      - silergy,sy20276
+      - silergy,sy20278
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+unevaluatedProperties: false
+
+examples:
+  - |
+    i2c {
+        #address-cells = <1>;
+        #size-cells = <0>;
+        regulator@60 {
+          compatible = "silergy,sy8824c";
+          regulator-min-microvolt = <800000>;
+          regulator-max-microvolt = <1150000>;
+          reg = <0x60>;
+        };
+    };
+
+...
Documentation/devicetree/bindings/regulator/sy8824x.txt deleted +0 -24
deleted file mode 100644
index c5e95850c427..000000000000
@@ -1,24 +0,0 @@
-SY8824C/SY8824E/SY20276 Voltage regulator
-
-Required properties:
-- compatible: Must be one of the following.
-	"silergy,sy8824c"
-	"silergy,sy8824e"
-	"silergy,sy20276"
-	"silergy,sy20278"
-- reg: I2C slave address
-
-Any property defined as part of the core regulator binding, defined in
-./regulator.txt, can also be used.
-
-Example:
-
-	vcore: regulator@00 {
-		compatible = "silergy,sy8824c";
-		reg = <0x66>;
-		regulator-name = "vcore";
-		regulator-min-microvolt = <800000>;
-		regulator-max-microvolt = <1150000>;
-		regulator-boot-on;
-		regulator-always-on;
-	};
Signature · 1 line
2.28.0
maintainer Reviewed-by on v3 1/1
#1 lore raw
Quoted 12 lines · Jisheng Zhang

Convert the sy8824x binding to DT schema format using json-schema.

Signed-off-by Jisheng Zhang <[email protected]>

---
Since v2:
- add $ref to regulator.yaml
- add unevaluatedProperties

Since v1:
- It seems there's something wrong with my last email, so send out a v2 with another email account

Quoted 6 lines
 .../bindings/regulator/silergy,sy8824x.yaml   | 45 +++++++++++++++++++
 .../devicetree/bindings/regulator/sy8824x.txt | 24 ----------
 2 files changed, 45 insertions(+), 24 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/regulator/silergy,sy8824x.yaml
 delete mode 100644 Documentation/devicetree/bindings/regulator/sy8824x.txt
Reviewed-by Rob Herring <[email protected]>
maintainer
#2 lore raw
In reply to Jisheng Zhang
Quoted 1 line · Jisheng Zhang

Convert the sy8824x 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] regulator: Convert sy8824x to json-schema

      commit: aedf7451e7535bc93bb9cec0ebc91744934da95c

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