linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Feng Kan <fkan@amcc.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Mark Miesfeld <miesfeld@gmail.com>,
	linuxppc-dev@ozlabs.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/2] Added support for Designware SATA controller driver
Date: Wed, 06 May 2009 10:44:24 -0700	[thread overview]
Message-ID: <4A01CC78.3060004@amcc.com> (raw)
In-Reply-To: <49FB68F2.10301@freescale.com>

Hi Scott:

I agree with your statement, however this driver is wrapped with this 
AHB DMA controller.
It would be very hard for it to work on non 460EX platforms. I can 
expand the depend in
the future if it is available on more cores.

Thanks
Feng Kan

Scott Wood wrote:
> Feng Kan wrote:
>> This adds support for the Designware SATA controller.
>>
>> Signed-off-by: Feng Kan <fkan@amcc.com>
>> Signed-off-by: Mark Miesfeld <miesfeld@gmail.com>
>> ---
>>  drivers/ata/Kconfig    |   10 +
>>  drivers/ata/Makefile   |    1 +
>>  drivers/ata/sata_dwc.c | 2053 
>> ++++++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 2064 insertions(+), 0 deletions(-)
>>  create mode 100644 drivers/ata/sata_dwc.c
>>
>> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
>> index 0bcf264..c3d0b24 100644
>> --- a/drivers/ata/Kconfig
>> +++ b/drivers/ata/Kconfig
>> @@ -72,6 +72,16 @@ config SATA_FSL
>>  
>>        If unsure, say N.
>>  
>> +config SATA_DWC
>> +    tristate "DesignWare Cores SATA support"
>> +     depends on 460EX
>
> That "depends" looks too specific -- we don't want to grow a list if 
> this controller gets added to other chips.
>
> Only depend on what this driver actually needs in order to function.
>
> -Scott

  reply	other threads:[~2009-05-06 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 21:02 [PATCH 1/2] Added support for Designware SATA controller driver Feng Kan
2009-05-01 21:26 ` Scott Wood
2009-05-06 17:44   ` Feng Kan [this message]
2009-05-01 23:20 ` Wolfgang Denk
2009-05-02  0:05   ` Jeff Garzik

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=4A01CC78.3060004@amcc.com \
    --to=fkan@amcc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miesfeld@gmail.com \
    --cc=scottwood@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).