linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@linux.intel.com>,
	linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH RFC] ata: Intel IDE-R support
Date: Wed, 18 Aug 2010 16:10:16 +0200	[thread overview]
Message-ID: <4C6BE9C8.4030803@kernel.org> (raw)
In-Reply-To: <20100818110306.03ce2fbc@lxorguk.ukuu.org.uk>

Hello,

On 08/18/2010 12:03 PM, Alan Cox wrote:
>> Sure, the thing is that your patch doesn't mean we don't have to keep
>> ata_piix device table up-to-date.  We would still need to be
>> maintaining that table whether ata_generic can detect IDE-R by itself
> 
> I'm not sure I follow

I was trying to say that IDE-R basically being the complement of Intel
IDE's not drive by ata_piix, we don't need to maintain a separate PCI
device ID table for IDE-R's.

>> or not.  The device ID table in ata_piix is given, and ata_generic
>> picking up the rest of intel IDE's wouldn't miss anything.  So, unless
>> IDE-R devices need some special treatment, I don't really see how the
>> detection code would be useful.
> 
> The trend is towards AHCI so the problem goes away for the other bits.

Yeah, it has helped a lot but ata_piix's are here to stay for the
foreseeable future and we'll be maintaining its device ID table.

> IDE-R is not ata_piix drivable, and lots of the ICH stuff really wants
> driving via ata_piix, so having the generic driver grab all intel stuff
> isn't as far as I can see going to be safe given a system may load the
> ata_generic module but not PIIX then meet a piix by hotplug.

That's the reason why we have module priorities.  The link priority
becomes module priority and modprobe will deterministically prefer
ata_piix over ata_generic if a controller is supported by both.

Thanks.

-- 
tejun

  reply	other threads:[~2010-08-18 14:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 15:56 [PATCH RFC] ata: Intel IDE-R support Alan Cox
2010-08-10 17:12 ` Sergei Shtylyov
2010-08-10 22:23   ` Alan Cox
2010-08-17 16:19 ` Tejun Heo
2010-08-17 16:42   ` Alan Cox
2010-08-17 16:30     ` Tejun Heo
2010-08-17 17:01       ` Alan Cox
2010-08-17 16:59         ` Tejun Heo
2010-08-17 18:23           ` Alan Cox
2010-08-18  6:19             ` Tejun Heo
2010-08-18 10:03               ` Alan Cox
2010-08-18 14:10                 ` Tejun Heo [this message]
2010-08-18 15:15                   ` Alan Cox
2010-08-19  9:37                     ` Tejun Heo
2010-08-19 10:09                       ` Alan Cox
2010-08-19 11:22                         ` Tejun Heo
2010-08-19 11:35                           ` Kay Sievers
2010-08-19 11:42                             ` Tejun Heo
2010-08-19 12:24                               ` Kay Sievers
2010-08-19 12:33                                 ` Tejun Heo
2010-08-19 12:52                                   ` Kay Sievers
2010-08-19 12:54                                     ` Tejun Heo
2010-08-19 13:08                                       ` Kay Sievers
2010-08-19 13:14                                         ` Tejun Heo
2010-08-19 12:56                           ` Tejun Heo
2010-08-19 18:05                             ` Jeff Garzik
2010-08-19 11:02                       ` Tim Small

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=4C6BE9C8.4030803@kernel.org \
    --to=tj@kernel.org \
    --cc=alan@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.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).