Linux ACPI
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Johannes Stezenbach <js@sig21.net>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	linux-clk@vger.kernel.org, linux-pm@vger.kernel.org,
	Carlo Caione <carlo@endlessm.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Darren Hart <dvhart@infradead.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Takashi Iwai <tiwai@suse.de>,
	linux-acpi@vger.kernel.org
Subject: Re: S0ix failure due to "clk: x86: Do not gate clocks enabled by the firmware"
Date: Thu, 21 Sep 2017 16:21:46 +0200	[thread overview]
Message-ID: <4036229.gTT6xKEFIS@aspire.rjw.lan> (raw)
In-Reply-To: <20170921094013.hznamkxx5md4yhgf@sig21.net>

On Thursday, September 21, 2017 11:40:13 AM CEST Johannes Stezenbach wrote:
> Hi,
> 
> TL;DR: ACPI 6.1 spec interpretation question:
> 
>   7.2 Declaring a Power Resource Object
>   ...
>   Power resource objects can appear wherever is convenient in the namespace.
>   ...
>   Systemlevel is the deepest system sleep level OSPM must maintain to keep this
>   power resource on (0 equates to S0, 1 equates to S1, and so on).
> 
> Does it imply the OS should turn Power Resources off when changing
> the system level below the systemlevel of the PowerResource?

You can interpret that this way I guess.

However, so far we have not had to deal with "dangling" power resources.

> Otherwise, what purpose do PowerResource objects have that are not
> mentioned in any device _PR[0-3W]?  Or is it BIOS bug?

There also is _RDI that may refer to power resources, but I'm not aware of
anyone using it in practice ATM.

Other than that, I don't see why it would ever be necessary to declare
a power resource that is not pointed to by any of the above.

At least when the "power level" is changing from S0 to anything like S3,
the firmware gets control anyway at one point and then it is free to
manipulate whatever power resources it needs to turn off at that point.

So I would be inclined to think of that as a BIOS issue.

Thanks,
Rafael


  reply	other threads:[~2017-09-21 14:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170906204237.24x6fzlfmq7jmuce@sig21.net>
     [not found] ` <5bb7e3ca-38fc-1184-3bca-f666275c6180@linux.intel.com>
2017-09-08 13:49   ` S0ix failure due to "clk: x86: Do not gate clocks enabled by the firmware" Johannes Stezenbach
2017-09-21  9:40     ` Johannes Stezenbach
2017-09-21 14:21       ` Rafael J. Wysocki [this message]
2017-09-21 16:23         ` Johannes Stezenbach
2017-09-21 22:20           ` Rafael J. Wysocki
2017-09-21 22:24             ` Rafael J. Wysocki
2017-09-21 22:35           ` Rafael J. Wysocki
2017-09-22  8:04             ` Johannes Stezenbach
2017-09-22 12:27               ` Takashi Iwai
2017-09-22 21:04                 ` Johannes Stezenbach
2017-09-22 22:12                 ` Rafael J. Wysocki
2017-09-22 22:09               ` Rafael J. Wysocki
2017-09-25 19:17                 ` Johannes Stezenbach
2017-09-25 19:21                   ` [RFC PATCH 1/2] platform/x86: add Atom PMC quirk to disable SATA Johannes Stezenbach
2017-12-13  0:00                     ` Rafael J. Wysocki
2017-12-13  8:53                       ` Hans de Goede
2017-12-13 11:13                         ` Johannes Stezenbach
2017-12-13 15:25                         ` Michael Turquette
2017-12-13 16:04                           ` Hans de Goede
2017-12-13 16:22                             ` Johannes Stezenbach
2017-12-13 16:37                               ` Hans de Goede
2017-12-13 19:33                                 ` Andy Shevchenko
2017-12-14 10:53                                   ` Hans de Goede
2017-09-25 19:23                 ` [RFC PATCH 2/2] clk: x86: Disable unused clocks to fix S0ix Johannes Stezenbach
2017-12-13  0:01                   ` Rafael J. Wysocki
2017-12-13  8:56                     ` Hans de Goede
2017-12-13 10:20                       ` Carlo Caione
2017-12-13 11:22                       ` Johannes Stezenbach
2017-12-13 14:25                         ` Pierre-Louis Bossart
2017-12-13 14:29                       ` 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=4036229.gTT6xKEFIS@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=carlo@endlessm.com \
    --cc=dvhart@infradead.org \
    --cc=enric.balletbo@collabora.com \
    --cc=js@sig21.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox