public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Konstantin Porotchkin <kostap@marvell.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: marvell: Disable AP I2C on Armada-8040-DB
Date: Mon, 03 Jun 2019 16:43:41 +0200	[thread overview]
Message-ID: <87muiyk9uq.fsf@FE-laptop> (raw)
In-Reply-To: <20190521143749.488-1-miquel.raynal@bootlin.com>

Hi Miquel,

> From: Konstantin Porotchkin <kostap@marvell.com>
>
> While AP I2C bus was available to users in early revisions of the SoC,
> this is not the case anymore since eMMC was connected to the AP. Most
> users do not have access to this I2C bus so do not enable it in the
> board device tree.
>
> As there are three I2C buses enabled on this board, add an alias to be
> sure the two other buses keep their initial numbering.
>
> Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>
> [<miquel.raynal@bootlin.com>: Reword commit message, add alias]
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

Applied on mvebu/dt64

Thanks,

Gregory

> ---
>  arch/arm64/boot/dts/marvell/armada-8040-db.dts | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-8040-db.dts b/arch/arm64/boot/dts/marvell/armada-8040-db.dts
> index 9f4f939ab65f..d6e9c014c2f9 100644
> --- a/arch/arm64/boot/dts/marvell/armada-8040-db.dts
> +++ b/arch/arm64/boot/dts/marvell/armada-8040-db.dts
> @@ -27,6 +27,8 @@
>  		ethernet1 = &cp0_eth2;
>  		ethernet2 = &cp1_eth0;
>  		ethernet3 = &cp1_eth1;
> +		i2c1 = &cp0_i2c0;
> +		i2c2 = &cp1_i2c0;
>  	};
>  
>  	cp0_reg_usb3_0_vbus: cp0-usb3-0-vbus {
> @@ -72,11 +74,6 @@
>  	};
>  };
>  
> -&i2c0 {
> -	status = "okay";
> -	clock-frequency = <100000>;
> -};
> -
>  &spi0 {
>  	status = "okay";
>  
> -- 
> 2.19.1
>

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-06-03 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 14:37 [PATCH] arm64: dts: marvell: Disable AP I2C on Armada-8040-DB Miquel Raynal
2019-06-03 14:43 ` Gregory CLEMENT [this message]

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=87muiyk9uq.fsf@FE-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=antoine.tenart@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jason@lakedaemon.net \
    --cc=kostap@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nadavh@marvell.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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