Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-18 Thread Daniel Drake
On Mon, Mar 19, 2018 at 6:36 AM, Rafael J. Wysocki wrote: > On Fri, Mar 16, 2018 at 10:06 AM, Mathias Nyman > wrote: >> Adding Rafael directly to CC >> >> In short, if _S3D and _S3W are missing in DSDT then a PCI device >> stays in D0 during

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-18 Thread Rafael J. Wysocki
On Fri, Mar 16, 2018 at 10:06 AM, Mathias Nyman wrote: > Adding Rafael directly to CC > > In short, if _S3D and _S3W are missing in DSDT then a PCI device > stays in D0 during suspend in Linux, but goes to D3 in Windows. > > USB wake doesn't work in Geminilake

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-16 Thread Mathias Nyman
Adding Rafael directly to CC In short, if _S3D and _S3W are missing in DSDT then a PCI device stays in D0 during suspend in Linux, but goes to D3 in Windows. USB wake doesn't work in Geminilake because of this. Should this be changed? reasoning below. On 16.03.2018 10:23, Daniel Drake wrote:

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-16 Thread Daniel Drake
> I've studied the ACPI spec trying to understand better, but I'm > struggling with the question: > What is the maximum number (lowest power) permitted device power state > for a device that is configured as able to wake the system from S3, > **that does not implement the _S3W method**? Actually

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-16 Thread Daniel Drake
Hi, I'm working alongside Chris on this issue. On Fri, Mar 16, 2018 at 12:11 AM, Mathias Nyman wrote: > Scope (_SB.PCI0.XHC) has _PS0 method, so Linux will look for a _S3W to get > the > lowest possible D state in S3, but_S3W is missing, so Linux pci-acpi code >

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-15 Thread Mathias Nyman
On 15.03.2018 15:28, Chris Chiu wrote: On Thu, Mar 15, 2018 at 7:46 PM, Mathias Nyman wrote: On 15.03.2018 06:40, Chris Chiu wrote: Hi, I have a ASUS AIO V222GA and another Acer Desktop XC-830 both have Intel CPU J5005 and they both hit the same problem.

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-15 Thread Chris Chiu
On Thu, Mar 15, 2018 at 7:46 PM, Mathias Nyman wrote: > On 15.03.2018 06:40, Chris Chiu wrote: >> >> Hi, >> I have a ASUS AIO V222GA and another Acer Desktop XC-830 both >> have Intel CPU J5005 and they both hit the same problem. The XHCI >> connected USB

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-15 Thread Mathias Nyman
On 15.03.2018 06:40, Chris Chiu wrote: Hi, I have a ASUS AIO V222GA and another Acer Desktop XC-830 both have Intel CPU J5005 and they both hit the same problem. The XHCI connected USB keyboard/mouse can never wakeup the system from suspend. It reminds me that similiar thing happens on

Intel GemniLake xHCI connected devices can never wake up the system from suspend

2018-03-14 Thread Chris Chiu
Hi, I have a ASUS AIO V222GA and another Acer Desktop XC-830 both have Intel CPU J5005 and they both hit the same problem. The XHCI connected USB keyboard/mouse can never wakeup the system from suspend. It reminds me that similiar thing happens on ApolloLake too which needs the