From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Carl Philipp Klemm <philipp@uvos.xyz>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-input@vger.kernel.org,
tony@atomide.com
Subject: Re: [PATCH v3] Drivers: input: misc: Add driver touchscreen-buttons to support physically labeled buttons on touch screen surfaces
Date: Sat, 21 Dec 2024 17:28:06 +0200 [thread overview]
Message-ID: <61a0c65e-386f-40d6-bc5f-f2b5a8d03cb5@gmail.com> (raw)
In-Reply-To: <20201115194421.b08f1458bc383c38d74d9982@uvos.xyz>
Hi,
On 15.11.20 г. 20:44 ч., Carl Philipp Klemm wrote:
> Adds a driver for supporting permanet, physically labeled, buttons on
> touchscreen surfaces. As are common on android phones designed with android 1.0
> to 2.3 in mind. The driver works by attaching to another input device and
> mirroring its events, while inserting key events and filtering for touches that
> land on the buttons. Buttons are arbitrary rectangles configurable via dts.
>
> Signed-off-by: Carl Philipp Klemm <philipp@uvos.xyz>
> ---
>
> Changes since v2:
> - Decrease the potential for memory leaks by migrating to devm_* where possible
>
> ---
> drivers/input/misc/Kconfig | 8 +
> drivers/input/misc/Makefile | 1 +
> drivers/input/misc/touchscreen-buttons.c | 587 +++++++++++++++++++++++
> 3 files changed, 596 insertions(+)
> create mode 100644 drivers/input/misc/touchscreen-buttons.c
>
Did that patch somehow went unnoticed?
Regards,
Ivo
prev parent reply other threads:[~2024-12-21 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 18:44 [PATCH v3] Drivers: input: misc: Add driver touchscreen-buttons to support physically labeled buttons on touch screen surfaces Carl Philipp Klemm
2024-12-21 15:28 ` Ivaylo Dimitrov [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=61a0c65e-386f-40d6-bc5f-f2b5a8d03cb5@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=philipp@uvos.xyz \
--cc=tony@atomide.com \
/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).