From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-input@vger.kernel.org
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Support for ELAN eKTF2132 touchscreens
Date: Fri, 6 Nov 2020 12:24:09 +0100 [thread overview]
Message-ID: <20201106112412.390724-1-j.neuschaefer@gmx.net> (raw)
This series adds support for the ELAN eKTF2132 touchscreen controller to
the existing ektf2127 driver. It is similar to the eKTF2127, but it uses
a different packet type and format to report touch events.
My understanding of the packet format is based on the Kobo Arua vendor
kernel: https://github.com/neuschaefer/linux/blob/vendor/kobo-aura/drivers/input/touchscreen/elan_touch_i2c.c#L237
Jonathan Neuschäfer (3):
dt-bindings: input: ektf2127: Add elan,ektf2132 compatible string
Input: ektf2127 - Add support for eKTF2132 touchscreen
ARM: dts: imx50-kobo-aura: Enable eKTF2132 touchscreen
.../bindings/input/touchscreen/ektf2127.txt | 2 +-
arch/arm/boot/dts/imx50-kobo-aura.dts | 16 +++++++++-
drivers/input/touchscreen/ektf2127.c | 32 ++++++++++++++++++-
3 files changed, 47 insertions(+), 3 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-06 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 11:24 Jonathan Neuschäfer [this message]
2020-11-06 11:24 ` [PATCH 1/3] dt-bindings: input: ektf2127: Add elan,ektf2132 compatible string Jonathan Neuschäfer
2020-11-09 2:30 ` Dmitry Torokhov
2020-11-06 11:24 ` [PATCH 2/3] Input: ektf2127 - Add support for eKTF2132 touchscreen Jonathan Neuschäfer
2020-11-09 2:30 ` Dmitry Torokhov
2020-11-06 11:24 ` [PATCH 3/3] ARM: dts: imx50-kobo-aura: Enable " Jonathan Neuschäfer
2020-11-10 2:35 ` Shawn Guo
2020-11-10 3:12 ` Shawn Guo
2020-11-10 8:25 ` Jonathan Neuschäfer
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=20201106112412.390724-1-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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
all inboxes | Powered by JetHome®