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 v5 0/2] i2c: mv64xxx: bus-reset-gpios
Date: Fri, 27 Oct 2023 16:31:02 +1300 [thread overview]
Message-ID: <20231027033104.1348921-1-chris.packham@alliedtelesis.co.nz> (raw)
This series adds the ability to associate a gpio with an I2C bus so that
downstream devices can be brought out of reset when the host controller is
probed.
Chris Packham (2):
dt-bindings: i2c: mv64xxx: add bus-reset-gpios property
i2c: mv64xxx: add an optional bus-reset-gpios property
.../bindings/i2c/marvell,mv64xxx-i2c.yaml | 10 ++++++++++
drivers/i2c/busses/i2c-mv64xxx.c | 16 ++++++++++++++++
2 files changed, 26 insertions(+)
--
2.42.0
next reply other threads:[~2023-10-27 3:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 3:31 Chris Packham [this message]
2023-10-27 3:31 ` [PATCH v5 1/2] dt-bindings: i2c: mv64xxx: add bus-reset-gpios property Chris Packham
2023-10-27 9:09 ` Wolfram Sang
2023-10-27 11:25 ` Krzysztof Kozlowski
2023-10-27 19:22 ` Rob Herring
2023-10-28 7:51 ` Krzysztof Kozlowski
2023-10-27 3:31 ` [PATCH v5 2/2] i2c: mv64xxx: add an optional " Chris Packham
2023-10-27 8:48 ` Andi Shyti
2023-10-27 11:27 ` Krzysztof Kozlowski
2023-10-27 11:37 ` Krzysztof Kozlowski
2023-10-27 12:55 ` Andi Shyti
2023-10-29 21:02 ` Chris Packham
2023-10-27 15:10 ` Mark Brown
2023-10-29 20:48 ` Chris Packham
2023-10-31 6:01 ` Krzysztof Kozlowski
2023-10-31 19:59 ` Chris Packham
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=20231027033104.1348921-1-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).