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, pierre.gondois@arm.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 0/3] i2c: mv64xxx: Support for I2C unstuck
Date: Wed, 27 Sep 2023 12:47:58 +1300 [thread overview]
Message-ID: <20230926234801.4078042-1-chris.packham@alliedtelesis.co.nz> (raw)
Some newer Marvell SoCs natively support a recovery mechanisim. This can be
used as an alternative to the generic pinctrl/GPIO recovery mechanism used on
the older SoCs.
Chris Packham (3):
dt-bindings: i2c: mv64xxx: update bindings for unstuck register
arm64: dts: marvell: AC5: use I2C unstuck function
i2c: mv64xxx: add support for FSM based recovery
.../bindings/i2c/marvell,mv64xxx-i2c.yaml | 5 +-
arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi | 14 ++--
drivers/i2c/busses/i2c-mv64xxx.c | 71 +++++++++++++++++--
3 files changed, 75 insertions(+), 15 deletions(-)
--
2.42.0
next reply other threads:[~2023-09-26 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 23:47 Chris Packham [this message]
2023-09-26 23:47 ` [PATCH 1/3] dt-bindings: i2c: mv64xxx: update bindings for unstuck register Chris Packham
2023-09-27 15:05 ` Conor Dooley
2023-09-26 23:48 ` [PATCH 2/3] arm64: dts: marvell: AC5: use I2C unstuck function Chris Packham
2023-09-26 23:48 ` [PATCH 3/3] i2c: mv64xxx: add support for FSM based recovery Chris Packham
2023-10-05 21:58 ` Andi Shyti
2023-10-05 22:39 ` Chris Packham
2023-10-05 23:07 ` Andi Shyti
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=20230926234801.4078042-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=pierre.gondois@arm.com \
--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).