linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Li Yang" <leoli@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH v7 5/9] add documentation for SATA nodes
Date: Fri, 19 Oct 2007 09:41:47 -0600	[thread overview]
Message-ID: <fa686aa40710190841q4f0c5ceao29ee55cc7fa2ff04@mail.gmail.com> (raw)
In-Reply-To: <1192793930-26039-6-git-send-email-leoli@freescale.com>

On 10/19/07, Li Yang <leoli@freescale.com> wrote:
> Signed-off-by: Li Yang <leoli@freescale.com>
> ---
>  Documentation/powerpc/booting-without-of.txt |   32 ++++++++++++++++++++++++++
>  1 files changed, 32 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index a96e853..8d49942 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -2242,6 +2242,38 @@ platforms are moved over to use the flattened-device-tree model.
>                            available.
>                            For Axon: 0x0000012a
>
> +    o) SATA nodes
> +
> +    SATA nodes are defined to describe on-chip Serial ATA controllers.
> +
> +    Required properties:
> +
> +    - compatible : Should specify what this SATA controller is compatible
> +      with.
> +    - reg : Offset and length of the register set for the device.
> +    - interrupts : <a b> where a is the interrupt number and b is a
> +      field that represents an encoding of the sense and level
> +      information for the interrupt.  This should be encoded based on
> +      the information in section 2) depending on the type of interrupt
> +      controller you have.
> +    - interrupt-parent : the phandle for the interrupt controller that
> +      services interrupts for this device.
> +
> +    Recommended properties :
> +
> +    - phy-handle : Some SATA controller uses a shared SerDes PHY. This
> +      property should specify the phandle of the SerDes node.

I'm not sure about this property.  Does the driver need to know about
this?  Will this setup ever change at runtime?  It seems to me that
like GPIOs and chip selects, setting you which shared PHY goes with
which device is something that should be done at board setup time.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  parent reply	other threads:[~2007-10-19 15:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 11:38 [PATCH v7 0/9] Add MPC837x generic support and MPC837xE MDS support Li Yang
2007-10-19 11:38 ` [PATCH v7 1/9] add e300c4 entry to cputable Li Yang
2007-10-19 11:38   ` [PATCH v7 2/9] ipic: add new interrupts introduced by new chip Li Yang
2007-10-19 11:38     ` [PATCH v7 3/9] add Freescale SerDes PHY support Li Yang
2007-10-19 11:38       ` [PATCH v7 4/9] add platform support for MPC837x MDS board Li Yang
2007-10-19 11:38         ` [PATCH v7 5/9] add documentation for SATA nodes Li Yang
2007-10-19 11:38           ` [PATCH v7 6/9] add documentation for SerDes nodes Li Yang
2007-10-19 11:38             ` [PATCH v7 7/9] ipic: clean up unsupported ack operations Li Yang
2007-10-19 11:38               ` [PATCH v7 8/9] add MPC837x MDS default kernel configuration Li Yang
2007-10-19 11:38                 ` [PATCH v7 9/9] add MPC837x MDS board default device tree Li Yang
2007-11-30  0:44                   ` Kumar Gala
2007-11-30  9:55                     ` Li Yang
2007-11-30  0:37                 ` [PATCH v7 8/9] add MPC837x MDS default kernel configuration Kumar Gala
2007-11-30  0:35               ` [PATCH v7 7/9] ipic: clean up unsupported ack operations Kumar Gala
2007-11-30 10:03                 ` Li Yang
2007-11-30 14:48                   ` Kumar Gala
2007-10-19 15:41           ` Grant Likely [this message]
2007-11-30  0:34         ` [PATCH v7 4/9] add platform support for MPC837x MDS board Kumar Gala
2007-10-19 15:35       ` [PATCH v7 3/9] add Freescale SerDes PHY support Grant Likely
2007-11-21  3:31         ` Kumar Gala
2007-11-21  3:48           ` Liu Dave
2007-11-21  3:48           ` Li Yang
2007-11-21  4:01             ` Kumar Gala
2007-11-21  4:05               ` Kumar Gala
2007-11-21  8:42             ` Benjamin Herrenschmidt
2007-11-30  0:34     ` [PATCH v7 2/9] ipic: add new interrupts introduced by new chip Kumar Gala
2007-11-30  0:33   ` [PATCH v7 1/9] add e300c4 entry to cputable 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=fa686aa40710190841q4f0c5ceao29ee55cc7fa2ff04@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=leoli@freescale.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).