When the binding was converted from txt to yaml, it actually added more
constrains than the original txt binding which was already used in many
in-tree DTSes. Some of the newly added constrains are either not valid
or not neccessary.
Not all SoCs use ipg as the clock name for i2c. There is no point in
having SoC integration information defined in i2c binding. Remove the
clock name requirement in the schema.
The original txt binding didn't require the order of tx and rx for
dmas/dma-names. Many in tree DTSes are already using the other order.
Both orders should just work fine. Update the schema to allow both.
Signed-off-by: Li Yang <leoyang.li@xxxxxxx>
---
v2:
Updated the patch description
Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-imx.yaml b/Documentation/devicetree/bindings/i2c/i2c-imx.yaml
index 3592d49235e0..da55d37a09a4 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-imx.yaml
+++ b/Documentation/devicetree/bindings/i2c/i2c-imx.yaml
@@ -54,20 +54,20 @@ properties:
maxItems: 1
clock-names:
- const: ipg
+ maxItems: 1
clock-frequency:
enum: [ 100000, 400000 ]
dmas:
- items:
- - description: DMA controller phandle and request line for RX
- - description: DMA controller phandle and request line for TX
+ minItems: 2
+ maxItems: 2
dma-names:
+ minItems: 2
+ maxItems: 2
items:
- - const: rx
- - const: tx
+ enum: [ "rx", "tx" ]
sda-gpios:
maxItems: 1
--
2.25.1
