From: Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>
To: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Best practice for compatible strings?
Date: Fri, 18 Nov 2011 09:45:44 +0000 [thread overview]
Message-ID: <1321609544.24216.12.camel@hornet.cambridge.arm.com> (raw)
In-Reply-To: <4EC5566C.4030508-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
On Thu, 2011-11-17 at 18:46 +0000, Mitch Bradley wrote:
> The bottom line: In my opinion, if there is no preexisting driver that
> you can't change, there is little need for a non-specific name in the
> compatible list.
I like this explanation very much indeed. And now, having a second look
at Grant's Versatile (non-express) trees I see that he had the same
approach:
compatible = "arm,versatile-ab";
and
compatible = "arm,versatile-pb";
without any additional generic "arm,versatile"...
It seems that I was overzealous in my attempts to abstract the reality,
although I was initially hoping that there would be a generic
"arm,vexpress" machine description. This idea died, so should the
generic compat string.
Thanks!
Paweł
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next prev parent reply other threads:[~2011-11-18 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 18:25 Best practice for compatible strings? Dave Martin
[not found] ` <20111117182543.GD3044-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2011-11-17 18:46 ` Mitch Bradley
[not found] ` <4EC5566C.4030508-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2011-11-18 9:45 ` Pawel Moll [this message]
2011-11-18 10:23 ` 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=1321609544.24216.12.camel@hornet.cambridge.arm.com \
--to=pawel.moll-5wv7dgnigg8@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=wmb-D5eQfiDGL7eakBO8gow8eQ@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