linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kepplinger Martin <Martin.Kepplinger@ginzinger.com>
To: Martin Kepplinger <martink@posteo.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: AW: [PATCH 2/3] Input: st1232 - add support for st1633
Date: Mon, 28 Jan 2019 08:49:26 +0000	[thread overview]
Message-ID: <20ec36c93a66462e893085af9920b3a5@ginzinger.com> (raw)
In-Reply-To: <20190128084449.16070-2-martink@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]


________________________________________
Von: Martin Kepplinger [martink@posteo.de]
Gesendet: Montag, 28. Jänner 2019 09:44
An: devicetree@vger.kernel.org; linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com; robh+dt@kernel.org; mark.rutland@arm.com; linux-kernel@vger.kernel.org; Kepplinger Martin
Betreff: [PATCH 2/3] Input: st1232 - add support for st1633

From: Martin Kepplinger <martin.kepplinger@ginzinger.com>

Add support for the Sitronix ST1633 touchscreen controller to the st1232
driver. A protocol spec can be found here:
www.ampdisplay.com/documents/pdf/AM-320480B6TZQW-TC0H.pdf

Signed-off-by: Martin Kepplinger <martin.kepplinger@ginzinger.com>
---

sorry, this is v3 of this series.

anyways, the of_device.h header isn't directly need now neither. thanks Dmitry!

                                 martin


revision history
----------------
v3: implement Dmitry's suggestion for i2c probe from v2 review
v2: use device_get_match_data(), invent an internal "have_z" bool property
v1: initial idea for the change



 drivers/input/touchscreen/Kconfig  |   6 +-
 drivers/input/touchscreen/st1232.c | 122 +++++++++++++++++++++--------
 2 files changed, 94 insertions(+), 34 deletions(-)


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3616 bytes --]

  reply	other threads:[~2019-01-28  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  8:44 [PATCH 1/3] dt-bindings: input: sitronix-st1232: add compatible string for ST1633 Martin Kepplinger
2019-01-28  8:44 ` [PATCH 2/3] Input: st1232 - add support for st1633 Martin Kepplinger
2019-01-28  8:49   ` Kepplinger Martin [this message]
2019-01-28 19:03   ` Dmitry Torokhov
2019-01-28 19:10     ` Martin Kepplinger
     [not found]       ` <419160a7-edf5-48cf-85ea-d6d5e9cd6e59.95bf7d06-047e-438c-8c7b-895af195351a.4c28554a-ad2d-4f90-8e2b-982cefd223a5@emailsignatures365.codetwo.com>
2019-01-29  7:07         ` AW: " Matthias Fend
2019-01-28  8:44 ` [PATCH 3/3] Input: st1232 - add Martin as module author Martin Kepplinger
2019-01-28 19:04   ` Dmitry Torokhov
2019-02-23  0:43 ` [PATCH 1/3] dt-bindings: input: sitronix-st1232: add compatible string for ST1633 Rob Herring

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=20ec36c93a66462e893085af9920b3a5@ginzinger.com \
    --to=martin.kepplinger@ginzinger.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martink@posteo.de \
    --cc=robh+dt@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).