On Tue, Jun 20, 2017 at 2:32 AM, Alan Stern wrote:
>
> It's possible that the test was invalid. Kai-Heng did not say whether
> /sys/.../power/wakeup was set to "enabled" for both the EHCI controller
> and the USB root hub beneath it, before the test was started. If
> either of them was set to "d
On Monday, June 19, 2017 02:32:57 PM Alan Stern wrote:
> On Mon, 19 Jun 2017, Bjorn Helgaas wrote:
>
> > > > Have you tested it with system suspend? That is, if you suspend the
> > > > whole computer, does plugging or unplugging a USB device cause the
> > > > system to wake up?
> > >
> > > No, t
On Mon, 19 Jun 2017, Bjorn Helgaas wrote:
> > > Have you tested it with system suspend? That is, if you suspend the
> > > whole computer, does plugging or unplugging a USB device cause the
> > > system to wake up?
> >
> > No, the system will not wake up when plugging or unplugging.
> > Tried sev
On Mon, Jun 19, 2017 at 11:30:18AM +0800, Kai-Heng Feng wrote:
> On Sat, Jun 17, 2017 at 1:30 AM, Alan Stern wrote:
> > On Sat, 17 Jun 2017, Kai-Heng Feng wrote:
> >
> >> On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
> >> wrote:
> >> > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
> >> > wrote
On Sat, Jun 17, 2017 at 1:30 AM, Alan Stern wrote:
> On Sat, 17 Jun 2017, Kai-Heng Feng wrote:
>
>> On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
>> wrote:
>> > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
>> > wrote:
>> >> Those documents refer to a hardware bug with a workaround in the BIOS
On Sat, 17 Jun 2017, Kai-Heng Feng wrote:
> On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
> wrote:
> > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
> > wrote:
> >> Those documents refer to a hardware bug with a workaround in the BIOS.
> >> Have you checked to see if your BIOS is up to date?
>
On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
wrote:
> On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
> wrote:
>> Those documents refer to a hardware bug with a workaround in the BIOS.
>> Have you checked to see if your BIOS is up to date?
>
> Yes, it's up to date.
>
Alan, I re-sent a patch but
On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern wrote:
> On Thu, 15 Jun 2017, Kai-Heng Feng wrote:
>
>> On Wed, Jun 14, 2017 at 1:28 AM, Bjorn Helgaas wrote:
>> >
>> > The lspci output [1] shows:
>> >
>> > 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
>> > Controller (re
On Thu, 15 Jun 2017, Kai-Heng Feng wrote:
> On Wed, Jun 14, 2017 at 1:28 AM, Bjorn Helgaas wrote:
> >
> > The lspci output [1] shows:
> >
> > 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
> > Controller (rev 39) (prog-if 20 [EHCI])
> > Capabilities: [c0] Power Man
On Thu, Jun 15, 2017 at 03:02:25PM +0800, Kai-Heng Feng wrote:
> On Thu, Jun 15, 2017 at 2:55 AM, Alan Stern wrote:
> > On Tue, 13 Jun 2017, Bjorn Helgaas wrote:
> >
> >> [+cc Rafael, linux-pm]
> >>
> >> On Tue, Jun 13, 2017 at 12:21:15PM +0800, Kai-Heng Feng wrote:
> >> > On Mon, Jun 12, 2017 at
On Thu, Jun 15, 2017 at 2:55 AM, Alan Stern wrote:
> On Tue, 13 Jun 2017, Bjorn Helgaas wrote:
>
>> [+cc Rafael, linux-pm]
>>
>> On Tue, Jun 13, 2017 at 12:21:15PM +0800, Kai-Heng Feng wrote:
>> > On Mon, Jun 12, 2017 at 10:18 PM, Alan Stern
>> > wrote:
>> > > Let's get some help from people who
On Wed, Jun 14, 2017 at 1:28 AM, Bjorn Helgaas wrote:
>
> The lspci output [1] shows:
>
> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
> Controller (rev 39) (prog-if 20 [EHCI])
> Capabilities: [c0] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ Aux
On Tue, 13 Jun 2017, Bjorn Helgaas wrote:
> [+cc Rafael, linux-pm]
>
> On Tue, Jun 13, 2017 at 12:21:15PM +0800, Kai-Heng Feng wrote:
> > On Mon, Jun 12, 2017 at 10:18 PM, Alan Stern
> > wrote:
> > > Let's get some help from people who understand PCI well.
> > >
> > > Here's the general problem
[+cc Rafael, linux-pm]
On Tue, Jun 13, 2017 at 12:21:15PM +0800, Kai-Heng Feng wrote:
> On Mon, Jun 12, 2017 at 10:18 PM, Alan Stern
> wrote:
> > Let's get some help from people who understand PCI well.
> >
> > Here's the general problem: Kai-Heng has a PCI-based USB host
> > controller that adv
On Mon, Jun 12, 2017 at 10:18 PM, Alan Stern wrote:
> Let's get some help from people who understand PCI well.
>
> Here's the general problem: Kai-Heng has a PCI-based USB host
> controller that advertises wakeup capability from D3, but it doesn't
> assert PME# from D3 when it should. For "lspci
Let's get some help from people who understand PCI well.
Here's the general problem: Kai-Heng has a PCI-based USB host
controller that advertises wakeup capability from D3, but it doesn't
assert PME# from D3 when it should. For "lspci -vv" output, see
http://marc.info/?l=linux-usb&m=14
On Mon, Jun 12, 2017 at 3:04 PM, Kai-Heng Feng
wrote:
> On Fri, Jun 9, 2017 at 10:43 PM, Alan Stern wrote:
>> On Fri, 9 Jun 2017, Kai-Heng Feng wrote:
>>
>> Is this really the right solution? Maybe it would be better to allow
>> the controller to go into D3 provided no wakeup signal is needed.
On Fri, Jun 9, 2017 at 10:43 PM, Alan Stern wrote:
> On Fri, 9 Jun 2017, Kai-Heng Feng wrote:
>
>> As Alan Stern points out [1], the PME signal is not enabled when
>> controller is in D3, therefore it's not being woken up when new deivces
>> get plugged in.
>>
>> Workaround this bug by preventing
On Fri, 9 Jun 2017, Kai-Heng Feng wrote:
> As Alan Stern points out [1], the PME signal is not enabled when
> controller is in D3, therefore it's not being woken up when new deivces
> get plugged in.
>
> Workaround this bug by preventing the controller enters D3 power state.
>
> [1] https://www.
As Alan Stern points out [1], the PME signal is not enabled when
controller is in D3, therefore it's not being woken up when new deivces
get plugged in.
Workaround this bug by preventing the controller enters D3 power state.
[1] https://www.spinics.net/lists/linux-usb/msg157462.html
Signed-off-b
20 matches
Mail list logo
