public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Cc: linuxppc-dev@ozlabs•org, Li Yang <leoli@freescale•com>, paulus@samba•org
Subject: Re: [PATCH v3 5/9] add documentation for SATA nodes
Date: Fri, 12 Oct 2007 16:38:06 +0200	[thread overview]
Message-ID: <200710121638.07618.arnd@arndb.de> (raw)
In-Reply-To: <1192195728-24189-6-git-send-email-leoli@freescale.com>

On Friday 12 October 2007, Li Yang wrote:

> +
> +=A0=A0=A0=A0=A0=A0=A0sata@19000 {
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0compatible =3D "fsl,mpc8315=
=2Dsata";
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0reg =3D <19000 1000>;
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0interrupts =3D <2d 8>;
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0interrupt-parent =3D < &ipi=
c >;
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0phy-handle =3D < &serdes1 >;
> + =A0 =A0 =A0 =A0};

I believe we should really have a generic way to probe ATA
ports as long as they are compatible to the standard register
set, and use a generic of-ata driver for that. The two
questions arising there are:

1. Should there be a new device-type for ATA? Alternatively
   we would only look at the "compatible" property, maybe
   looking for a generic "ata" name.

2. How do we make sure the of-ata driver and the specific
   (e.g. sata_fsl) driver don't fight over the same devices?
   Would it be enough to reject all known specific devices
   in of_ata_probe?

	Arnd <><

  parent reply	other threads:[~2007-10-12 14:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 13:28 [PATCH v3 0/9] Add MPC837x generic support and MPC837xE MDS support Li Yang
2007-10-12 13:28 ` [PATCH v3 1/9] add e300c4 entry to cputable Li Yang
2007-10-12 13:28   ` [PATCH v3 2/9] ipic: add new interrupts introduced by new chip Li Yang
2007-10-12 13:28     ` [PATCH v3 3/9] add Freescale SerDes PHY support Li Yang
2007-10-12 13:28       ` [PATCH v3 4/9] add platform support for MPC837x MDS board Li Yang
2007-10-12 13:28         ` [PATCH v3 5/9] add documentation for SATA nodes Li Yang
2007-10-12 13:28           ` [PATCH v3 6/9] add documentation for SerDes nodes Li Yang
2007-10-12 13:28             ` [PATCH v3 7/9] ipic: clean up unsupported ack operations Li Yang
2007-10-12 13:28               ` [PATCH v3 8/9] add MPC837x MDS default kernel configuration Li Yang
2007-10-12 13:28                 ` [PATCH v3 9/9] add MPC837x MDS board default device tree Li Yang
2007-10-15  0:37                   ` David Gibson
2007-10-17 13:59                     ` Kumar Gala
2007-10-18 13:46                       ` Li Yang-r58472
2007-10-19 13:04                         ` Kumar Gala
2007-10-12 14:38           ` Arnd Bergmann [this message]
2007-10-17 13:47         ` [PATCH v3 4/9] add platform support for MPC837x MDS board Kumar Gala
2007-10-18  3:51           ` Li Yang-r58472
2007-10-12 14:33       ` [PATCH v3 3/9] add Freescale SerDes PHY support Arnd Bergmann
2007-10-15 12:30         ` Li Yang-r58472
2007-10-15 14:10           ` Arnd Bergmann
2007-10-14  5:59       ` Stephen Rothwell
2007-10-17 14:13       ` Kumar Gala
2007-10-18  2:46         ` Li Yang-r58472
2007-10-17 13:45     ` [PATCH v3 2/9] ipic: add new interrupts introduced by new chip Kumar Gala
2007-10-18  4:09       ` Li Yang-r58472

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=200710121638.07618.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=leoli@freescale$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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