Skip to contentSkip to conversation

dt-bindings: i2c: imx-lpi2c: Add properties and use unevaluatedProperties

PATCH Applied Krzysztof Kozlowski 3 participants 13 messages Sep 17, 2020 – Sep 27, 2020

Subsystems (5)
lore
Share & tools
lore
#1 lore raw

PATCH v4 2/4 dt-bindings: i2c: imx-lpi2c: Fix i.MX 8QXP compatible matching

In reply to Krzysztof Kozlowski

The i.MX 8QXP DTSes use two compatibles so update the binding to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8qxp-mek.dt.yaml: i2c@5a820000:
compatible: ['fsl,imx8qxp-lpi2c', 'fsl,imx7ulp-lpi2c'] is too long

---
 .../devicetree/bindings/i2c/i2c-imx-lpi2c.yaml        | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)
Documentation/devicetree/bindings/i2c/i2c-imx-lpi2c.yaml +7 -4
index bf68489eecd1..29b9447f3b84 100644
@@ -14,10 +14,13 @@ allOf:
 
 properties:
   compatible:
-    enum:
-      - fsl,imx7ulp-lpi2c
-      - fsl,imx8qxp-lpi2c
-      - fsl,imx8qm-lpi2c
+    oneOf:
+      - enum:
+          - fsl,imx7ulp-lpi2c
+          - fsl,imx8qm-lpi2c
+      - items:
+          - const: fsl,imx8qxp-lpi2c
+          - const: fsl,imx7ulp-lpi2c
 
   reg:
     maxItems: 1
Signature · 1 line
2.17.1
#7 lore raw

PATCH v4 4/4 dt-bindings: i2c: imx: Fix i.MX 7 compatible matching

In reply to Krzysztof Kozlowski

The i.MX 7 DTSes use two compatibles so update the binding to fix dtbs_check warnings like:

arch/arm/boot/dts/imx7d-cl-som-imx7.dt.yaml: i2c@30a20000:
compatible: ['fsl,imx7d-i2c', 'fsl,imx21-i2c'] is not valid under any of the given schemas (Possible causes of the failure):

arch/arm/boot/dts/imx7d-cl-som-imx7.dt.yaml: i2c@30a20000:

    compatible: ['fsl,imx7d-i2c', 'fsl,imx21-i2c'] is too long
---
 Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 3 +++
 1 file changed, 3 insertions(+)
Documentation/devicetree/bindings/i2c/i2c-imx.yaml +3 -0
index a0c87307ca07..f23966b0d6c6 100644
@@ -21,6 +21,9 @@ properties:
       - items:
           - const: fsl,imx35-i2c
           - const: fsl,imx1-i2c
+      - items:
+          - const: fsl,imx7d-i2c
+          - const: fsl,imx21-i2c
       - items:
           - enum:
               - fsl,imx25-i2c
Signature · 1 line
2.17.1
#4 lore raw

PATCH v4 3/4 dt-bindings: i2c: imx: Add properties and use unevaluatedProperties

In reply to Krzysztof Kozlowski

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml: i2c@30a20000:

    '#address-cells', '#size-cells', 'pmic@25' do not match any of the regexes: 'pinctrl-[0-9]+'

---

Changes since v3:
1. Drop address/size cells

Changes since v2:
1. None

Changes since v1:
1. Add more properties and include /schemas/i2c/i2c-controller.yaml#

---
 Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
Documentation/devicetree/bindings/i2c/i2c-imx.yaml +4 -1
index 810536953177..a0c87307ca07 100644
@@ -9,6 +9,9 @@ title: Freescale Inter IC (I2C) and High Speed Inter IC (HS-I2C) for i.MX
 maintainers:
   - Wolfram Sang <[email protected]>
 
+allOf:
+  - $ref: /schemas/i2c/i2c-controller.yaml#
+
 properties:
   compatible:
     oneOf:
@@ -75,7 +78,7 @@ required:
   - interrupts
   - clocks
 
-additionalProperties: false
+unevaluatedProperties: false
 
 examples:
   - |
Signature · 1 line
2.17.1
#0 lore raw

PATCH v4 1/4 dt-bindings: i2c: imx-lpi2c: Add properties and use unevaluatedProperties

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dt.yaml: i2c@5a800000:
'assigned-clock-rates', 'assigned-clocks', 'clock-names', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+'

arch/arm64/boot/dts/freescale/imx8qxp-colibri-eval-v3.dt.yaml: i2c@5a800000:
'touchscreen@2c' does not match any of the regexes: 'pinctrl-[0-9]+'

---

Changes since v3:
1. Drop address/size cells
2. Set maxItems to power domains to 1

Changes since v2:
1. Add assigned-clock-parents

Changes since v1:
1. Add more properties and include /schemas/i2c/i2c-controller.yaml#

---
 .../devicetree/bindings/i2c/i2c-imx-lpi2c.yaml | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/i2c/i2c-imx-lpi2c.yaml +16 -2
index ac0bc5dd64d6..bf68489eecd1 100644
@@ -9,6 +9,9 @@ title: Freescale Low Power Inter IC (LPI2C) for i.MX
 maintainers:
   - Anson Huang <[email protected]>
 
+allOf:
+  - $ref: /schemas/i2c/i2c-controller.yaml#
+
 properties:
   compatible:
     enum:
@@ -22,23 +25,34 @@ properties:
   interrupts:
     maxItems: 1
 
+  assigned-clock-parents: true
+  assigned-clock-rates: true
+  assigned-clocks: true
+  clock-frequency: true
+
+  clock-names:
+    maxItems: 1
+
   clocks:
     maxItems: 1
 
+  power-domains:
+    maxItems: 1
+
 required:
   - compatible
   - reg
   - interrupts
   - clocks
 
-additionalProperties: false
+unevaluatedProperties: false
 
 examples:
   - |
     #include <dt-bindings/clock/imx7ulp-clock.h>
     #include <dt-bindings/interrupt-controller/arm-gic.h>
 
-    lpi2c7@40a50000 {
+    i2c@40a50000 {
         compatible = "fsl,imx7ulp-lpi2c";
         reg = <0x40A50000 0x10000>;
         interrupt-parent = <&intc>;
Signature · 1 line
2.17.1
maintainer Reviewed-by on v4 1/4
#10 lore raw
Quoted 18 lines · Krzysztof Kozlowski

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dt.yaml: i2c@5a800000:
'assigned-clock-rates', 'assigned-clocks', 'clock-names', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+'

arch/arm64/boot/dts/freescale/imx8qxp-colibri-eval-v3.dt.yaml: i2c@5a800000:
'touchscreen@2c' does not match any of the regexes: 'pinctrl-[0-9]+'

---

Changes since v3:
1. Drop address/size cells
2. Set maxItems to power domains to 1

Quoted 9 lines

Changes since v2:
1. Add assigned-clock-parents

Changes since v1:
1. Add more properties and include /schemas/i2c/i2c-controller.yaml#

---
 .../devicetree/bindings/i2c/i2c-imx-lpi2c.yaml | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)
maintainer Reviewed-by on v4 2/4
#2 lore raw

Re: [PATCH v4 2/4] dt-bindings: i2c: imx-lpi2c: Fix i.MX 8QXP compatible matching

In reply to Krzysztof Kozlowski
Quoted 11 lines · Krzysztof Kozlowski

The i.MX 8QXP DTSes use two compatibles so update the binding to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8qxp-mek.dt.yaml: i2c@5a820000:
compatible: ['fsl,imx8qxp-lpi2c', 'fsl,imx7ulp-lpi2c'] is too long

---
 .../devicetree/bindings/i2c/i2c-imx-lpi2c.yaml        | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)
maintainer Reviewed-by on v4 3/4
#5 lore raw

Re: [PATCH v4 3/4] dt-bindings: i2c: imx: Add properties and use unevaluatedProperties

In reply to Krzysztof Kozlowski
Quoted 14 lines · Krzysztof Kozlowski

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml: i2c@30a20000:

    '#address-cells', '#size-cells', 'pmic@25' do not match any of the regexes: 'pinctrl-[0-9]+'

---

Changes since v3:
1. Drop address/size cells

Quoted 9 lines

Changes since v2:
1. None

Changes since v1:
1. Add more properties and include /schemas/i2c/i2c-controller.yaml#

---
 Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
maintainer Reviewed-by on v4 4/4
#8 lore raw

Re: [PATCH v4 4/4] dt-bindings: i2c: imx: Fix i.MX 7 compatible matching

In reply to Krzysztof Kozlowski
Quoted 6 lines · Krzysztof Kozlowski

The i.MX 7 DTSes use two compatibles so update the binding to fix dtbs_check warnings like:

arch/arm/boot/dts/imx7d-cl-som-imx7.dt.yaml: i2c@30a20000:
compatible: ['fsl,imx7d-i2c', 'fsl,imx21-i2c'] is not valid under any of the given schemas (Possible causes of the failure):

Quoted 8 lines

arch/arm/boot/dts/imx7d-cl-som-imx7.dt.yaml: i2c@30a20000:

    compatible: ['fsl,imx7d-i2c', 'fsl,imx21-i2c'] is too long
---
 Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 3 +++
 1 file changed, 3 insertions(+)
#11 lore raw
In reply to Krzysztof Kozlowski
Quoted 18 lines · Krzysztof Kozlowski

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dt.yaml: i2c@5a800000:
'assigned-clock-rates', 'assigned-clocks', 'clock-names', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+'

arch/arm64/boot/dts/freescale/imx8qxp-colibri-eval-v3.dt.yaml: i2c@5a800000:
'touchscreen@2c' does not match any of the regexes: 'pinctrl-[0-9]+'

---

Changes since v3:
1. Drop address/size cells
2. Set maxItems to power domains to 1

Quoted 8 lines

Changes since v2:
1. Add assigned-clock-parents

Changes since v1:
1. Add more properties and include /schemas/i2c/i2c-controller.yaml#

---
 .../devicetree/bindings/i2c/i2c-imx-lpi2c.yaml | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

Hi Wolfram,

The patches have Rob's ack. Could you pick them via I2C tree?

Best regards,
Krzysztof

Applied
#12 lore raw
In reply to Krzysztof Kozlowski
Quoted 4 lines · Krzysztof Kozlowski

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

Quoted 8 lines

arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dt.yaml: i2c@5a800000:
'assigned-clock-rates', 'assigned-clocks', 'clock-names', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+'

arch/arm64/boot/dts/freescale/imx8qxp-colibri-eval-v3.dt.yaml: i2c@5a800000:
'touchscreen@2c' does not match any of the regexes: 'pinctrl-[0-9]+'

Applied to for-next, thanks!

Applied
#3 lore raw

Re: [PATCH v4 2/4] dt-bindings: i2c: imx-lpi2c: Fix i.MX 8QXP compatible matching

In reply to Krzysztof Kozlowski
Quoted 7 lines · Krzysztof Kozlowski

The i.MX 8QXP DTSes use two compatibles so update the binding to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8qxp-mek.dt.yaml: i2c@5a820000:
compatible: ['fsl,imx8qxp-lpi2c', 'fsl,imx7ulp-lpi2c'] is too long

Applied to for-next, thanks!

Applied
#6 lore raw

Re: [PATCH v4 3/4] dt-bindings: i2c: imx: Add properties and use unevaluatedProperties

In reply to Krzysztof Kozlowski
Quoted 9 lines · Krzysztof Kozlowski

Additional properties actually might appear (e.g. power-domains) so describe all typical properties, reference generic i2c schema and use unevaluatedProperties to fix dtbs_check warnings like:

arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml: i2c@30a20000:

    '#address-cells', '#size-cells', 'pmic@25' do not match any of the regexes: 'pinctrl-[0-9]+'

Applied to for-next, thanks!

Applied
#9 lore raw

Re: [PATCH v4 4/4] dt-bindings: i2c: imx: Fix i.MX 7 compatible matching

In reply to Krzysztof Kozlowski
Quoted 10 lines · Krzysztof Kozlowski

The i.MX 7 DTSes use two compatibles so update the binding to fix dtbs_check warnings like:

arch/arm/boot/dts/imx7d-cl-som-imx7.dt.yaml: i2c@30a20000:
compatible: ['fsl,imx7d-i2c', 'fsl,imx21-i2c'] is not valid under any of the given schemas (Possible causes of the failure):

arch/arm/boot/dts/imx7d-cl-som-imx7.dt.yaml: i2c@30a20000:

    compatible: ['fsl,imx7d-i2c', 'fsl,imx21-i2c'] is too long

Applied to for-next, thanks!