From: Alexander Kochetkov <al.kochet@gmail.com>
To: linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Siarhei Volkau <lis8215@gmail.com>,
Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH] Revert "Input: matrix_keypad - force switch rows to input mode"
Date: Mon, 19 Oct 2026 11:00:43 +0300 [thread overview]
Message-ID: <36834AAE-F2DD-4974-A5A9-60B30F29DCF4@gmail.com> (raw)
In-Reply-To: <20261002100935.449473-1-al.kochet@gmail.com>
Hi Dmitry,
Gentle ping. This is a regression fix for matrix_keypad with Acked-by
from Siarhei (author of the reverted commit) and Paul (Ingenic
maintainer); it still applies to your next branch. Is there anything
else you need from me?
Thanks,
Alexander
> 2 окт. 2026 г., в 13:09, Alexander Kochetkov <al.kochet@gmail.com> написал(а):
>
> This reverts commit 01c84b03d80aab9f04c4e3e1f9085f4202ff7c29.
>
> The commit makes every scan call gpiod_direction_input() on the row
> GPIOs. On pin controllers where GPIO input and interrupt are separate
> pinmux functions this switches the row pins out of interrupt mode, and
> enable_row_irqs() does not switch them back: it only unmasks the
> interrupts. Row interrupts then never arrive and the keypad stops
> working. Seen with a matrix keypad on an Allwinner A64 board (PINE
> A64-LTS); it works again with the commit reverted.
>
> The workaround is not needed on Ingenic either: the author of the
> reverted commit re-tested all available JZ47xx SoCs and they all report
> the live pin state in interrupt mode, see the thread in Link.
>
> Fixes: 01c84b03d80a ("Input: matrix_keypad - force switch rows to input mode")
> Link: https://lore.kernel.org/all/4130C026-2A83-408B-836A-ECA044491C47@gmail.com/
> Cc: stable@vger.kernel.org
> Signed-off-by: Alexander Kochetkov <al.kochet@gmail.com>
> ---
> The same three-line removal has been in use on Allwinner A64 hardware on
> top of v6.12.33; this version is rebased onto v7.3-rc5 and build-tested
> (arm64, CONFIG_KEYBOARD_MATRIX=m).
>
> Siarhei, Paul: you both agreed to the revert in the thread above, please
> reply with your Acked-by/Tested-by if you would like it recorded.
>
> drivers/input/keyboard/matrix_keypad.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/input/keyboard/matrix_keypad.c b/drivers/input/keyboard/matrix_keypad.c
> index 8863b741d1a3..cda2888b2e56 100644
> --- a/drivers/input/keyboard/matrix_keypad.c
> +++ b/drivers/input/keyboard/matrix_keypad.c
> @@ -134,9 +134,6 @@ static void matrix_keypad_scan(struct work_struct *work)
>
> memset(new_state, 0, sizeof(new_state));
>
> - for (row = 0; row < keypad->num_row_gpios; row++)
> - gpiod_direction_input(keypad->row_gpios[row]);
> -
> /* assert each column and read the row status out */
> for (col = 0; col < keypad->num_col_gpios; col++) {
>
>
> base-commit: 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e
> --
> 2.43.0
>
prev parent reply other threads:[~2026-10-19 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 10:09 Alexander Kochetkov
2026-10-02 12:35 ` Siarhei Volkau
2026-10-02 14:02 ` Paul Cercueil
2026-10-19 8:00 ` Alexander Kochetkov [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=36834AAE-F2DD-4974-A5A9-60B30F29DCF4@gmail.com \
--to=al.kochet@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lis8215@gmail.com \
--cc=paul@crapouillou.net \
/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
all inboxes | Powered by JetHome®