From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@linux-foundation.org, jeff@garzik.org,
linux-ide@vger.kernel.org, alan@redhat.com, lenb@kernel.org
Subject: Re: [patch 04/30] ACPI driver support for pata
Date: Tue, 06 Mar 2007 23:18:36 +0900 [thread overview]
Message-ID: <45ED783C.6060604@gmail.com> (raw)
In-Reply-To: <20070306151415.45db1d52@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> using separate pata_acpi driver (we can definitely implement pata_acpi
>> using the helpers). It will reduce general confusion and allow
>> combining acpi cable detection with specialized device handling (e.g.
>> ACPI cable detection combined with ADMA command operation).
>
> Read the code Tejun, I did exactly that. pata_acpi is a driver which uses
> a nice clean set of helper methods I added to libata-acpi. pata_acpi
> itself knows nothing about ACPI other than calling into libata-acpi.
Actually, I have. I was thinking of higher level helpers. e.g.
pacpi_cable_detect() in libata-acpi.c such that sata_nv's cable_detect
can do.
int nv_cable_detect(struct ata_port *ap)
{
if (ck804) {
if (pacpi_cable_detect(ap) == 0)
return 0;
}
/* do original nv cable detection */
return rc;
}
So that it's more robust && we don't have to alternate between sata_nv,
pata_acpi depending on BIOS/kernel configuration, and possibly combine
other low level features with ACPI support.
--
tejun
next prev parent reply other threads:[~2007-03-06 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:37 [patch 04/30] ACPI driver support for pata akpm
2007-03-06 12:54 ` Tejun Heo
2007-03-06 15:14 ` Alan Cox
2007-03-06 14:18 ` Tejun Heo [this message]
2007-03-06 14:29 ` Alan Cox
2007-03-06 14:26 ` Jeff Garzik
2007-03-06 16:29 ` Alan Cox
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=45ED783C.6060604@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=jeff@garzik.org \
--cc=lenb@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.