On Wed, Aug 14, 2019 at 01:26:56AM +0200, Rafael J. Wysocki wrote:
> On Tuesday, August 6, 2019 3:36:38 PM CEST Bjorn Helgaas wrote:
> > On Mon, Aug 05, 2019 at 11:02:51PM +0200, Rafael J. Wysocki wrote:
> > > On Mon, Aug 5, 2019 at 10:52 PM Bjorn Helgaas wrote:
> > > >
> > > > pci_check_pme_statu
On Tuesday, August 6, 2019 3:36:38 PM CEST Bjorn Helgaas wrote:
> On Mon, Aug 05, 2019 at 11:02:51PM +0200, Rafael J. Wysocki wrote:
> > On Mon, Aug 5, 2019 at 10:52 PM Bjorn Helgaas wrote:
> > >
> > > pci_check_pme_status() reads the Power Management capability to determine
> > > whether a device
On Mon, Aug 05, 2019 at 11:02:51PM +0200, Rafael J. Wysocki wrote:
> On Mon, Aug 5, 2019 at 10:52 PM Bjorn Helgaas wrote:
> >
> > pci_check_pme_status() reads the Power Management capability to determine
> > whether a device has generated a PME. The capability is in config space,
> > which is acc
On Mon, Aug 5, 2019 at 10:52 PM Bjorn Helgaas wrote:
>
> From: Bjorn Helgaas
>
> pci_check_pme_status() reads the Power Management capability to determine
> whether a device has generated a PME. The capability is in config space,
> which is accessible in D0, D1, D2, and D3hot, but not in D3cold.
From: Bjorn Helgaas
pci_check_pme_status() reads the Power Management capability to determine
whether a device has generated a PME. The capability is in config space,
which is accessible in D0, D1, D2, and D3hot, but not in D3cold.
If we call pci_check_pme_status() on a device that's in D3cold,
5 matches
Mail list logo