From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Subject: Re: Compatible string best practices
Date: Fri, 23 May 2014 17:03:31 +0100
Message-ID: <20140523160331.GA6969@leverpostej>
References: <cc5b8415-4297-49fb-8a2c-bdc4b1b19c2c@BY2FFO11FD033.protection.gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Return-path: <devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Content-Disposition: inline
In-Reply-To: <cc5b8415-4297-49fb-8a2c-bdc4b1b19c2c-neA4ZlFjCT3DAA6W7k9C4mYJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
To: =?utf-8?B?U8O2cmVu?= Brinkmann <soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "git-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org" <git-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
List-Id: devicetree@vger.kernel.org

On Fri, May 23, 2014 at 04:03:06PM +0100, S=C3=B6ren Brinkmann wrote:
> Hi,

Hi,

> I have a question regarding how a compatible string should be created=
=2E
> The simple case is obvious:
>  <IP-vendor>,<IP-type/name>-<IP-revision>
>=20
> But what is the recommended string for a SOC specific implementation =
of
> that IP? Let's say for
>  <SOC-vendor>,<SOC-name>-<SOC-revision>
> how would I assemble a compatible string to identify the SOC-specific
> implementation of IP?
> I think my biggest confusion is which vendor string to use in that ca=
se.
> But in general I'm curious whether some best practice exists for thes=
e
> cases.
>=20
> I think what I've seen most is:
>  <SOC-vendor>,<SOC-name>-<IP-type>
>=20
> But one could probably argue whether to rather use IP-vendor, appendi=
ng
> all the revision strings, ...

I would expect that the vendor prefix would be the last entity along th=
e
chain which altered the IP in some way. Say foo sells device to bar, wh=
o
do nothing other than sell it to baz who do some hacks to integrate it.
=46or that I'd expect something like:

compatible =3D "baz,soc-device", "foo,device";

I'm not sure with revisions (they're not always that useful), but I'd
expect that to be kept next to the element it represent the revision
for:

"baz,soc-vX-device-vY", "bar,soc-device-vY", "foo,device-vY",
"foo,device-vY";

Cheers,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" i=
n
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html