Add a reset-gpios property to the marvell,mv64xxx-i2c binding.

Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
---
 Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml b/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
index 461d1c9ee3f7..ac8859aa2545 100644
--- a/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
+++ b/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
@@ -70,6 +70,9 @@ properties:
   resets:
     maxItems: 1
 
+  reset-gpios:
+    maxItems: 1
+
   dmas:
     items:
       - description: RX DMA Channel
-- 
2.42.0

On 12/10/2023 05:58, Chris Packham wrote:
> Add a reset-gpios property to the marvell,mv64xxx-i2c binding.

Why?

> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---


Best regards,
Krzysztof

Hi Krysztof,

(resend as plain text)

On 12/10/23 20:42, Krzysztof Kozlowski wrote:
> On 12/10/2023 05:58, Chris Packham wrote:
>> Add a reset-gpios property to the marvell,mv64xxx-i2c binding.
> Why?

Sorry about that. I put a better explanation in the corresponding driver 
change but then over-edited when doing the device-tree change. I'll try 
and explain things a bit better in v2.

>> Signed-off-by: Chris Packham<chris.packham@alliedtelesis.co.nz>
>> ---
> Best regards,
> Krzysztof
>