From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>
Cc: jason@lakedaemon.net, andrew@lunn.ch,
sebastian.hesselbarth@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux@armlinux.org.uk, wsa@the-dreams.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH v2 1/2] ARM: dts: Fix I2C repeated start issue on Armada-38x
Date: Mon, 02 Oct 2017 16:21:19 +0200 [thread overview]
Message-ID: <87o9ppmy00.fsf@free-electrons.com> (raw)
In-Reply-To: <20170928213605.22874-2-kalyan.kinthada@alliedtelesis.co.nz> (Kalyan Kinthada's message of "Fri, 29 Sep 2017 10:36:04 +1300")
Hi Kalyan,
On ven., sept. 29 2017, Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz> wrote:
> All the Armada 38x(380, 385, 388) have a silicon issue in
> the I2C controller which violates the I2C repeated start timing
> (errata FE-8471889).
>
> i2c-mv64xxx driver handles this errata based on the compatible string
> "marvell,mv78230-a0-i2c".
>
> This patch activates the "marvell,mv78230-a0-i2c" compatible string
> for the I2C controller on armada-38x SoC based devices.
>
> Signed-off-by: Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>
Applied on mvebu/fixes
Thanks,
Gregory
> ---
> arch/arm/boot/dts/armada-38x.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi
> index 7ff0811e61db..4960722aab32 100644
> --- a/arch/arm/boot/dts/armada-38x.dtsi
> +++ b/arch/arm/boot/dts/armada-38x.dtsi
> @@ -178,7 +178,7 @@
> };
>
> i2c0: i2c@11000 {
> - compatible = "marvell,mv64xxx-i2c";
> + compatible = "marvell,mv78230-a0-i2c", "marvell,mv64xxx-i2c";
> reg = <0x11000 0x20>;
> #address-cells = <1>;
> #size-cells = <0>;
> @@ -189,7 +189,7 @@
> };
>
> i2c1: i2c@11100 {
> - compatible = "marvell,mv64xxx-i2c";
> + compatible = "marvell,mv78230-a0-i2c", "marvell,mv64xxx-i2c";
> reg = <0x11100 0x20>;
> #address-cells = <1>;
> #size-cells = <0>;
> --
> 2.14.1
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-10-02 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 21:36 [PATCH v2 0/2] Fix I2C repeated start timing violation on Armada-38x Kalyan Kinthada
2017-09-28 21:36 ` [PATCH v2 1/2] ARM: dts: Fix I2C repeated start issue " Kalyan Kinthada
2017-10-02 14:21 ` Gregory CLEMENT [this message]
2017-09-28 21:36 ` [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c" Kalyan Kinthada
[not found] ` <20170928213605.22874-3-kalyan.kinthada-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-10-02 14:23 ` Gregory CLEMENT
2017-10-05 11:08 ` Wolfram Sang
2017-10-05 23:29 ` Rob Herring
2017-11-05 12:54 ` Wolfram Sang
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=87o9ppmy00.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=kalyan.kinthada@alliedtelesis.co.nz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=wsa@the-dreams.de \
/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).