All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Daniel Golle" <daniel@makrotopia.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org, dmitry.torokhov@gmail.com, robh@kernel.org
Subject: Re: [PATCH v2 4/5] Input: hynitron-cst816x: time out gesture key release
Date: Fri, 02 Oct 2026 13:14:34 +0000	[thread overview]
Message-ID: <20261002131435.66E641F00893@smtp.kernel.org> (raw)
In-Reply-To: <909d4a3a2182ede94e76f60954279774d5f91b15.1790944534.git.daniel@makrotopia.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] timers: use timer_shutdown_sync() for devres teardown path
--

commit f56704648dd845b470f4641ef231af0c72507d76
Author: Daniel Golle <daniel@makrotopia.org>

Input: hynitron-cst816x: time out gesture key release

This commit introduces a timer to release the gesture keys 40 ms after the
last report containing a gesture code. This prevents the gesture key from
remaining pressed indefinitely if the panel stops reporting after the
initial gesture event.

> diff --git a/drivers/input/touchscreen/hynitron-cst816x.c b/drivers/input/touchscreen/hynitron-cst816x.c
> --- a/drivers/input/touchscreen/hynitron-cst816x.c
> +++ b/drivers/input/touchscreen/hynitron-cst816x.c
[ ... ]
> +static void cst816x_timer_stop(void *data)
> +{
> +	struct cst816x_priv *priv = data;
> +
> +	timer_delete_sync(&priv->release_timer);

[Severity: Low]
Does this devres teardown path need to use timer_shutdown_sync() instead of
timer_delete_sync()?

Using timer_delete_sync() in a final teardown path is deprecated. The timer
subsystem introduced timer_shutdown_sync() to permanently disable timers
during teardown.

Because devres executes actions in last-in, first-out order, the interrupt
is already freed and synchronized before the timer is stopped. A re-arm race
is structurally impossible here, making this an API compliance regression
rather than a use-after-free bug.

> +}
> +
>  static int cst816x_probe(struct i2c_client *client)

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790944534.git.daniel@makrotopia.org?part=4

  reply	other threads:[~2026-10-02 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 12:47 [PATCH v2 0/5] Input: hynitron-cst816x: axes, gesture keys and panel power Daniel Golle
2026-10-02 12:47 ` [PATCH v2 1/5] dt-bindings: input: touchscreen: hynitron,cst816x: axes and panel Daniel Golle
2026-10-04  7:24   ` Krzysztof Kozlowski
2026-10-04  7:29     ` Daniel Golle
2026-10-04  7:33       ` Krzysztof Kozlowski
2026-10-02 12:47 ` [PATCH v2 2/5] Input: hynitron-cst816x: respect touchscreen DT properties Daniel Golle
2026-10-04 20:30   ` Oleh Kuzhylnyi
2026-10-02 12:47 ` [PATCH v2 3/5] Input: hynitron-cst816x: release gesture keys Daniel Golle
2026-10-04 21:36   ` Oleh Kuzhylnyi
     [not found]   ` <XXX-PASTE-MESSAGE-ID-OF-OLEHS-MAIL>
2026-10-05 17:07     ` Daniel Golle
2026-10-02 12:48 ` [PATCH v2 4/5] Input: hynitron-cst816x: time out gesture key release Daniel Golle
2026-10-02 13:14   ` sashiko-bot [this message]
2026-10-02 12:48 ` [PATCH v2 5/5] Input: hynitron-cst816x: power sequence with the panel Daniel Golle
2026-10-02 13:26   ` sashiko-bot

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=20261002131435.66E641F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.