From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: [PATCH v2 0/5] Input: gpio_decoder - update driver to use modern APIs
Date: Thu, 13 Nov 2025 16:44:41 +0100 [thread overview]
Message-ID: <20251113154616.3107676-1-andriy.shevchenko@linux.intel.com> (raw)
Update gpio_decoder driver to use modern in-kernel APIs.
Changelog v2:
- fixed typo (LKP), dunno what I have compiled before
v1: 20251112191412.2088105-1-andriy.shevchenko@linux.intel.com
Andy Shevchenko (5):
Input: gpio_decoder - make use of device properties
Input: gpio_decoder - unify messages with help of dev_err_probe()
Input: gpio_decoder - replace custom loop by
gpiod_get_array_value_cansleep()
Input: gpio_decoder - make use of the macros from bits.h
Input: gpio_decoder - don't use "proxy" headers
drivers/input/misc/gpio_decoder.c | 72 ++++++++++++++-----------------
1 file changed, 33 insertions(+), 39 deletions(-)
--
2.50.1
next reply other threads:[~2025-11-13 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 15:44 Andy Shevchenko [this message]
2025-11-13 15:44 ` [PATCH v2 1/5] Input: gpio_decoder - make use of device properties Andy Shevchenko
2025-11-13 15:44 ` [PATCH v2 2/5] Input: gpio_decoder - unify messages with help of dev_err_probe() Andy Shevchenko
2025-11-13 15:44 ` [PATCH v2 3/5] Input: gpio_decoder - replace custom loop by gpiod_get_array_value_cansleep() Andy Shevchenko
2025-11-13 15:44 ` [PATCH v2 4/5] Input: gpio_decoder - make use of the macros from bits.h Andy Shevchenko
2025-11-13 15:44 ` [PATCH v2 5/5] Input: gpio_decoder - don't use "proxy" headers Andy Shevchenko
2026-01-13 8:56 ` [PATCH v2 0/5] Input: gpio_decoder - update driver to use modern APIs Andy Shevchenko
2026-01-21 21:05 ` 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=20251113154616.3107676-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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