From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
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: Re: [PATCH v2 2/3] arm64: dts: marvell: AC5: use I2C unstuck function
Date: Thu, 19 Oct 2023 16:40:05 +0200 [thread overview]
Message-ID: <87a5sead6i.fsf@BL-laptop> (raw)
In-Reply-To: <20231006003321.2100016-3-chris.packham@alliedtelesis.co.nz>
Hello Chris,
> The AC5 SoC supports using a controller based I2C unstuck function for
> recovery. Use this instead of the generic GPIO recovery.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi | 14 ++++----------
> 1 file changed, 4 insertions(+), 10 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> index c9ce1010c415..e52d3c3496d5 100644
> --- a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> +++ b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> @@ -137,7 +137,7 @@ mdio: mdio@22004 {
>
> i2c0: i2c@11000{
> compatible = "marvell,mv78230-i2c";
> - reg = <0x11000 0x20>;
> + reg = <0x11000 0x20>, <0x110a0 0x4>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> @@ -146,17 +146,14 @@ i2c0: i2c@11000{
> interrupts = <GIC_SPI 87 IRQ_TYPE_LEVEL_HIGH>;
> clock-frequency=<100000>;
>
> - pinctrl-names = "default", "gpio";
> + pinctrl-names = "default";
> pinctrl-0 = <&i2c0_pins>;
> - pinctrl-1 = <&i2c0_gpio>;
> - scl-gpios = <&gpio0 26 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> - sda-gpios = <&gpio0 27 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
By doing this then older kernel won't be able to do recovery, while if
you keep it, the new kernels will still use new way to support recovery
thanks to the new reg filed added and old kernels will continue to work.
However, what we try to maintain is running new kernel on old dtb not
the opposite which is just a nice to have. At the end it is up to you,
if you really want to remove this chunk I will apply it once the driver
part of the series will be accepted.
Gregory
> status = "disabled";
> };
>
> i2c1: i2c@11100{
> compatible = "marvell,mv78230-i2c";
> - reg = <0x11100 0x20>;
> + reg = <0x11100 0x20>, <0x110a4 0x4>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> @@ -165,11 +162,8 @@ i2c1: i2c@11100{
> interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>;
> clock-frequency=<100000>;
>
> - pinctrl-names = "default", "gpio";
> + pinctrl-names = "default";
> pinctrl-0 = <&i2c1_pins>;
> - pinctrl-1 = <&i2c1_gpio>;
> - scl-gpios = <&gpio0 20 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> - sda-gpios = <&gpio0 21 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> status = "disabled";
> };
>
> --
> 2.42.0
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2023-10-19 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 0:33 [PATCH v2 0/3] i2c: mv64xxx: Support for I2C unstuck Chris Packham
2023-10-06 0:33 ` [PATCH v2 1/3] dt-bindings: i2c: mv64xxx: update bindings for unstuck register Chris Packham
2023-10-06 0:33 ` [PATCH v2 2/3] arm64: dts: marvell: AC5: use I2C unstuck function Chris Packham
2023-10-19 14:40 ` Gregory CLEMENT [this message]
2023-10-19 19:41 ` Chris Packham
2023-10-06 0:33 ` [PATCH v2 3/3] i2c: mv64xxx: add support for FSM based recovery Chris Packham
2023-10-12 20:15 ` Andi Shyti
2023-10-12 20:25 ` Chris Packham
2023-10-13 7:11 ` Wolfram Sang
2023-10-15 20:12 ` 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=87a5sead6i.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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