[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM7w-FXAGki+k9aP0wV1Qs8dKqpPXgY9ZJR_a83ETrUF6ZRZOw@mail.gmail.com>
Date: Tue, 1 Nov 2022 13:37:26 -0400
From: Sven van Ashbrook <svenva@...omium.org>
To: Mario Limonciello <mario.limonciello@....com>
Cc: Rafael J Wysocki <rafael@...nel.org>, Pavel Machek <pavel@....cz>,
Len Brown <len.brown@...el.com>,
Rajneesh Bhardwaj <irenic.rajneesh@...il.com>,
S-k Shyam-sundar <Shyam-sundar.S-k@....com>,
rrangel@...omium.org, platform-driver-x86@...r.kernel.org,
Rajat Jain <rajatja@...gle.com>,
David E Box <david.e.box@...el.com>,
Hans de Goede <hdegoede@...hat.com>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [RFC 1/3] PM: Add a sysfs file to represent whether hardware
reached the deepest state
On Mon, Oct 31, 2022 at 4:43 PM Mario Limonciello
<mario.limonciello@....com> wrote:
>
> +void pm_set_hw_deepest_state(u64 duration)
> +{
> + suspend_stats.last_hw_deepest_state = duration;
I'm wondering if we could add a userspace notification here. Then
userspace wouldn't have to synchronize with the suspend/resume state
of the system when reading this entry.
What about sysfs_notify() ? Or via udev?
> +}
> +EXPORT_SYMBOL_GPL(pm_set_hw_deepest_state);
Powered by blists - more mailing lists