at 21:45, Bjorn Helgaas wrote:
On Fri, Jul 05, 2019 at 03:02:01PM +0800, Kai-Heng Feng wrote:
at 19:57, Bjorn Helgaas wrote:
On Mon, May 27, 2019 at 11:57:47AM -0500, Bjorn Helgaas wrote:
I'm wondering if this platform has a firmware defect. Here's my
thinking. The xHC is a Root Complex
On Fri, Jul 05, 2019 at 03:02:01PM +0800, Kai-Heng Feng wrote:
> at 19:57, Bjorn Helgaas wrote:
> > On Mon, May 27, 2019 at 11:57:47AM -0500, Bjorn Helgaas wrote:
> > > I'm wondering if this platform has a firmware defect. Here's my
> > > thinking. The xHC is a Root Complex Integrated Endpoint,
at 17:39, Rafael J. Wysocki wrote:
On Friday, July 5, 2019 9:02:01 AM CEST Kai-Heng Feng wrote:
at 19:57, Bjorn Helgaas wrote:
On Mon, May 27, 2019 at 11:57:47AM -0500, Bjorn Helgaas wrote:
On Thu, May 23, 2019 at 12:39:23PM +0800, Kai-Heng Feng wrote:
at 04:52, Bjorn Helgaas wrote:
On
On Friday, July 5, 2019 9:02:01 AM CEST Kai-Heng Feng wrote:
> at 19:57, Bjorn Helgaas wrote:
>
> > On Mon, May 27, 2019 at 11:57:47AM -0500, Bjorn Helgaas wrote:
> >> On Thu, May 23, 2019 at 12:39:23PM +0800, Kai-Heng Feng wrote:
> >>> at 04:52, Bjorn Helgaas wrote:
> On Wed, May 22, 2019
at 19:57, Bjorn Helgaas wrote:
On Mon, May 27, 2019 at 11:57:47AM -0500, Bjorn Helgaas wrote:
On Thu, May 23, 2019 at 12:39:23PM +0800, Kai-Heng Feng wrote:
at 04:52, Bjorn Helgaas wrote:
On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
On Wed, 22 May 2019, Bjorn Helgaas wrote:
On Mon, May 27, 2019 at 11:57:47AM -0500, Bjorn Helgaas wrote:
> On Thu, May 23, 2019 at 12:39:23PM +0800, Kai-Heng Feng wrote:
> > at 04:52, Bjorn Helgaas wrote:
> > > On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
> > > > On Wed, 22 May 2019, Bjorn Helgaas wrote:
> > > > > On Wed, M
On Thu, May 23, 2019 at 12:39:23PM +0800, Kai-Heng Feng wrote:
> at 04:52, Bjorn Helgaas wrote:
> > On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
> > > On Wed, 22 May 2019, Bjorn Helgaas wrote:
> > > > On Wed, May 22, 2019 at 11:46:25PM +0800, Kai Heng Feng wrote:
> > > > > > On May
at 04:52, Bjorn Helgaas wrote:
On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
On Wed, 22 May 2019, Bjorn Helgaas wrote:
On Wed, May 22, 2019 at 11:46:25PM +0800, Kai Heng Feng wrote:
On May 22, 2019, at 9:48 PM, Bjorn Helgaas wrote:
On Wed, May 22, 2019 at 11:42:14AM +0800, Kai
On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
> On Wed, 22 May 2019, Bjorn Helgaas wrote:
> > On Wed, May 22, 2019 at 11:46:25PM +0800, Kai Heng Feng wrote:
> > > > On May 22, 2019, at 9:48 PM, Bjorn Helgaas wrote:
> > > > On Wed, May 22, 2019 at 11:42:14AM +0800, Kai Heng Feng wrote
> On May 23, 2019, at 2:53 AM, Lukas Wunner wrote:
>
> On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
>> According to Kai, PME signalling doesn't work in D0 -- or at least, it
>> is _documented_ not to work in D0 -- even though it is enabled and the
>> device claims to support it.
On Wed, May 22, 2019 at 02:39:56PM -0400, Alan Stern wrote:
> According to Kai, PME signalling doesn't work in D0 -- or at least, it
> is _documented_ not to work in D0 -- even though it is enabled and the
> device claims to support it.
>
> In any case, I don't really see any point in "runtime sus
On Wed, 22 May 2019, Bjorn Helgaas wrote:
> On Wed, May 22, 2019 at 11:46:25PM +0800, Kai Heng Feng wrote:
> > > On May 22, 2019, at 9:48 PM, Bjorn Helgaas wrote:
> > > On Wed, May 22, 2019 at 11:42:14AM +0800, Kai Heng Feng wrote:
> > >> at 6:23 AM, Bjorn Helgaas wrote:
> > >>> On Wed, May 22,
On Wed, May 22, 2019 at 11:46:25PM +0800, Kai Heng Feng wrote:
> > On May 22, 2019, at 9:48 PM, Bjorn Helgaas wrote:
> > On Wed, May 22, 2019 at 11:42:14AM +0800, Kai Heng Feng wrote:
> >> at 6:23 AM, Bjorn Helgaas wrote:
> >>> On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
>
> On May 22, 2019, at 9:48 PM, Bjorn Helgaas wrote:
>
> On Wed, May 22, 2019 at 11:42:14AM +0800, Kai Heng Feng wrote:
>> at 6:23 AM, Bjorn Helgaas wrote:
>>> On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
There's an xHC device that doesn't wake when a USB device gets plu
On Wed, May 22, 2019 at 11:42:14AM +0800, Kai Heng Feng wrote:
> at 6:23 AM, Bjorn Helgaas wrote:
> > On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
> > > There's an xHC device that doesn't wake when a USB device gets plugged
> > > to its USB port. The driver's own runtime suspend
at 6:23 AM, Bjorn Helgaas wrote:
[+cc Mathias, linux-usb]
On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
There's an xHC device that doesn't wake when a USB device gets plugged
to its USB port. The driver's own runtime suspend callback was called,
PME signaling was enabled, but
[+cc Mathias, linux-usb]
On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
> There's an xHC device that doesn't wake when a USB device gets plugged
> to its USB port. The driver's own runtime suspend callback was called,
> PME signaling was enabled, but it stays at PCI D0.
s/xHC/xHCI
There's an xHC device that doesn't wake when a USB device gets plugged
to its USB port. The driver's own runtime suspend callback was called,
PME signaling was enabled, but it stays at PCI D0.
A PCI device can be runtime suspended to D0 when it supports D0 PME and
its _S0W reports D0. Theoraticall
18 matches
Mail list logo