From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Haojian Zhuang <haojian.zhuang@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
soc@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [PATCH 0/5] Remove support for platform data from matrix keypad driver
Date: Sun, 4 Aug 2024 18:47:03 -0700 [thread overview]
Message-ID: <20240805014710.1961677-1-dmitry.torokhov@gmail.com> (raw)
Hi,
This series attempts to remove support for platform data from
matrix_keypad driver, and have it use generic device properties only
for the keypad configuration. Spitz is the only board [left] that
uses platform data.
As part of the migration I am also dropping support for "clustered"
interrupt mode, as it was only available through platform data and there
are no users of it in the mainline kernel.
Additionally gpio-keys device used by Spitz converted to use device
properties instead of platform data.
I would prefer not to have the song and dance of merging first 2 patches
through the input tree, waiting, merging the spitz patches through SoC
tree, waiting, and finally merging the last patch to matrix keypad
through input again, so maybe we could merge it all through SoC?
Alternatively, I could merge everything through input. What do you
think?
Dmitry Torokhov (5):
Input: matrix_keypad - remove support for clustered interrupt
Input: matrix_keypad - switch to gpiod API and generic device
properties
ARM: spitz: Use software nodes/properties for the GPIO-driven buttons
ARM: spitz: Use software nodes/properties for the matrix keypad
Input: matrix_keypad - remove support for platform data
arch/arm/mach-pxa/spitz.c | 163 ++++++++----
drivers/input/keyboard/matrix_keypad.c | 334 ++++++++++---------------
include/linux/input/matrix_keypad.h | 48 ----
3 files changed, 248 insertions(+), 297 deletions(-)
Thanks.
--
Dmitry
next reply other threads:[~2024-08-05 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 1:47 Dmitry Torokhov [this message]
2024-08-05 1:47 ` [PATCH 1/5] Input: matrix_keypad - remove support for clustered interrupt Dmitry Torokhov
2024-08-05 1:47 ` [PATCH 2/5] Input: matrix_keypad - switch to gpiod API and generic device properties Dmitry Torokhov
2024-08-05 1:47 ` [PATCH 3/5] ARM: spitz: Use software nodes/properties for the GPIO-driven buttons Dmitry Torokhov
2024-08-05 1:47 ` [PATCH 4/5] ARM: spitz: Use software nodes/properties for the matrix keypad Dmitry Torokhov
2024-08-05 1:47 ` [PATCH 5/5] Input: matrix_keypad - remove support for platform data Dmitry Torokhov
2024-08-23 15:51 ` [PATCH 0/5] Remove support for platform data from matrix keypad driver Linus Walleij
2024-08-23 16:02 ` Dmitry Torokhov
2024-08-26 8:52 ` Linus Walleij
2024-09-05 14:36 ` Arnd Bergmann
2024-09-06 5:24 ` 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=20240805014710.1961677-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=soc@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).