From: dhdang@apm.com (Duc Dang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: apm: Fix compatible string for X-Gene 2 SATA controller DTS node
Date: Tue, 29 Mar 2016 12:11:21 -0700 [thread overview]
Message-ID: <CADaLNDnU7UJOOFs9euPP035iJX5b1-p7jLoKB5f0Sn==Ec3sYA@mail.gmail.com> (raw)
In-Reply-To: <1459245294-22678-1-git-send-email-rsahu@apm.com>
On Tue, Mar 29, 2016 at 2:54 AM, Rameshwar Prasad Sahu <rsahu@apm.com> wrote:
> Fix X-Gene SATA controller compatible string for Merlin board.
>
> Signed-off-by: Rameshwar Prasad Sahu <rsahu@apm.com>
> Acked-by: Suman Tripathi <stripathi@apm.com>
I will queue this patch into xgene-next tree.
> ---
> arch/arm64/boot/dts/apm/apm-shadowcat.dtsi | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi b/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
> index 5d87a3d..74d971e 100644
> --- a/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
> +++ b/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
> @@ -524,7 +524,7 @@
> };
>
> sata1: sata at 1a000000 {
> - compatible = "apm,xgene-ahci";
> + compatible = "apm,xgene-ahci-v2";
> reg = <0x0 0x1a000000 0x0 0x1000>,
> <0x0 0x1f200000 0x0 0x1000>,
> <0x0 0x1f20d000 0x0 0x1000>,
> @@ -534,7 +534,7 @@
> };
>
> sata2: sata at 1a200000 {
> - compatible = "apm,xgene-ahci";
> + compatible = "apm,xgene-ahci-v2";
> reg = <0x0 0x1a200000 0x0 0x1000>,
> <0x0 0x1f210000 0x0 0x1000>,
> <0x0 0x1f21d000 0x0 0x1000>,
> @@ -544,7 +544,7 @@
> };
>
> sata3: sata at 1a400000 {
> - compatible = "apm,xgene-ahci";
> + compatible = "apm,xgene-ahci-v2";
> reg = <0x0 0x1a400000 0x0 0x1000>,
> <0x0 0x1f220000 0x0 0x1000>,
> <0x0 0x1f22d000 0x0 0x1000>,
> --
> 1.7.1
>
Regards,
Duc Dang.
next prev parent reply other threads:[~2016-03-29 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 9:54 [PATCH] arm64: dts: apm: Fix compatible string for X-Gene 2 SATA controller DTS node Rameshwar Prasad Sahu
2016-03-29 19:11 ` Duc Dang [this message]
2016-04-11 9:14 ` Rameshwar Sahu
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='CADaLNDnU7UJOOFs9euPP035iJX5b1-p7jLoKB5f0Sn==Ec3sYA@mail.gmail.com' \
--to=dhdang@apm.com \
--cc=linux-arm-kernel@lists.infradead.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).