From: Adrian Hunter <adrian.hunter@intel.com>
To: Chris Ball <cjb@laptop.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-mmc@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Add SDHCI ACPI driver
Date: Thu, 22 Nov 2012 16:46:10 +0200 [thread overview]
Message-ID: <50AE3AB2.2070307@intel.com> (raw)
In-Reply-To: <87k3tdagim.fsf@octavius.laptop.org>
On 22/11/12 15:55, Chris Ball wrote:
> Hi,
>
> On Thu, Nov 22 2012, Adrian Hunter wrote:
>> Here is SDHCI ACPI driver. It is dependent on new ACPI Platform support
>> so I suggest Rafael takes the patches with Chris' Ack.
>>
>> Please note that I would prefer this to be queued for 3.8
>
> Looks fine:
>
> Acked-by: Chris Ball <cjb@laptop.org>
Thank you!
>
> I have some dumb questions, though -- what kind of platforms ship with
> these devices? Do they ever have the controller on PCI too, and what
> happens with sdhci-pci vs. sdhci-acpi in that case?
Since the arrival of ACPI5, platform devices can be configured using ACPI
tables. PCI can also be used, but the firmware ensures that the same
device is not enumerated via both ACPI and PCI.
Rafael can you take these patches?
next prev parent reply other threads:[~2012-11-22 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:43 [PATCH 0/3] Add SDHCI ACPI driver Adrian Hunter
2012-11-22 8:43 ` [PATCH 1/3] PNPACPI: exclude SDHCI devices Adrian Hunter
2012-11-22 8:43 ` [PATCH 2/3] ACPI: add SDHCI to ACPI platform devices Adrian Hunter
2012-11-22 8:43 ` [PATCH 3/3] mmc: sdhci-acpi: add SDHCI ACPI driver Adrian Hunter
2012-11-23 9:44 ` Mika Westerberg
2012-11-22 13:55 ` [PATCH 0/3] Add " Chris Ball
2012-11-22 14:46 ` Adrian Hunter [this message]
2012-11-22 21:24 ` Rafael J. Wysocki
2012-11-23 9:34 ` Mika Westerberg
2012-11-23 10:13 ` Adrian Hunter
2012-11-23 10:50 ` Rafael J. Wysocki
2012-11-23 10:23 ` Adrian Hunter
2012-11-23 10:51 ` Rafael J. Wysocki
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=50AE3AB2.2070307@intel.com \
--to=adrian.hunter@intel.com \
--cc=cjb@laptop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
/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).