From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: gregory.clement@bootlin.com, andi.shyti@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 1/2] dt-bindings: i2c: mv64xxx: add reset-gpios property
Date: Thu, 12 Oct 2023 16:58:37 +1300 [thread overview]
Message-ID: <20231012035838.2804064-2-chris.packham@alliedtelesis.co.nz> (raw)
In-Reply-To: <20231012035838.2804064-1-chris.packham@alliedtelesis.co.nz>
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
next prev parent reply other threads:[~2023-10-12 3:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 3:58 [PATCH 0/2] i2c: mv64xxx: reset-gpios Chris Packham
2023-10-12 3:58 ` Chris Packham [this message]
2023-10-12 7:42 ` [PATCH 1/2] dt-bindings: i2c: mv64xxx: add reset-gpios property Krzysztof Kozlowski
2023-10-12 20:55 ` Chris Packham
2023-10-12 3:58 ` [PATCH 2/2] i2c: mv64xxx: add an optional " Chris Packham
2023-10-12 10:21 ` Andi Shyti
2023-10-12 10:49 ` Peter Rosin
2023-10-12 20:54 ` Chris Packham
[not found] ` <812dd506-c61b-4967-9b0b-ea35a111bc7f@alliedtelesis.co.nz>
2023-10-13 9:34 ` Andi Shyti
2023-10-15 20:20 ` Chris Packham
2023-10-16 7:31 ` Peter Rosin
2023-10-21 7:18 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231012035838.2804064-2-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).