Linux Input/HID development
 help / color / mirror / Atom feed
From: ahmad baghereslami <ahmad.b1995@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v3] Input: synaptics - support the touchpad LED on RMI function $30
Date: Sun, 15 Nov 2026 17:50:31 +0330	[thread overview]
Message-ID: <20261115142031.349182-1-ahmad.b1995@gmail.com> (raw)
In-Reply-To: <sashiko-outbox-214329@kernel.org>

On Sat, 14 Nov 2026 09:24:32 +0000, sashiko-bot@kernel.org wrote:
> led_trigger_set(led_cdev, NULL) calls led_set_brightness(led_cdev,
> LED_OFF), which invokes synaptics_rmi_led_set() and sets priv->rmi_led_on
> to false.  cancel_delayed_work_sync() then cancels the pending work before
> it can write to the touchpad, and the check on priv->rmi_led_on is false,
> so __synaptics_rmi_led_set(psmouse, false) is skipped and the hardware LED
> stays on.

Right. The same happens without a trigger when the brightness is set
to 0 just before an unbind: the work cannot take psmouse_mutex, so it
is cancelled before it reaches the touchpad.

v4 will turn the LED off in synaptics_rmi_led_unregister() whatever
rmi_led_on says, as synaptics_rmi_led_init() does. I will wait a few
days for other comments on v3 before sending it.

Thanks,
Ahmad

      reply	other threads:[~2026-11-15 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  7:08 [PATCH] Input: synaptics - support the touchpad LED on RMI function $30 ahmad baghereslami
2026-10-30  7:24 ` sashiko-bot
2026-10-31  1:23 ` kernel test robot
2026-10-31  2:29 ` kernel test robot
2026-11-06  9:56 ` [PATCH v2] " ahmad baghereslami
2026-11-06 10:14   ` sashiko-bot
2026-11-14  9:08   ` [PATCH v3] " ahmad baghereslami
2026-11-14  9:24     ` sashiko-bot
2026-11-15 14:20       ` ahmad baghereslami [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=20261115142031.349182-1-ahmad.b1995@gmail.com \
    --to=ahmad.b1995@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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