From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Heiko Stübner" <heiko@sntech.de>, linux-input@vger.kernel.org
Cc: Andreas Kemnade <andreas@kemnade.info>, linux-kernel@vger.kernel.org
Subject: [PATCH 00/18] zforse_ts: assorted cleanups
Date: Fri, 23 Aug 2024 22:50:24 -0700 [thread overview]
Message-ID: <20240824055047.1706392-1-dmitry.torokhov@gmail.com> (raw)
Hi,
This is a set of somewhat random cleanups for the zforce_ts driver.
Heiko, Andreas, if you still have access to the hardware it would be
great if you could give it a spin.
Thanks!
Dmitry Torokhov (17):
Input: zforce_ts - simplify reporting of slot state
Input: zforce_ts - remove support for platfrom data
Input: zforce_ts - do not explicitly set EV_SYN, etc bits
Input: zforce_ts - handle errors from input_mt_init_sots()
Input: zforce_ts - remove unneeded locking
Input: zforce_ts - ensure that pm_stay_awake() and pm_relax() are balanced
Input: zforce_ts - use guard notation when acquiring mutexes
Input: zforce_ts - switch to using get_unaligned_le16
Input: zforce_ts - make parsing of contacts less confusing
Input: zforce_ts - do not ignore errors when acquiring regulator
Input: zforce_ts - use dev_err_probe() where appropriate
Input: zforce_ts - make zforce_idtable constant
Input: zforce_ts - stop treating VDD regulator as optional
Input: zforce_ts - switch to using devm_regulator_get_enable()
Input: zforce_ts - do not hardcode interrupt level
Input: zforce_ts - remove assert/deassert wrappers
Input: zforce_ts - switch to using asynchronous probing
Sudip Mukherjee (1):
Input: zforce_ts - use devm_add_action_or_reset()
drivers/input/touchscreen/zforce_ts.c | 474 ++++++++++--------------
include/linux/platform_data/zforce_ts.h | 15 -
2 files changed, 192 insertions(+), 297 deletions(-)
delete mode 100644 include/linux/platform_data/zforce_ts.h
--
Dmitry
next reply other threads:[~2024-08-24 5:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 5:50 Dmitry Torokhov [this message]
2024-08-24 5:50 ` [PATCH 01/18] Input: zforce_ts - use devm_add_action_or_reset() Dmitry Torokhov
2024-08-24 11:13 ` Heiko Stübner
2024-08-29 17:54 ` Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 02/18] Input: zforce_ts - simplify reporting of slot state Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 03/18] Input: zforce_ts - remove support for platfrom data Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 04/18] Input: zforce_ts - do not explicitly set EV_SYN, etc bits Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 05/18] Input: zforce_ts - handle errors from input_mt_init_sots() Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 06/18] Input: zforce_ts - remove unneeded locking Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 07/18] Input: zforce_ts - ensure that pm_stay_awake() and pm_relax() are balanced Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 08/18] Input: zforce_ts - use guard notation when acquiring mutexes Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 09/18] Input: zforce_ts - switch to using get_unaligned_le16 Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 10/18] Input: zforce_ts - make parsing of contacts less confusing Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 11/18] Input: zforce_ts - do not ignore errors when acquiring regulator Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 12/18] Input: zforce_ts - use dev_err_probe() where appropriate Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 13/18] Input: zforce_ts - make zforce_idtable constant Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 14/18] Input: zforce_ts - stop treating VDD regulator as optional Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 15/18] Input: zforce_ts - switch to using devm_regulator_get_enable() Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 16/18] Input: zforce_ts - do not hardcode interrupt level Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 17/18] Input: zforce_ts - remove assert/deassert wrappers Dmitry Torokhov
2024-08-24 5:50 ` [PATCH 18/18] Input: zforce_ts - switch to using asynchronous probing Dmitry Torokhov
2024-09-02 8:08 ` [PATCH 00/18] zforse_ts: assorted cleanups Andreas Kemnade
2024-09-06 5:49 ` 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=20240824055047.1706392-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=andreas@kemnade.info \
--cc=heiko@sntech.de \
--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;
as well as URLs for NNTP newsgroup(s).