Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   =?UTF-8?q?Jonathan=20Neusch=C3=A4fer?= <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>,
        =?UTF-8?q?Jonathan=20Neusch=C3=A4fer?= <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
Message-Id: <20201106112412.390724-1-j.neuschaefer@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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=C3=A4fer (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(-)

=2D-
2.28.0