public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/2] ARM: mvebu: use armada-370-sata for SATA on Armada 375
Date: Fri, 12 Feb 2016 17:49:00 +0100	[thread overview]
Message-ID: <87io1tx4ar.fsf@free-electrons.com> (raw)
In-Reply-To: <1455121756-20804-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Wed, 10 Feb 2016 17:29:15 +0100")

Hi Thomas,
 
 On mer., f?vr. 10 2016, Thomas Petazzoni <thomas.petazzoni@free-electrons•com> wrote:

> From: Lior Amsalem <alior@marvell•com>
>
> The Armada 375 has the same SATA IP as Armada 370 and Armada XP, which
> requires the PHY speed to be set in the LP_PHY_CTL register for SATA
> hotplug to work.
>
> Therefore, this commit updates the compatible string used to describe
> the SATA IP in Armada 375 from marvell,orion-sata to
> marvell,armada-370-sata.
>
> Fixes: 4de59085091f753d08c8429d756b46756ab94665 ("ARM: mvebu: add Device Tree description of the Armada 375 SoC")
> Cc: <stable@vger•kernel.org>
> Signed-off-by: Lior Amsalem <alior@marvell•com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons•com>

Applied on mvebu/dt, I renamed the patch to: " ARM: dts: armada-375: use
armada-370-sata for SATA" to unify the way we labl the dt related patch.
I also adde the reviwed-by tag from Andrew.

Thanks,

Gregory

> ---
> Changes since v1:
>  - Add Fixes: tag, and add stable@ in Cc, as suggested by Andrew Lunn.
> ---
>  arch/arm/boot/dts/armada-375.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/armada-375.dtsi b/arch/arm/boot/dts/armada-375.dtsi
> index 7ccce75..cc952cf 100644
> --- a/arch/arm/boot/dts/armada-375.dtsi
> +++ b/arch/arm/boot/dts/armada-375.dtsi
> @@ -529,7 +529,7 @@
>  			};
>  
>  			sata at a0000 {
> -				compatible = "marvell,orion-sata";
> +				compatible = "marvell,armada-370-sata";
>  				reg = <0xa0000 0x5000>;
>  				interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
>  				clocks = <&gateclk 14>, <&gateclk 20>;
> -- 
> 2.6.4
>

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2016-02-12 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 16:29 [PATCH v2 1/2] ARM: mvebu: use armada-370-sata for SATA on Armada 375 Thomas Petazzoni
2016-02-10 16:29 ` [PATCH v2 2/2] ARM: mvebu: add NAND description to Armada 370 DB and Armada XP DB Thomas Petazzoni
2016-02-10 17:18   ` Andrew Lunn
2016-02-12 16:50   ` Gregory CLEMENT
2016-02-10 17:17 ` [PATCH v2 1/2] ARM: mvebu: use armada-370-sata for SATA on Armada 375 Andrew Lunn
2016-02-12 16:49 ` Gregory CLEMENT [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-27 15:24 [PATCH 0/2] ARM: mvebu: misc DT improvements Thomas Petazzoni
2016-01-27 15:24 ` [PATCH v2 1/2] ARM: mvebu: use armada-370-sata for SATA on Armada 375 Thomas Petazzoni
2016-01-27 17:13   ` Andrew Lunn

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=87io1tx4ar.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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