From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: DTS: LS1021A: add SATA node to DTS
Date: Wed, 2 Dec 2015 14:30:40 +0800 [thread overview]
Message-ID: <20151202063040.GJ692@tiger> (raw)
In-Reply-To: <1448854775-19865-1-git-send-email-Yuantian.Tang@freescale.com>
On Mon, Nov 30, 2015 at 11:39:35AM +0800, Yuantian.Tang at freescale.com wrote:
> From: Tang Yuantian <Yuantian.Tang@freescale.com>
>
> Added SATA node to LS1021A DTS to support SATA function.
>
> Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
I think 'ARM: dts: ls1021a: ...' is a more idiomatic patch prefix for
your patch.
> ---
> v2:
> - put reg-names right after reg property
>
> arch/arm/boot/dts/ls1021a.dtsi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/dts/ls1021a.dtsi
> index 9430a99..33aae8d 100644
> --- a/arch/arm/boot/dts/ls1021a.dtsi
> +++ b/arch/arm/boot/dts/ls1021a.dtsi
> @@ -143,6 +143,16 @@
> status = "disabled";
> };
>
> + sata: sata at 3200000 {
> + compatible = "fsl,ls1021a-ahci";
> + reg = <0x0 0x3200000 0x0 0x10000>,
> + <0x0 0x20220520 0x0 0x4>;
> + reg-names = "ahci", "sata-ecc";
> + interrupts = <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&platform_clk 1>;
> + dma-coherent;
> + };
Shouldn't it have the line below to get the device disabled in
<soc>.dtsi by default, and let <board>.dts that has sata support to
enable it?
status = "disabled";
Shawn
> +
> scfg: scfg at 1570000 {
> compatible = "fsl,ls1021a-scfg", "syscon";
> reg = <0x0 0x1570000 0x0 0x10000>;
> --
> 2.1.0.27.g96db324
>
>
prev parent reply other threads:[~2015-12-02 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 3:39 [PATCH v2] ARM: DTS: LS1021A: add SATA node to DTS Yuantian.Tang at freescale.com
2015-12-02 6:30 ` Shawn Guo [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=20151202063040.GJ692@tiger \
--to=shawnguo@kernel.org \
--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).