From: Arnd Bergmann <arnd@arndb.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
mark.rutland@arm.com, graeme.gregory@linaro.org,
marc.zyngier@arm.com, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, astone@redhat.com,
grant.likely@linaro.org, hanjun.guo@linaro.org,
Sudeep.Holla@arm.com, olof@lixom.net, jason@lakedaemon.net,
"Duran, Leo" <leo.duran@amd.com>, Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH 1/4] ata: ahci_platform: Add ACPI support for AMD Seattle SATA controller
Date: Mon, 06 Oct 2014 20:19:37 +0200 [thread overview]
Message-ID: <2026795.jAP8HDLAZo@wuerfel> (raw)
In-Reply-To: <20141006163147.GA22482@srcf.ucam.org>
On Monday 06 October 2014 17:31:47 Matthew Garrett wrote:
> On Thu, Oct 02, 2014 at 10:39:18AM +0200, Arnd Bergmann wrote:
>
> > I think part of the problem is that there is no specification for what
> > an AHCI device should look like when it's not connected to a PCI
> > bus, the AHCI document published by Intel just states:
>
> One thing that has come out of further discussion on this - ACPI defines
> a _CLS object, which allows ACPI devices to declare compatibility with a
> PCI class device. We don't have support for it at the moment, but it
> would be easy enough to add this to the kernel and then just expose the
> AHCI PCI class via _CLS. That would avoid us having problems with people
> doing similar things with USB hosts.
Interesting. Does this also define a way to get access to registers
that are normally in PCI config space, provided they are accessible at
all?
I'm guessing that it's not extremely important, given that so far all
platforms are doing ok without the power management registers or MSI,
but I guess it would be nice if we could support those.
Arnd
next prev parent reply other threads:[~2014-10-06 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1410828446-28502-1-git-send-email-suravee.suthikulpanit@amd.com>
2014-09-16 4:28 ` [RFC PATCH for AMD Seattle 0/4] Drivers for AMD-Seatlle to boot from ACPI Suravee Suthikulpanit
2014-09-16 22:56 ` Jon Masters
[not found] ` <1410828446-28502-2-git-send-email-suravee.suthikulpanit@amd.com>
2014-09-17 1:26 ` [PATCH 1/4] ata: ahci_platform: Add ACPI support for AMD Seattle SATA controller Matthew Garrett
2014-10-01 21:19 ` Suravee Suthikulanit
2014-10-02 8:39 ` Arnd Bergmann
2014-10-06 16:31 ` Matthew Garrett
2014-10-06 18:19 ` Arnd Bergmann [this message]
2014-10-06 18:21 ` Matthew Garrett
2014-10-06 18:44 ` Arnd Bergmann
2014-10-06 18:47 ` Matthew Garrett
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=2026795.jAP8HDLAZo@wuerfel \
--to=arnd@arndb.de \
--cc=Sudeep.Holla@arm.com \
--cc=astone@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=graeme.gregory@linaro.org \
--cc=grant.likely@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=jason@lakedaemon.net \
--cc=jcm@redhat.com \
--cc=leo.duran@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mjg59@srcf.ucam.org \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=suravee.suthikulpanit@amd.com \
--cc=will.deacon@arm.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).