From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Zhang Wei-r63237" <Wei.Zhang@freescale.com>
Cc: <mporter@kernel.crashing.org>,
"Kumar Gala" <galak@kernel.crashing.org>,
<linux-kernel@vger.kernel.org>, <linuxppc-dev@ozlabs.org>,
<paulus@samba.org>
Subject: Re: [PATCH 1/5] Add the explanation and sample of RapidIO DTS sector to the document of booting-without-of.txt file.
Date: Mon, 18 Jun 2007 14:43:43 +0200 [thread overview]
Message-ID: <8ce6f7f0f93921b9b6ed883fba247c2b@kernel.crashing.org> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C527171@zch01exm26.fsl.freescale.net>
>> You don't need to mention _all_ compatible devices in
>> the "compatible" property, only the few that matter;
>> typically the oldest one, and sometimes some intermediate
>> device that has extra features over the original one.
>
> The oldest one is difficult to find out sometime. Can we only set the
> self name in dts, such as "fsl, rapidio-8641", and add this
> 'compatible'
> property to the driver ids arrays?
You can do that, but you typically don't need to -- the
whole idea of "compatible" is to avoid this, and not need
to have huge "pci id" style tables in the device drivers
that need constant updating. But you _can_ do it, sure.
> Such as:
>
> static struct of_device_id of_rio_rpn_ids[] = {
> { .compatible = "fsl, rapidio-8540",},
> { .compatible = "fsl, rapidio-8560",},
> { .compatible = "fsl, rapidio-8641",},
> { .compatible = "fsl, rapidio-8548",},
> {},
> };
>
> How about that?
I would just put 8540 in the table and in all device trees
in this case.
>> It isn't useful to add "compatible" entries that no OS
>> probes for.
>>
>>>> Concrete names are good.
>>>
>>> While I agree concrete names are good, we put these 'blocks' in so
>>> many devices that using the device to match on is pointless.
>>
>> You *definitely* should put the device name for _this_
>> device in there, in case it needs some special workaround.
>>
>>> I'm all for making up a name like 'Grande', 'Del',
>> 'Janeiro'. This is
>>> effective what we did with gianfar. The name gets picked up pretty
>>> quickly by people.
>>
>> That can be used as the "base" name, yes.
>
> Do you have the name list? I can change my codes according them.
Nope.
> How about 'Mercurary', 'Venus', 'Earth', 'Mars', 'Saturn', 'Jupiter',
> 'Uranus', 'Neptune',
> Or 'Aries', 'Taurus', 'Gemini', 'Cancer', 'Leo', 'Virgo', 'Libra',
> 'Scorpius', 'Sagittarius', 'Capricornus', 'Aquarius', 'Pisces' ?
I don't like making up names just for this, I don't see what good
this would do. Using a pre-existing code name is fine of course,
as long as it is a unique identifier, since that's all that matters.
Segher
prev parent reply other threads:[~2007-06-18 12:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 9:02 [PATCH 0/5] Porting RapidIO driver from ppc to powerpc architecture and adding memory mapped RapidIO driver Zhang Wei
2007-06-12 9:02 ` [PATCH 1/5] Add the explanation and sample of RapidIO DTS sector to the document of booting-without-of.txt file Zhang Wei
2007-06-12 9:02 ` [PATCH 2/5] Add RapidIO sector to MPC8641HPCN board dts file Zhang Wei
2007-06-12 9:02 ` [PATCH 3/5] Add the platform device support with RapidIO to MPC8641HPCN platform Zhang Wei
2007-06-12 9:02 ` [PATCH 4/5] Add RapidIO support to powerpc architecture Zhang Wei
2007-06-12 22:58 ` [PATCH 2/5] Add RapidIO sector to MPC8641HPCN board dts file Phil Terry
2007-06-13 2:49 ` Zhang Wei-r63237
2007-06-13 5:02 ` [PATCH 1/5] Add the explanation and sample of RapidIO DTS sector to the document of booting-without-of.txt file Segher Boessenkool
2007-06-13 8:14 ` Zhang Wei-r63237
2007-06-13 8:28 ` Segher Boessenkool
2007-06-13 9:37 ` Zhang Wei-r63237
2007-06-13 9:48 ` Segher Boessenkool
2007-06-14 5:53 ` Kumar Gala
2007-06-14 7:52 ` Segher Boessenkool
2007-06-18 3:27 ` Zhang Wei-r63237
2007-06-18 12:43 ` Segher Boessenkool [this message]
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=8ce6f7f0f93921b9b6ed883fba247c2b@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Wei.Zhang@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mporter@kernel.crashing.org \
--cc=paulus@samba.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