On Tue, Apr 23, 2019 at 11:00:48AM +0200, hotwater438@xxxxxxxxxxxx wrote: > Hi. > > Honestly, I can't find any information about my acpi suspend type. > There are no options in my BIOS to change it, and I can't determine > which exactly I have. But I suppose I have a S3 because I have suspend > issue. > > Can I somehow determine it in Linux? I did a research but found nothing > on the internet. You can read the default mode from /sys/power/mem_sleep. "s2idle" means, well suspend-to-idle and "deep" means S3.
Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
- From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
- Date: Tue, 23 Apr 2019 12:08:16 +0300
- In-reply-to: <Ld8QGex--3-1@tutanota.com>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20190422044539.16085-1-kai.heng.feng@canonical.com> <Ld5HCy5--3-1@tutanota.com> <EA207DE8-E89A-427B-B910-A36170A76031@canonical.com> <Ld8QGex--3-1@tutanota.com>
- User-agent: Mutt/1.11.3 (2019-02-01)
- References:
- [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
- From: Kai-Heng Feng
- Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
- From: Kai-Heng Feng
- [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
- Prev by Date: [PATCH v10 01/11] dt-bindings: mfd: add DT bindings for max77650
- Next by Date: Re: [PATCH v3] gpio: merrifield: Fix build err without CONFIG_ACPI
- Previous by thread: Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
- Next by thread: Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
- Index(es):
 |