public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Antheas Kapenekakis <lkml@antheas.dev>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: bob.beckett@collabora.com, bookeldor@gmail.com,
	hadess@hadess.net, jaap@haitsma.org, kernel@collabora.com,
	lennart@poettering.net, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, mccann@jhu.edu,
	richard@hughsie.com, sebastian.reichel@collabora.com,
	superm1@kernel.org, systemd-devel@lists.freedesktop.org,
	xaver.hugl@gmail.com
Subject: Re: [RFC v1 0/8] acpi/x86: s2idle: Introduce and implement runtime standby ABI for ACPI s0ix platforms
Date: Tue, 17 Mar 2026 14:56:53 +0300	[thread overview]
Message-ID: <030c38aa-353e-4387-a006-42e641b3ac6a@collabora.com> (raw)
In-Reply-To: <CAGwozwGEgLpjFTCF4kinR9+-_Wt=bYw19dcbVOswYe998z8Ykw@mail.gmail.com>

On 3/16/26 22:52, Antheas Kapenekakis wrote:
>> So in accordance with the above, /sys/power/standby is not a very
>> fortunate choice of the name of this interface and I'm totally
>> unconvinced that it belongs to sys/power because its role is not
>> really power management (and it is ACPI-only for the time being).
> Hm, most of the changes / implementation resides in the pm subsystem
> and it is related to the s2idle suspend flow.
> 
> I assume that when it stops being ACPI only provided we reach a design
> that allows for that, the related callbacks would also nest in pm ops.
> 
> Where could a more appropriate directory in sysfs be? I would still
> tend towards /sys/power

Question is whether anyone outside of ACPI will ever need the generic
interface. Making it generic based on guesswork could be a wasted effort
that Rafael and others will have to maintain. The mode file could go
under /sys/firmware/acpi if interface is made ACPI-specific.

Will be good if you could demonstrate a need in making interface
generic, if there are any devices on your mind that could make use of it
right away. Old interface can be deprecated if a better new appears.

Either way is okay to me, but Rafael is the PM expert and I'd do as he
wants it to be.

-- 
Best regards,
Dmitry

  reply	other threads:[~2026-03-17 11:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-26 10:26 [RFC v1 0/8] acpi/x86: s2idle: Introduce and implement runtime standby ABI for ACPI s0ix platforms Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 1/8] Documentation: PM: Add documentation for Runtime Standby States Antheas Kapenekakis
2026-03-13 20:07   ` Rafael J. Wysocki
2026-03-16 19:54     ` Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror their function Antheas Kapenekakis
2026-03-13 20:12   ` Rafael J. Wysocki
2026-03-16 20:01     ` Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 3/8] acpi/x86: s2idle: add runtime standby transition function Antheas Kapenekakis
2026-03-13 20:29   ` Rafael J. Wysocki
2026-03-16 20:06     ` Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 4/8] acpi/x86: s2idle: add support for querying runtime standby state support Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 5/8] acpi/x86: s2idle: move DSM notifications to do_notification callback Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 6/8] acpi/x86: s2idle: implement turn on display DSM as resume notification Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 7/8] PM: hibernate: Enter s2idle sleep state before hibernation Antheas Kapenekakis
2026-03-13 20:33   ` Rafael J. Wysocki
2026-03-16 20:09     ` Antheas Kapenekakis
2025-12-26 10:26 ` [RFC v1 8/8] PM: standby: Add sysfs attribute for runtime standby transitions Antheas Kapenekakis
2026-01-12 20:33 ` [RFC v1 0/8] acpi/x86: s2idle: Introduce and implement runtime standby ABI for ACPI s0ix platforms Antheas Kapenekakis
2026-01-13  9:48   ` Dmitry Osipenko
2026-01-13 10:11     ` Antheas Kapenekakis
2026-01-14 23:07       ` Dmitry Osipenko
2026-01-15  7:49         ` Antheas Kapenekakis
2026-03-16 19:02           ` Dmitry Osipenko
2026-03-16 19:33             ` Antheas Kapenekakis
2026-03-16 19:36               ` Antheas Kapenekakis
2026-03-17 11:04                 ` Dmitry Osipenko
2026-02-27 14:59 ` Antheas Kapenekakis
2026-02-27 18:42   ` Rafael J. Wysocki
2026-03-13 19:36 ` Rafael J. Wysocki
2026-03-16 19:52   ` Antheas Kapenekakis
2026-03-17 11:56     ` Dmitry Osipenko [this message]
2026-03-17 12:09       ` Rafael J. Wysocki
2026-03-17 15:13         ` Mario Limonciello
2026-03-19 12:35           ` Antheas Kapenekakis
2026-03-20 20:41             ` Mario Limonciello (AMD) (kernel.org)
2026-03-21 13:46               ` Antheas Kapenekakis
2026-03-21 13:52                 ` Antheas Kapenekakis
2026-03-21 18:43                   ` Mario Limonciello
2026-03-21 22:33                     ` Antheas Kapenekakis
2026-03-23  4:36                       ` Mario Limonciello
2026-03-23  9:26                         ` Antheas Kapenekakis

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=030c38aa-353e-4387-a006-42e641b3ac6a@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=bob.beckett@collabora.com \
    --cc=bookeldor@gmail.com \
    --cc=hadess@hadess.net \
    --cc=jaap@haitsma.org \
    --cc=kernel@collabora.com \
    --cc=lennart@poettering.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=mccann@jhu.edu \
    --cc=rafael@kernel.org \
    --cc=richard@hughsie.com \
    --cc=sebastian.reichel@collabora.com \
    --cc=superm1@kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=xaver.hugl@gmail.com \
    /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