From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: "Armin Wolf" <W_Armin@gmx.de>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-hwmon@vger.kernel.org, "Hans de Goede" <hansg@kernel.org>,
"Derek John Clark" <derekjohn.clark@gmail.com>,
"Joaquín Ignacio Aramendía" <samsagax@gmail.com>,
"Jean Delvare" <jdelvare@suse.com>,
"Guenter Roeck" <linux@roeck-us.net>
Subject: Re: [PATCH v5 6/6] platform/x86: ayaneo-ec: Add suspend hook
Date: Mon, 17 Nov 2025 11:56:52 +0200 (EET) [thread overview]
Message-ID: <054431ff-9bc9-c827-a81b-ee6741fec230@linux.intel.com> (raw)
In-Reply-To: <CAGwozwExxbcrTQP5G6cc3sjayiW+crCXTfG4VHi85QrMqFtpBQ@mail.gmail.com>
On Sun, 16 Nov 2025, Antheas Kapenekakis wrote:
> On Sun, 16 Nov 2025 at 17:05, Armin Wolf <W_Armin@gmx.de> wrote:
> >
> > Am 13.11.25 um 22:22 schrieb Antheas Kapenekakis:
> >
> > > The Ayaneo EC resets after hibernation, losing the charge control state.
> > > Add a small PM hook to restore this state on hibernation resume.
> > >
> > > The fan speed is also lost during hibernation, but since hibernation
> > > failures are common with this class of devices, setting a low fan speed
> > > when the userspace program controlling the fan will potentially not
> > > take over could cause the device to overheat, so it is not restored.
> > >
> > > Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
> > > ---
> > > drivers/platform/x86/ayaneo-ec.c | 84 +++++++++++++++++++++++++++++++-
> > > 1 file changed, 83 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/platform/x86/ayaneo-ec.c b/drivers/platform/x86/ayaneo-ec.c
> > > index 814f7f028710..3f40429acbd4 100644
> > > --- a/drivers/platform/x86/ayaneo-ec.c
> > > +++ b/drivers/platform/x86/ayaneo-ec.c
> > > @@ -52,6 +52,11 @@ struct ayaneo_ec_platform_data {
> > > struct platform_device *pdev;
> > > struct ayaneo_ec_quirk *quirks;
> > > struct acpi_battery_hook battery_hook;
> > > +
> > > + // Protects access to restore_pwm
> > > + struct mutex hwmon_lock;
> > > + bool restore_charge_limit;
> > > + bool restore_pwm;
> > > };
> > >
> > > static const struct ayaneo_ec_quirk quirk_fan = {
> > > @@ -208,10 +213,16 @@ static int ayaneo_ec_read(struct device *dev, enum hwmon_sensor_types type,
> > > static int ayaneo_ec_write(struct device *dev, enum hwmon_sensor_types type,
> > > u32 attr, int channel, long val)
> > > {
> > > + struct ayaneo_ec_platform_data *data = dev_get_drvdata(dev);
> > > + int ret;
> > > +
> > > + guard(mutex)(&data->hwmon_lock);
> > > +
> > > switch (type) {
> > > case hwmon_pwm:
> > > switch (attr) {
> > > case hwmon_pwm_enable:
> > > + data->restore_pwm = false;
> > > switch (val) {
> > > case 1:
> > > return ec_write(AYANEO_PWM_ENABLE_REG,
> > > @@ -225,6 +236,17 @@ static int ayaneo_ec_write(struct device *dev, enum hwmon_sensor_types type,
> > > case hwmon_pwm_input:
> > > if (val < 0 || val > 255)
> > > return -EINVAL;
> > > + if (data->restore_pwm) {
> > > + /*
> > > + * Defer restoring PWM control to after
> > > + * userspace resumes successfully
> > > + */
> > > + ret = ec_write(AYANEO_PWM_ENABLE_REG,
> > > + AYANEO_PWM_MODE_MANUAL);
> > > + if (ret)
> > > + return ret;
> > > + data->restore_pwm = false;
> > > + }
> > > return ec_write(AYANEO_PWM_REG, (val * 100) / 255);
> > > default:
> > > break;
> > > @@ -454,11 +476,14 @@ static int ayaneo_ec_probe(struct platform_device *pdev)
> > >
> > > data->pdev = pdev;
> > > data->quirks = dmi_entry->driver_data;
> > > + ret = devm_mutex_init(&pdev->dev, &data->hwmon_lock);
> > > + if (ret)
> > > + return ret;
> > > platform_set_drvdata(pdev, data);
> > >
> > > if (data->quirks->has_fan_control) {
> > > hwdev = devm_hwmon_device_register_with_info(&pdev->dev,
> > > - "ayaneo_ec", NULL, &ayaneo_ec_chip_info, NULL);
> > > + "ayaneo_ec", data, &ayaneo_ec_chip_info, NULL);
> > > if (IS_ERR(hwdev))
> > > return PTR_ERR(hwdev);
> > > }
> > > @@ -475,10 +500,67 @@ static int ayaneo_ec_probe(struct platform_device *pdev)
> > > return 0;
> > > }
> > >
> > > +static int ayaneo_freeze(struct device *dev)
> > > +{
> > > + struct platform_device *pdev = to_platform_device(dev);
> > > + struct ayaneo_ec_platform_data *data = platform_get_drvdata(pdev);
> > > + int ret;
> > > + u8 tmp;
> > > +
> > > + if (data->quirks->has_charge_control) {
> > > + ret = ec_read(AYANEO_CHARGE_REG, &tmp);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + data->restore_charge_limit = tmp == AYANEO_CHARGE_VAL_INHIBIT;
> > > + }
> > > +
> > > + if (data->quirks->has_fan_control) {
> > > + ret = ec_read(AYANEO_PWM_ENABLE_REG, &tmp);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + data->restore_pwm = tmp == AYANEO_PWM_MODE_MANUAL;
> > > +
> > > + /*
> > > + * Release the fan when entering hibernation to avoid
> > > + * overheating if hibernation fails and hangs.
> > > + */
> > > + if (data->restore_pwm) {
> > > + ret = ec_write(AYANEO_PWM_ENABLE_REG, AYANEO_PWM_MODE_AUTO);
> > > + if (ret)
> > > + return ret;
> > > + }
> > > + }
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static int ayaneo_restore(struct device *dev)
> > > +{
> > > + struct platform_device *pdev = to_platform_device(dev);
> > > + struct ayaneo_ec_platform_data *data = platform_get_drvdata(pdev);
> > > + int ret;
> > > +
> > > + if (data->quirks->has_charge_control && data->restore_charge_limit) {
> > > + ret = ec_write(AYANEO_CHARGE_REG, AYANEO_CHARGE_VAL_INHIBIT);
> > > + if (ret)
> > > + return ret;
> > > + }
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static const struct dev_pm_ops ayaneo_pm_ops = {
> > > + .freeze = ayaneo_freeze,
> > > + .restore = ayaneo_restore,
> > > +};
> > > +
> > > static struct platform_driver ayaneo_platform_driver = {
> > > .driver = {
> > > .name = "ayaneo-ec",
> > > .dev_groups = ayaneo_ec_groups,
> > > + .pm = &ayaneo_pm_ops,
> >
> > Maybe you should use pm_sleep_ptr() here. With that being fixed:
>
> True, i conflated that with using a sleep define so I skipped it.
> Seems it is a ternary that checks CONFIG_PM_SLEEP
>
> @Ilpo lmk if I should resend this before the merge window or it's
> small enough to edit inplace
In general, I prefer new version over having to hand edit things myself.
I might do in-place editing of in patch format on my own volition when
replying is more effort than editing itself; but if you ask, I'll have to
reply anyway so it doesn't save even the time needed for writing the
reply.
Also, this doesn't add any headers despite adding use for struct
dev_pm_ops so you should likely add an include too.
--
i.
prev parent reply other threads:[~2025-11-17 9:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 21:22 [PATCH v5 0/6] platform/x86: ayaneo-ec: Add Ayaneo Embedded Controller platform driver Antheas Kapenekakis
2025-11-13 21:22 ` [PATCH v5 1/6] " Antheas Kapenekakis
2025-11-16 16:02 ` Armin Wolf
2025-11-13 21:22 ` [PATCH v5 2/6] platform/x86: ayaneo-ec: Add hwmon support Antheas Kapenekakis
2025-11-17 10:16 ` Ilpo Järvinen
2025-11-13 21:22 ` [PATCH v5 3/6] platform/x86: ayaneo-ec: Add charge control support Antheas Kapenekakis
2025-11-13 21:22 ` [PATCH v5 4/6] platform/x86: ayaneo-ec: Add controller power and modules attributes Antheas Kapenekakis
2025-11-17 10:29 ` Ilpo Järvinen
2025-11-17 13:33 ` Antheas Kapenekakis
2025-11-18 12:31 ` Ilpo Järvinen
2025-11-18 12:58 ` Antheas Kapenekakis
2025-11-18 14:06 ` Armin Wolf
2025-11-19 15:36 ` Hans de Goede
2025-11-13 21:22 ` [PATCH v5 5/6] platform/x86: ayaneo-ec: Move Ayaneo devices from oxpec to ayaneo-ec Antheas Kapenekakis
2025-11-13 21:22 ` [PATCH v5 6/6] platform/x86: ayaneo-ec: Add suspend hook Antheas Kapenekakis
2025-11-16 16:05 ` Armin Wolf
2025-11-16 16:19 ` Antheas Kapenekakis
2025-11-17 9:56 ` Ilpo Järvinen [this message]
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=054431ff-9bc9-c827-a81b-ee6741fec230@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkml@antheas.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=samsagax@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;
as well as URLs for NNTP newsgroup(s).