From: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Jingchang Lu <jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: arnd-r2nGTMty4D4@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCHv6 0/6] ARM: imx: Add Freescale LS1021A SoC and board support
Date: Sun, 26 Oct 2014 08:23:55 +0800 [thread overview]
Message-ID: <20141026002354.GC6973@tiger> (raw)
In-Reply-To: <1414145327-23541-1-git-send-email-jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Fri, Oct 24, 2014 at 06:08:41PM +0800, Jingchang Lu wrote:
> This series contain the support for Freescale LS1021A CPU and LS1021A-QDS
> and LS1021A-TWR board.
>
> The LS1021A SoC combines two ARM Cortex-A7 cores that have been optimized
> for high reliability and pack the highest level of integration available
> for sub-3W embedded communications processors and with a comprehensive
> enablement model focused on ease of programmability.
>
> The LS1021A SoC shares IPs with i.MX family, Vybrid family and Freescale
> PowerPC platform.
>
> For the detail information about LS1021A SoC, please refer to the RM doc.
>
> ---
> changes in v6:
> add dts patch description.
> remove '-' from QDS and TWR board dts name for consistence with u-boot.
I'm not sure it's a good idea. The most idiomatic DTS naming schema is
just <socname>-<boardname>.dts.
Shawn
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-26 0:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 10:08 [PATCHv6 0/6] ARM: imx: Add Freescale LS1021A SoC and board support Jingchang Lu
[not found] ` <1414145327-23541-1-git-send-email-jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-24 10:08 ` [PATCHv6 1/6] ARM: dts: Add SoC level device tree support for LS1021A Jingchang Lu
2014-10-24 10:08 ` [PATCHv6 2/6] ARM: dts: Add initial LS1021A QDS board dts support Jingchang Lu
2014-10-24 10:08 ` [PATCHv6 3/6] ARM: dts: Add initial LS1021A TWR " Jingchang Lu
2014-10-24 10:08 ` [PATCHv5 RESEND 4/6] dt-bindings: arm: add Freescale LS1021A SoC device tree binding Jingchang Lu
2014-10-24 10:08 ` [PATCHv5 RESEND 5/6] ARM: imx: Add initial support for Freescale LS1021A Jingchang Lu
2014-10-24 10:08 ` [PATCHv6 6/6] ARM: imx: Add Freescale LS1021A SMP support Jingchang Lu
2014-10-26 0:23 ` Shawn Guo [this message]
2014-10-26 14:57 ` [PATCHv6 0/6] ARM: imx: Add Freescale LS1021A SoC and board support Jingchang Lu
[not found] ` <1414335419636.17637-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-28 22:17 ` Stefan Agner
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=20141026002354.GC6973@tiger \
--to=shawn.guo-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.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).