From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: Hans de Goede <hansg@kernel.org>,
wse@tuxedocomputers.com, platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 6/7] platform/x86: uniwill-laptop: Mark EC_ADDR_OEM_4 as volatile
Date: Thu, 30 Apr 2026 16:13:44 +0300 (EEST) [thread overview]
Message-ID: <aff220ab-3c15-6b20-322b-6263e1be5c64@linux.intel.com> (raw)
In-Reply-To: <20260417050912.5582-7-W_Armin@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 5591 bytes --]
On Fri, 17 Apr 2026, Armin Wolf wrote:
> It turned out that EC_ADDR_OEM_4 also contains bits with a volatile
> nature. Mark the whole register as volatile to prepare for the usage
> of said bits. This also means that we now have to save/restore the
> touchpad toggle state ourself.
>
> Reviewed-by: Werner Sembach <wse@tuxedocomputers.com>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> ---
> drivers/platform/x86/uniwill/uniwill-acpi.c | 70 ++++++++++++++++++---
> 1 file changed, 60 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
> index 8c00d762ab08..d4abcaf87e39 100644
> --- a/drivers/platform/x86/uniwill/uniwill-acpi.c
> +++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
> @@ -343,6 +343,7 @@ struct uniwill_data {
> struct mutex battery_lock; /* Protects the list of currently registered batteries */
> bool last_fn_lock_state;
> bool last_super_key_enable_state;
> + bool last_touchpad_toggle_enable_state;
> struct mutex super_key_lock; /* Protects the toggling of the super key lock state */
> struct list_head batteries;
> struct mutex led_lock; /* Protects writes to the lightbar registers */
> @@ -598,6 +599,7 @@ static bool uniwill_volatile_reg(struct device *dev, unsigned int reg)
> case EC_ADDR_PWM_2:
> case EC_ADDR_TRIGGER:
> case EC_ADDR_SWITCH_STATUS:
> + case EC_ADDR_OEM_4:
> case EC_ADDR_CHARGE_CTRL:
> case EC_ADDR_USB_C_POWER_PRIORITY:
> return true;
> @@ -747,11 +749,22 @@ static ssize_t super_key_enable_show(struct device *dev, struct device_attribute
>
> static DEVICE_ATTR_RW(super_key_enable);
>
> +static int uniwill_write_touchpad_toggle_enable(struct uniwill_data *data, bool status)
> +{
> + unsigned int value;
> +
> + if (status)
> + value = 0;
> + else
> + value = TOUCHPAD_TOGGLE_OFF;
> +
> + return regmap_update_bits(data->regmap, EC_ADDR_OEM_4, TOUCHPAD_TOGGLE_OFF, value);
> +}
> +
> static ssize_t touchpad_toggle_enable_store(struct device *dev, struct device_attribute *attr,
> const char *buf, size_t count)
> {
> struct uniwill_data *data = dev_get_drvdata(dev);
> - unsigned int value;
> bool enable;
> int ret;
>
> @@ -759,30 +772,39 @@ static ssize_t touchpad_toggle_enable_store(struct device *dev, struct device_at
> if (ret < 0)
> return ret;
>
> - if (enable)
> - value = 0;
> - else
> - value = TOUCHPAD_TOGGLE_OFF;
> -
> - ret = regmap_update_bits(data->regmap, EC_ADDR_OEM_4, TOUCHPAD_TOGGLE_OFF, value);
> + ret = uniwill_write_touchpad_toggle_enable(data, enable);
> if (ret < 0)
> return ret;
>
> return count;
> }
>
> +static int uniwill_read_touchpad_toggle_enable(struct uniwill_data *data, bool *status)
> +{
> + unsigned int value;
> + int ret;
> +
> + ret = regmap_read(data->regmap, EC_ADDR_OEM_4, &value);
> + if (ret < 0)
> + return ret;
> +
> + *status = !(value & TOUCHPAD_TOGGLE_OFF);
> +
> + return 0;
> +}
> +
> static ssize_t touchpad_toggle_enable_show(struct device *dev, struct device_attribute *attr,
> char *buf)
> {
> struct uniwill_data *data = dev_get_drvdata(dev);
> - unsigned int value;
> + bool status;
> int ret;
>
> - ret = regmap_read(data->regmap, EC_ADDR_OEM_4, &value);
> + ret = uniwill_read_touchpad_toggle_enable(data, &status);
> if (ret < 0)
> return ret;
>
> - return sysfs_emit(buf, "%d\n", !(value & TOUCHPAD_TOGGLE_OFF));
> + return sysfs_emit(buf, "%d\n", status);
> }
>
> static DEVICE_ATTR_RW(touchpad_toggle_enable);
> @@ -1774,6 +1796,18 @@ static int uniwill_suspend_super_key(struct uniwill_data *data)
> return uniwill_read_super_key_enable(data, &data->last_super_key_enable_state);
> }
>
> +static int uniwill_suspend_touchpad_toggle(struct uniwill_data *data)
> +{
> + if (!uniwill_device_supports(data, UNIWILL_FEATURE_TOUCHPAD_TOGGLE))
> + return 0;
> +
> + /*
> + * EC_ADDR_OEM_4 is marked as volatile, so we have to restore it
> + * ourselves.
> + */
> + return uniwill_read_touchpad_toggle_enable(data, &data->last_touchpad_toggle_enable_state);
> +}
> +
> static int uniwill_suspend_battery(struct uniwill_data *data)
> {
> if (!uniwill_device_supports(data, UNIWILL_FEATURE_BATTERY))
> @@ -1809,6 +1843,10 @@ static int uniwill_suspend(struct device *dev)
> if (ret < 0)
> return ret;
>
> + ret = uniwill_suspend_touchpad_toggle(data);
> + if (ret < 0)
> + return ret;
> +
> ret = uniwill_suspend_battery(data);
> if (ret < 0)
> return ret;
> @@ -1839,6 +1877,14 @@ static int uniwill_resume_super_key(struct uniwill_data *data)
> return uniwill_write_super_key_enable(data, data->last_super_key_enable_state);
> }
>
> +static int uniwill_resume_touchpad_toggle(struct uniwill_data *data)
> +{
> + if (!uniwill_device_supports(data, UNIWILL_FEATURE_TOUCHPAD_TOGGLE))
> + return 0;
> +
> + return uniwill_write_touchpad_toggle_enable(data, data->last_touchpad_toggle_enable_state);
> +}
> +
> static int uniwill_resume_battery(struct uniwill_data *data)
> {
> if (!uniwill_device_supports(data, UNIWILL_FEATURE_BATTERY))
> @@ -1884,6 +1930,10 @@ static int uniwill_resume(struct device *dev)
> if (ret < 0)
> return ret;
>
> + ret = uniwill_resume_touchpad_toggle(data);
> + if (ret < 0)
> + return ret;
> +
> ret = uniwill_resume_battery(data);
> if (ret < 0)
> return ret;
>
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
next prev parent reply other threads:[~2026-04-30 13:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 5:09 [PATCH v2 0/7] platform/x86: uniwill-laptop: Charging-related improvements Armin Wolf
2026-04-17 5:09 ` [PATCH v2 1/7] platform/x86: uniwill-laptop: Properly initialize charging threshold Armin Wolf
2026-04-30 12:53 ` Ilpo Järvinen
2026-05-03 21:34 ` Armin Wolf
2026-04-17 5:09 ` [PATCH v2 2/7] platform/x86: uniwill-laptop: Accept charging threshold of 0 Armin Wolf
2026-04-30 12:55 ` Ilpo Järvinen
2026-04-17 5:09 ` [PATCH v2 3/7] platform/x86: uniwill-laptop: Fix behavior of "force" module param Armin Wolf
2026-04-17 12:01 ` Werner Sembach
2026-04-30 12:57 ` Ilpo Järvinen
2026-04-17 5:09 ` [PATCH v2 4/7] platform/x86: uniwill-laptop: Do not enable the charging limit even when forced Armin Wolf
2026-04-17 12:01 ` Werner Sembach
2026-04-30 12:57 ` Ilpo Järvinen
2026-04-17 5:09 ` [PATCH v2 5/7] platform/x86: uniwill-laptop: Rework FN lock/super key suspend handling Armin Wolf
2026-04-30 13:11 ` Ilpo Järvinen
2026-04-17 5:09 ` [PATCH v2 6/7] platform/x86: uniwill-laptop: Mark EC_ADDR_OEM_4 as volatile Armin Wolf
2026-04-30 13:13 ` Ilpo Järvinen [this message]
2026-04-17 5:09 ` [PATCH v2 7/7] platform/x86: uniwill-laptop: Add support for battery charge modes Armin Wolf
2026-04-20 20:03 ` Werner Sembach
2026-04-30 13:22 ` Ilpo Järvinen
2026-04-30 13:41 ` Armin Wolf
2026-05-04 8:44 ` Werner Sembach
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=aff220ab-3c15-6b20-322b-6263e1be5c64@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.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