From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: wsa@kernel.org, andi.shyti@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
gregory.clement@bootlin.com
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v6 0/2] i2c: bus-reset-gpios
Date: Wed, 15 Nov 2023 16:57:51 +1300 [thread overview]
Message-ID: <20231115035753.925534-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.
v5: https://lore.kernel.org/lkml/20231027033104.1348921-1-chris.packham@alliedtelesis.co.nz/
The conversation sparked from v5 was heading in the direction of this needing
to be more generic. So I've moved the changes up to the i2c core, which is
about as generic as I'm comfortable with.
Chris Packham (2):
dt-bindings: i2c: add bus-reset-gpios property
i2c: add an optional bus-reset-gpios property
Documentation/devicetree/bindings/i2c/i2c.txt | 8 ++++
drivers/i2c/i2c-core-base.c | 39 +++++++++++++++++++
include/linux/i2c.h | 3 ++
3 files changed, 50 insertions(+)
--
2.42.0
next reply other threads:[~2023-11-15 3:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 3:57 Chris Packham [this message]
2023-11-15 3:57 ` [PATCH v6 1/2] dt-bindings: i2c: add bus-reset-gpios property Chris Packham
2023-11-15 21:29 ` Krzysztof Kozlowski
2023-11-15 21:53 ` Chris Packham
2023-11-16 11:37 ` Krzysztof Kozlowski
2023-12-19 17:02 ` wsa
2023-12-19 19:28 ` Chris Packham
2023-12-19 20:50 ` wsa
2023-12-19 23:25 ` Andi Shyti
2023-12-20 7:22 ` Krzysztof Kozlowski
2023-12-20 11:03 ` wsa
2023-12-20 11:29 ` Krzysztof Kozlowski
2023-12-20 11:52 ` wsa
2023-12-21 0:40 ` Andi Shyti
2023-11-15 3:57 ` [PATCH v6 2/2] i2c: add an optional " 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=20231115035753.925534-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 \
--cc=wsa@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).