From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] [POWERPC] Add docs for Freescale PowerQUICC SATA device tree nodes
Date: Tue, 22 Jan 2008 14:54:03 -0700 [thread overview]
Message-ID: <fa686aa40801221354i53b5e8ebn8fc547b8eea75ebe@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801221536430.25559@blarg.am.freescale.net>
On 1/22/08, Kumar Gala <galak@kernel.crashing.org> wrote:
> Signed-off-by: Li Yang <leoli@freescale.com>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> Documentation/powerpc/booting-without-of.txt | 30 ++++++++++++++++++++++++++
> 1 files changed, 30 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index 3584c33..387310a 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -2743,6 +2743,36 @@ platforms are moved over to use the flattened-device-tree model.
> };
> };
>
> + * Freescale 8xxx/3.0 Gb/s SATA nodes
> +
> + SATA nodes are defined to describe on-chip Serial ATA controllers.
> + Each SATA port should have its own node.
> +
> + Required properties:
> + - compatible : compatible list, contains 2 entries, first is
> + "fsl,CHIP-sata", where CHIP is the processor
> + (mpc8315, mpc8379, etc.) and the second is
> + "fsl,pq-sata"
As discussed on IRC, I don't like the approach of trying to define
generic names for these ip cores. Too much can change in the future
to make the definition of the generic type drift over time. Better to
always refer to exact chip variants.
ie. Assuming mpc8315 was the first part to contain the sata core; the
dts should claim "fsl,CHIP-sata","fsl,mpc8315-sata" instead of
"fsl,CHIP-sata","fsl,pq-sata".
It ends up being the same amount of work to support, but it doesn't
fall into the trap of making stuff up.
Another example; when describing serial ports, we still use an
*ancient* device to claim compatibility with: "ns16550". ns16550 is
specific, not generic, yet everyone still knows what it means.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-01-22 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 21:37 [PATCH] [POWERPC] Add docs for Freescale PowerQUICC SATA device tree nodes Kumar Gala
2008-01-22 21:54 ` Grant Likely [this message]
2008-01-22 22:05 ` Kumar Gala
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=fa686aa40801221354i53b5e8ebn8fc547b8eea75ebe@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=timur@freescale.com \
/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).