devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Agner <stefan-XLVq0VzYD2Y@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
	kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
	b35083-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] ARM: dts: vf500/vf610: support VF500 SoC
Date: Thu, 02 Oct 2014 17:53:37 +0200	[thread overview]
Message-ID: <20f4e3a1932756c92443d380a7f42f56@agner.ch> (raw)
In-Reply-To: <8882221.sfQOLcQs3p@wuerfel>

Am 2014-10-02 17:28, schrieb Arnd Bergmann:
> On Thursday 02 October 2014 16:55:23 Stefan Agner wrote:
>> The VF500 is essentially the same SoC, but with only one core and
>> without L1 cache. The VF610 is therefore a superset of the VF500.
>> Move allmost all periperals to vf500.dtsi which is then included
>> and enhanced by vf610.dtsi.
>>
>> Signed-off-by: Stefan Agner <stefan-XLVq0VzYD2Y@public.gmane.org>
>> ---
>> Somehow using -M -B switches create a unapplyable patch, hence I
>> generated one without those options. Sorry about that.
>>
>>  arch/arm/boot/dts/vf500.dtsi | 498 ++++++++++++++++++++++++++++++++++++++++++
>>  arch/arm/boot/dts/vf610.dtsi | 507 +------------------------------------------
>>  2 files changed, 510 insertions(+), 495 deletions(-)
>>  create mode 100644 arch/arm/boot/dts/vf500.dtsi
> 
> I think it would be better to create one extra file that contains the common
> parts and is included by both vf500 and vf610.
> 

I also thought about that. But when looking at the product variants, its
clear that VF500 really contains only features, which are part of all
other Vybrids (VF3xx series excluded, but these series is not really
suitable for Linux due to lack of external memory). So vf500.dtsi would
always be a oneliner (#include <vf.dtsi>).

Also I disliked this idea because of the somewhat unclear naming
(vf.dtsi? vfxxx.dtsi?)

--
Stefan
--
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

  reply	other threads:[~2014-10-02 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 14:55 [PATCH 1/2] ARM: dts: vf500/vf610: support VF500 SoC Stefan Agner
     [not found] ` <1412261724-11073-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2014-10-02 14:55   ` [PATCH 2/2] ARM: dts: vf500-colibri: add Colibri VF50 support Stefan Agner
2014-10-02 15:28   ` [PATCH 1/2] ARM: dts: vf500/vf610: support VF500 SoC Arnd Bergmann
2014-10-02 15:53     ` Stefan Agner [this message]
2014-10-08 15:57       ` Bill Pringlemeir

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=20f4e3a1932756c92443d380a7f42f56@agner.ch \
    --to=stefan-xlvq0vzyd2y@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=b35083-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@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).