From: Manuel Traut <manuel.traut@mt.com>
To: Markus Burri <markus.burri@mt.com>
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 7/7] Input: matrix_keypad - detect change during scan
Date: Wed, 19 Feb 2025 17:56:10 +0100 [thread overview]
Message-ID: <Z7YNKl4ljWFQEa-u@mt.com> (raw)
In-Reply-To: <20250110054906.354296-8-markus.burri@mt.com>
On Fri, Jan 10, 2025 at 06:49:06AM +0100, Markus Burri wrote:
> For a setup where the matrix keypad is connected over a slow interface
> (e.g. a gpio-expansion over i2c), the scan can take a longer time to read.
>
> Interrupts need to be disabled during scan. And therefore changes in this
> period are not detected.
> To improve this situation, scan the matrix again if the row state changed
> during interrupts disabled.
> The rescan is repeated until no change is detected anymore.
This is a quirk for a bad hardware design. For 'good' hardware it adds
an additional read_row_state for no need. For even slower connected
GPIOs this will also not help much. However it is obvious that it will
be an improvement for some designs.
Dmitry, would it make sense to make this configurable?
> Signed-off-by: Markus Burri <markus.burri@mt.com>
>
> ---
> drivers/input/keyboard/matrix_keypad.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/input/keyboard/matrix_keypad.c b/drivers/input/keyboard/matrix_keypad.c
> index fdb3499..e50a6fe 100644
> --- a/drivers/input/keyboard/matrix_keypad.c
> +++ b/drivers/input/keyboard/matrix_keypad.c
> @@ -125,6 +125,10 @@ static void matrix_keypad_scan(struct work_struct *work)
> const unsigned short *keycodes = input_dev->keycode;
> uint32_t new_state[MATRIX_MAX_COLS];
> int row, col, code;
> + u32 init_row_state, new_row_state;
> +
> + /* read initial row state to detect changes between scan */
> + init_row_state = read_row_state(keypad);
>
> /* de-activate all columns for scanning */
> activate_all_cols(keypad, false);
> @@ -173,6 +177,18 @@ static void matrix_keypad_scan(struct work_struct *work)
> keypad->scan_pending = false;
> enable_row_irqs(keypad);
> }
> +
> + /* read new row state and detect if value has changed */
> + new_row_state = read_row_state(keypad);
> + if (init_row_state != new_row_state) {
> + guard(spinlock_irq)(&keypad->lock);
> + if (unlikely(keypad->scan_pending || keypad->stopped))
> + return;
> + disable_row_irqs(keypad);
> + keypad->scan_pending = true;
> + schedule_delayed_work(&keypad->work,
> + msecs_to_jiffies(keypad->debounce_ms));
> + }
> }
>
> static irqreturn_t matrix_keypad_interrupt(int irq, void *id)
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-02-19 16:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 5:48 [PATCH v5 0/7] Input: matrix-keypad: Various performance improvements Markus Burri
2025-01-10 5:49 ` [PATCH v5 1/7] Input: matrix_keypad - use fsleep for variable delay duration Markus Burri
2025-02-19 16:34 ` Manuel Traut
2025-02-25 6:40 ` Dmitry Torokhov
2025-02-25 6:55 ` Dmitry Torokhov
2025-02-25 8:46 ` Markus Burri
2025-02-26 0:13 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 2/7] Input: matrix_keypad - add function for reading row state Markus Burri
2025-02-19 16:40 ` Manuel Traut
2025-01-10 5:49 ` [PATCH v5 3/7] dt-bindings: input: matrix_keypad - convert to YAML Markus Burri
2025-01-14 19:50 ` Rob Herring (Arm)
2025-02-19 16:41 ` Manuel Traut
2025-02-26 0:13 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 4/7] dt-bindings: input: matrix_keypad - add missing property Markus Burri
2025-01-14 19:51 ` Rob Herring (Arm)
2025-02-19 16:42 ` Manuel Traut
2025-02-25 6:46 ` Dmitry Torokhov
2025-02-25 10:16 ` Markus Burri
2025-02-25 17:43 ` Dmitry Torokhov
2025-02-26 12:14 ` Markus Burri
2025-01-10 5:49 ` [PATCH v5 5/7] dt-bindings: input: matrix_keypad - add settle time after enable all columns Markus Burri
2025-02-19 16:42 ` Manuel Traut
2025-02-26 0:14 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 6/7] Input: " Markus Burri
2025-02-19 16:47 ` Manuel Traut
2025-02-26 0:14 ` Dmitry Torokhov
2025-01-10 5:49 ` [PATCH v5 7/7] Input: matrix_keypad - detect change during scan Markus Burri
2025-02-19 16:56 ` Manuel Traut [this message]
2025-02-25 6:58 ` Dmitry Torokhov
2025-02-25 8:51 ` Markus Burri
2025-02-25 17:46 ` Dmitry Torokhov
2025-02-26 12:06 ` Markus Burri
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=Z7YNKl4ljWFQEa-u@mt.com \
--to=manuel.traut@mt.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=markus.burri@mt.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).