All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: hotwater438@tutanota.com
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Hdegoede <hdegoede@redhat.com>,
	Linux Gpio <linux-gpio@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: intel: Clear interrupt status in unmask callback
Date: Tue, 23 Apr 2019 12:08:16 +0300	[thread overview]
Message-ID: <20190423090816.GN2654@lahna.fi.intel.com> (raw)
In-Reply-To: <Ld8QGex--3-1@tutanota.com>

On Tue, Apr 23, 2019 at 11:00:48AM +0200, hotwater438@tutanota.com 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.

  parent reply	other threads:[~2019-04-23  9:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  4:45 [PATCH] pinctrl: intel: Clear interrupt status in unmask callback Kai-Heng Feng
     [not found] ` <Ld5HCy5--3-1@tutanota.com>
2019-04-23  4:57   ` Kai-Heng Feng
     [not found]     ` <Ld8QGex--3-1@tutanota.com>
2019-04-23  9:08       ` Mika Westerberg [this message]
     [not found]         ` <Ld8ZLG1--3-1@tutanota.com>
2019-04-23  9:47           ` Kai-Heng Feng
     [not found]             ` <Ld9SLAo--3-1@tutanota.com>
2019-04-25  5:16               ` Kai Heng Feng
2019-04-25  9:11 ` Mika Westerberg
2019-04-26 21:47 ` Andy Shevchenko
2019-04-29  9:16   ` Kai-Heng Feng
2019-04-29 13:13     ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190423090816.GN2654@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=hotwater438@tutanota.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.