On Tue, Oct 15, 2019 at 9:20 PM Bjorn Helgaas wrote:
>
> On Mon, Oct 14, 2019 at 01:25:00PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > There is an arbitrary difference between the system resume and
> > runtime resume code paths for PCI devices regarding the delay to
> > a
On Mon, Oct 14, 2019 at 01:25:00PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> There is an arbitrary difference between the system resume and
> runtime resume code paths for PCI devices regarding the delay to
> apply when switching the devices from D3cold to D0.
>
> Namely, pci
On Tue, Oct 15, 2019 at 7:11 AM Daniel Drake wrote:
>
> On Mon, Oct 14, 2019 at 7:25 PM Rafael J. Wysocki wrote:
> > Since there is no reason for that difference to exist, modify
> > pci_power_up() to follow pci_set_power_state() more closely and
> > invoke __pci_start_power_transition() from the
On Mon, Oct 14, 2019 at 7:25 PM Rafael J. Wysocki wrote:
> Since there is no reason for that difference to exist, modify
> pci_power_up() to follow pci_set_power_state() more closely and
> invoke __pci_start_power_transition() from there to call the
> platform firmware to power up the device (in c
4 matches
Mail list logo