Chen Yu ( changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #3 from Chen Yu ( ---
(In reply to Robin Lee from comment #2)
> (In reply to Chen Yu from comment #1)
> > (In reply to Robin Lee from comment #0)
> > > With "deep" mem_sleep, every thing works well on my ThinkPad X1 Tablet.
> > > But since commit included in 4.14
> > > e870c6c87cf9484090d28f2a68aa29e008960c93
> > > "ACPI / PM: Prefer suspend-to-idle over S3 on some systems",
> > > the preference is changed to 's2idle'.
> > > 
> > > 's2idle' seems to work by itself, but does not co-operate with the power
> > > button and
> > > gravity sensor. The most annoying thing is that the breathing LED light
> is
> > > just shut off at
> > > s2idle.
> > Do you mean, the system could not be woken up via power button, or? Not
> > quite sure what your concern is here.
> The system sometimes could not be woken up via power button when in 's2idle'
> mem_sleep.
> I don't actually concern with what the strange issues with 's2idle'
> mem_sleep. My tablet works fine with 'deep' mem_sleep.
> What I actually care about is why my tablet was detected and set to 's2idle'
> mem_sleep by default.
Because your system has told the linux:
(1) the ACPI_FADT_LOW_POWER_S0 flag is set in the FADT and
(2) the Low Power Idle S0 _DSM interface has been discovered and
Which means that it support s0ix AKA suspend to idle, so.. 
not sure if we should maintain a list in the code, add Rafael too.

You are receiving this mail because:
You are watching the assignee of the bug.
Check out the vibrant tech community on one of the world's most
engaging tech sites,!
acpi-bugzilla mailing list

Reply via email to