[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230926234801.4078042-2-chris.packham@alliedtelesis.co.nz>
Date: Wed, 27 Sep 2023 12:47:59 +1300
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: gregory.clement@...tlin.com, andi.shyti@...nel.org,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, pierre.gondois@....com
Cc: linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [PATCH 1/3] dt-bindings: i2c: mv64xxx: update bindings for unstuck register
Some newer Marvell SoCs support an "unstuck" function for I2C bus
recovery. This is an alternative to the generic GPIO based recovery that
the older SoCs use. The unstuck register falls outside of the usual
address block for the I2C controller so requires an additional cell in
the register property. This is optional and does not need to be
supplied.
Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
---
.../devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml b/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
index 984fc1ed3ec6..461d1c9ee3f7 100644
--- a/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
+++ b/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
@@ -45,7 +45,10 @@ properties:
auto-detects this and sets it appropriately.
reg:
- maxItems: 1
+ minItems: 1
+ items:
+ - description: I2C controller registers
+ - description: I2C unstuck register
interrupts:
maxItems: 1
--
2.42.0
Powered by blists - more mailing lists