From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Derek J . Clark" <derekjohn.clark@gmail.com>
Cc: "Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Nitin Joshi" <nitjoshi@gmail.com>,
"Andrzej Pietrasiewicz" <andrzej.p@collabora.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: thinkpad_acpi: Use input_device_enabled()
Date: Wed, 05 Aug 2026 10:51:53 -0400 [thread overview]
Message-ID: <4ad479fa-8465-4d00-aa73-ced177254eee@app.fastmail.com> (raw)
In-Reply-To: <anK1j7hbMyFHGBUS@google.com>
On Wed, Aug 5, 2026, at 12:03 AM, Dmitry Torokhov wrote:
> From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
>
> Use the new helper. Inspecting input device's 'users' member needs to be
> done under device's mutex, so add appropriate invocations.
>
> Signed-off-by: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
> Acked-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Link: https://lore.kernel.org/r/20200608112211.12125-7-andrzej.p@collabora.com
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>
> Not sure how this got stuck in my patch queue but it is still valid...
>
> drivers/platform/x86/lenovo/thinkpad_acpi.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/lenovo/thinkpad_acpi.c
> b/drivers/platform/x86/lenovo/thinkpad_acpi.c
> index 445e1403308e..f8e116e8a65d 100644
> --- a/drivers/platform/x86/lenovo/thinkpad_acpi.c
> +++ b/drivers/platform/x86/lenovo/thinkpad_acpi.c
> @@ -2547,9 +2547,10 @@ static void hotkey_poll_setup(const bool
> may_warn)
>
> lockdep_assert_held(&hotkey_mutex);
>
> + mutex_lock(&tpacpi_inputdev->mutex);
> if (hotkey_poll_freq > 0 &&
> (poll_driver_mask ||
> - (poll_user_mask && tpacpi_inputdev->users > 0))) {
> + (poll_user_mask && input_device_enabled(tpacpi_inputdev)))) {
> if (!tpacpi_hotkey_task) {
> tpacpi_hotkey_task = kthread_run(hotkey_kthread,
> NULL, TPACPI_NVRAM_KTHREAD_NAME);
> @@ -2566,6 +2567,7 @@ static void hotkey_poll_setup(const bool may_warn)
> poll_user_mask, poll_driver_mask);
> }
> }
> + mutex_unlock(&tpacpi_inputdev->mutex);
> }
>
> static void hotkey_poll_setup_safe(const bool may_warn)
> --
Looks good to me.
Only note is that can you use guard(mutex)(&tpacpi_inputdev->mutex) instead of the lock/unlock? I think that's preferred these days.
Reviewed-by: Mark Pearson <mpearson-lenovo@squebb.ca>
next prev parent reply other threads:[~2026-08-05 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 4:03 [PATCH] platform/x86: thinkpad_acpi: Use input_device_enabled() Dmitry Torokhov
2026-08-05 14:51 ` Mark Pearson [this message]
2026-08-05 15:52 ` Dmitry Torokhov
2026-08-05 16:15 ` Mark Pearson
2026-08-06 6:20 ` Dmitry Torokhov
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=4ad479fa-8465-4d00-aa73-ced177254eee@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=andrzej.p@collabora.com \
--cc=derekjohn.clark@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hansg@kernel.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nitjoshi@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
/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