On Mon, Oct 06, 2014 at 08:44:35PM +0200, Arnd Bergmann wrote:
> On Monday 06 October 2014 19:21:53 Matthew Garrett wrote:
> > Unfortunately not. I'd assume that PM registers are expected to be
> > accessed via the _PS* methods instead. Does MSI make sense outside the
> > context of PCI interrupt
On Monday 06 October 2014 19:21:53 Matthew Garrett wrote:
> On Mon, Oct 06, 2014 at 08:19:37PM +0200, Arnd Bergmann wrote:
>
> > 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?
>
> Unfortunatel
On Mon, Oct 06, 2014 at 08:19:37PM +0200, Arnd Bergmann wrote:
> 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?
Unfortunately not. I'd assume that PM registers are expected to be
accessed via the
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 pu
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 furthe
On Wednesday 01 October 2014 16:19:37 Suravee Suthikulanit wrote:
> On 9/16/2014 8:26 PM, Matthew Garrett wrote:
> > On Mon, Sep 15, 2014 at 07:47:23PM -0500, suravee.suthikulpa...@amd.com
> > wrote:
> >> From: Suravee Suthikulpanit
> >>
> >> This patch adds ACPI match table in ahci_platform. The
On 9/16/2014 8:26 PM, Matthew Garrett wrote:
On Mon, Sep 15, 2014 at 07:47:23PM -0500, suravee.suthikulpa...@amd.com wrote:
From: Suravee Suthikulpanit
This patch adds ACPI match table in ahci_platform. The table includes
the acpi_device_id to match AMD Seattle SATA controller with following
a
On Mon, Sep 15, 2014 at 07:47:23PM -0500, suravee.suthikulpa...@amd.com wrote:
> From: Suravee Suthikulpanit
>
> This patch adds ACPI match table in ahci_platform. The table includes
> the acpi_device_id to match AMD Seattle SATA controller with following
> asl structure in DSDT:
>
> Device
From: Suravee Suthikulpanit
This patch adds ACPI match table in ahci_platform. The table includes
the acpi_device_id to match AMD Seattle SATA controller with following
asl structure in DSDT:
Device (SATA0)
{
Name(_HID, "AMDI0600")// Seattle AHSATA
Name (_CCA, 1)
9 matches
Mail list logo
