All of lore.kernel.org
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: vexpress: Add DT support in v2m
Date: Wed, 16 Nov 2011 17:39:45 +0000	[thread overview]
Message-ID: <20111116173945.GG2073@localhost.localdomain> (raw)
In-Reply-To: <1321463271.3137.380.camel@hornet.cambridge.arm.com>

On Wed, Nov 16, 2011 at 05:07:51PM +0000, Pawel Moll wrote:
> On Wed, 2011-11-16 at 16:59 +0000, Rob Herring wrote:
> > It has nothing to do with taste and obviously documentation changes over
> > time. I'm going to start naming everything with legacy because someday
> > it all will be...
> > 
> > It's about how you create compatible strings. They should not be
> > generic, but specific to particular hardware version. If you happen to
> > be compatible with older h/w then you can claim compatibility with that
> > older h/w.
> 
> Notice that it's not:
> 
> 	compatible=legacy
> 
> not even:
> 
> 	compatible=arm,legacy
> 
> It's:
> 	
> 	compatible=arm,vexpress-legacy
> 
> A specific variant of Versatile Express hardware. It's just that the
> "legacy" word carries some meaning. Would it looked better if it was
> called:
> 
> 	compatible=arm,vexpress-nalatenskap
> 
> ? (thanks, google translate ;-)

Come to think of it, is the problem here that we're trying to describe
the _motherboard_ using the compatible property on the root node.
This is why I talked about universal/generic features -- the set of
features common to all platforms sharing a single motherboard
configuration.

Arguably that's wrong, and that compatible property belongs on the
motherboard node itself, so:

/ {
	compatible = "arm,vexpress-ca9x4"


> 
> > >> If you defined the property when the
> > >> original vexpress was designed, it never would have had legacy in the
> > >> name. Generally speaking you never change bindings on old platforms.
> > >>
> > >> So I would have "arm,vexpress" mean legacy and "arm,vexpress-rs1" be the
> > >> new memory map.
> > > 
> > > I'd rather second Dave's idea of having
> > > 
> > >>> 	compatible = "arm,vexpress-<model>", "arm-vexpress-rs1", "arm-vexpress";
> > > 
> > > and
> > > 
> > >>> +	compatible = "arm,vexpress-<model>", "arm,vexpress-legacy", "arm-vexpress";
> > 
> > If arm,vexpress-ca9 is the only legacy platform, then just drop
> > arm,vexpress-legacy altogether.
> 
> It's not. There is additional one, which is not publicly available, but
> is using the motherboard in legacy mode.
> 
> Cheers!
> 
> Pawe?
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Dave Martin <dave.martin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 3/5] ARM: vexpress: Add DT support in v2m
Date: Wed, 16 Nov 2011 17:39:45 +0000	[thread overview]
Message-ID: <20111116173945.GG2073@localhost.localdomain> (raw)
In-Reply-To: <1321463271.3137.380.camel-okZbbLrgpR/YkXV2EHHjLW3o5bpOHsLO@public.gmane.org>

On Wed, Nov 16, 2011 at 05:07:51PM +0000, Pawel Moll wrote:
> On Wed, 2011-11-16 at 16:59 +0000, Rob Herring wrote:
> > It has nothing to do with taste and obviously documentation changes over
> > time. I'm going to start naming everything with legacy because someday
> > it all will be...
> > 
> > It's about how you create compatible strings. They should not be
> > generic, but specific to particular hardware version. If you happen to
> > be compatible with older h/w then you can claim compatibility with that
> > older h/w.
> 
> Notice that it's not:
> 
> 	compatible=legacy
> 
> not even:
> 
> 	compatible=arm,legacy
> 
> It's:
> 	
> 	compatible=arm,vexpress-legacy
> 
> A specific variant of Versatile Express hardware. It's just that the
> "legacy" word carries some meaning. Would it looked better if it was
> called:
> 
> 	compatible=arm,vexpress-nalatenskap
> 
> ? (thanks, google translate ;-)

Come to think of it, is the problem here that we're trying to describe
the _motherboard_ using the compatible property on the root node.
This is why I talked about universal/generic features -- the set of
features common to all platforms sharing a single motherboard
configuration.

Arguably that's wrong, and that compatible property belongs on the
motherboard node itself, so:

/ {
	compatible = "arm,vexpress-ca9x4"


> 
> > >> If you defined the property when the
> > >> original vexpress was designed, it never would have had legacy in the
> > >> name. Generally speaking you never change bindings on old platforms.
> > >>
> > >> So I would have "arm,vexpress" mean legacy and "arm,vexpress-rs1" be the
> > >> new memory map.
> > > 
> > > I'd rather second Dave's idea of having
> > > 
> > >>> 	compatible = "arm,vexpress-<model>", "arm-vexpress-rs1", "arm-vexpress";
> > > 
> > > and
> > > 
> > >>> +	compatible = "arm,vexpress-<model>", "arm,vexpress-legacy", "arm-vexpress";
> > 
> > If arm,vexpress-ca9 is the only legacy platform, then just drop
> > arm,vexpress-legacy altogether.
> 
> It's not. There is additional one, which is not publicly available, but
> is using the motherboard in legacy mode.
> 
> Cheers!
> 
> Paweł
> 
> 
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

  parent reply	other threads:[~2011-11-16 17:39 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 18:27 [PATCH 0/5] Versatile Express DT support, take 2 Pawel Moll
2011-11-11 18:27 ` Pawel Moll
2011-11-11 18:27 ` [PATCH 1/5] ARM: vexpress: Get rid of MMIO_P2V Pawel Moll
2011-11-11 18:27   ` Pawel Moll
2011-11-16 15:35   ` Dave Martin
2011-11-16 15:35     ` Dave Martin
2011-11-16 16:16     ` Pawel Moll
2011-11-16 16:16       ` Pawel Moll
2011-11-16 17:28       ` Dave Martin
2011-11-16 17:28         ` Dave Martin
2011-11-16 17:30         ` Pawel Moll
2011-11-16 17:30           ` Pawel Moll
2011-11-17  7:02           ` Ryan Harkin
2011-11-17  7:02             ` Ryan Harkin
2011-11-17 15:43   ` Russell King - ARM Linux
2011-11-17 15:43     ` Russell King - ARM Linux
2011-11-18 12:20     ` Pawel Moll
2011-11-18 12:20       ` Pawel Moll
2011-11-18 17:44       ` Russell King - ARM Linux
2011-11-18 17:44         ` Russell King - ARM Linux
2011-11-11 18:27 ` [PATCH 2/5] ARM: vexpress: Remove platform SMP functions from ct_desc Pawel Moll
2011-11-11 18:27   ` Pawel Moll
2011-11-17 15:31   ` Russell King - ARM Linux
2011-11-17 15:31     ` Russell King - ARM Linux
2011-11-18 12:20     ` Pawel Moll
2011-11-18 12:20       ` Pawel Moll
2011-11-11 18:27 ` [PATCH 3/5] ARM: vexpress: Add DT support in v2m Pawel Moll
2011-11-11 18:27   ` Pawel Moll
2011-11-16 15:44   ` Dave Martin
2011-11-16 15:44     ` Dave Martin
2011-11-16 16:26     ` Rob Herring
2011-11-16 16:26       ` Rob Herring
2011-11-16 16:37       ` Pawel Moll
2011-11-16 16:37         ` Pawel Moll
2011-11-16 16:59         ` Rob Herring
2011-11-16 16:59           ` Rob Herring
2011-11-16 17:07           ` Pawel Moll
2011-11-16 17:07             ` Pawel Moll
2011-11-16 17:37             ` Pawel Moll
2011-11-16 17:37               ` Pawel Moll
2011-11-16 19:14               ` Dave Martin
2011-11-16 19:14                 ` Dave Martin
2011-11-16 17:39             ` Dave Martin [this message]
2011-11-16 17:39               ` Dave Martin
2011-11-16 17:50               ` Dave Martin
2011-11-16 17:50                 ` Dave Martin
2011-11-16 17:55                 ` Pawel Moll
2011-11-16 17:55                   ` Pawel Moll
2011-11-17 15:53             ` Russell King - ARM Linux
2011-11-17 15:53               ` Russell King - ARM Linux
2011-11-18 12:20               ` Pawel Moll
2011-11-18 12:20                 ` Pawel Moll
2011-11-18 17:49                 ` Russell King - ARM Linux
2011-11-18 17:49                   ` Russell King - ARM Linux
2011-11-16 16:35     ` Pawel Moll
2011-11-16 16:35       ` Pawel Moll
2011-11-16 17:57       ` Dave Martin
2011-11-16 17:57         ` Dave Martin
2011-11-17 13:50         ` Pawel Moll
2011-11-17 13:50           ` Pawel Moll
2011-11-17 14:41           ` Dave Martin
2011-11-17 14:41             ` Dave Martin
2011-11-17 16:05   ` Russell King - ARM Linux
2011-11-17 16:05     ` Russell King - ARM Linux
2011-11-17 18:37     ` Dave Martin
2011-11-17 18:37       ` Dave Martin
2011-11-18 17:52       ` Russell King - ARM Linux
2011-11-18 17:52         ` Russell King - ARM Linux
2011-11-18 12:20     ` Pawel Moll
2011-11-18 12:20       ` Pawel Moll
2011-11-11 18:27 ` [PATCH 4/5] ARM: vexpress: Initial RS1 memory map support Pawel Moll
2011-11-11 18:27   ` Pawel Moll
2011-11-16 15:42   ` Dave Martin
2011-11-16 15:42     ` Dave Martin
2011-11-16 16:28     ` Pawel Moll
2011-11-16 16:28       ` Pawel Moll
2011-11-16 18:03       ` Dave Martin
2011-11-16 18:03         ` Dave Martin
2011-11-17 15:36   ` Russell King - ARM Linux
2011-11-17 15:36     ` Russell King - ARM Linux
2011-11-18 12:20     ` Pawel Moll
2011-11-18 12:20       ` Pawel Moll
2011-11-18 17:56       ` Russell King - ARM Linux
2011-11-18 17:56         ` Russell King - ARM Linux
2011-11-11 18:27 ` [PATCH 5/5] ARM: vexpress: DT-based support for CoreTiles Express A5x2 and A9x4 Pawel Moll
2011-11-11 18:27   ` Pawel Moll
2011-11-11 22:30   ` Rob Herring
2011-11-11 22:30     ` Rob Herring
2011-11-11 22:54     ` Pawel Moll
2011-11-11 22:54       ` Pawel Moll
2011-11-16 15:36   ` Dave Martin
2011-11-16 15:36     ` Dave Martin
2011-11-16 16:22     ` Pawel Moll
2011-11-16 16:22       ` Pawel Moll
2011-11-16 18:17       ` Dave Martin
2011-11-16 18:17         ` Dave Martin
2011-11-16 15:33 ` [PATCH 0/5] Versatile Express DT support, take 2 Dave Martin
2011-11-16 15:33   ` Dave Martin

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=20111116173945.GG2073@localhost.localdomain \
    --to=dave.martin@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.