linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org
Cc: Scott Liu <scott.liu@emc.com.tw>,
	James Chen <james.chen@emc.com.tw>,
	Johnny Chuang <johnny.chuang@emc.com.tw>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org,
	Henrik Rydberg <rydberg@bitmath.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh-dt@kernel.org>
Subject: Re: [PATCH v2 0/9] input: elants: Support Asus TF300T touchscreen
Date: Thu, 12 Dec 2019 03:29:31 +0300	[thread overview]
Message-ID: <3da0327c-d7c4-b0f2-9ab4-b7088891ef7c@gmail.com> (raw)
In-Reply-To: <cover.1576079249.git.mirq-linux@rere.qmqm.pl>

11.12.2019 19:03, Michał Mirosław пишет:
> This series cleans up the driver a bit and implements changes needed to
> support EKTF3624-based touchscreen used in eg. Asus TF300T tablet. 
> 
> ---
> v2: extended with Dmitry's patches (replaced v1 patches 3 and 4)
> 
> Dmitry Osipenko (3):
>   input: elants: support 0x66 reply opcode for reporting touches
>   dt-bindings: input: elants-i2c: Document common touchscreen properties
>   dt-bindings: input: elants-i2c: Document eKTF3624
> 
> Michał Mirosław (6):
>   input: elants: document some registers and values
>   input: elants: support old touch report format
>   input: elants: remove unused axes
>   input: elants: override touchscreen info with DT properties
>   input: elants: refactor elants_i2c_execute_command()
>   input: elants: read touchscreen size for EKTF3624
> 
>  .../devicetree/bindings/input/elants_i2c.txt  |   6 +-
>  drivers/input/touchscreen/elants_i2c.c        | 358 ++++++++++++------
>  2 files changed, 239 insertions(+), 125 deletions(-)
> 

Hello Michał,

The series works and looks good to me, eKTF3624 touchscreen is working
fine on Nexus 7. Thank you very much!

  parent reply	other threads:[~2019-12-12  0:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 16:03 [PATCH v2 0/9] input: elants: Support Asus TF300T touchscreen Michał Mirosław
2019-12-11 16:03 ` [PATCH v2 3/9] input: elants: remove unused axes Michał Mirosław
2019-12-12  0:34   ` Dmitry Osipenko
2019-12-11 16:03 ` [PATCH v2 2/9] input: elants: support old touch report format Michał Mirosław
2019-12-12  0:54   ` Dmitry Osipenko
2019-12-12 19:45     ` Michał Mirosław
2019-12-13  0:06       ` Dmitry Osipenko
2019-12-11 16:03 ` [PATCH v2 1/9] input: elants: document some registers and values Michał Mirosław
2019-12-12  0:34   ` Dmitry Osipenko
2019-12-11 16:03 ` [PATCH v2 4/9] input: elants: override touchscreen info with DT properties Michał Mirosław
2019-12-11 16:03 ` [PATCH v2 6/9] input: elants: read touchscreen size for EKTF3624 Michał Mirosław
2019-12-12  0:39   ` Dmitry Osipenko
2019-12-11 16:03 ` [PATCH v2 5/9] input: elants: refactor elants_i2c_execute_command() Michał Mirosław
2019-12-12  0:30   ` Dmitry Osipenko
2019-12-11 16:03 ` [PATCH v2 7/9] input: elants: support 0x66 reply opcode for reporting touches Michał Mirosław
2019-12-11 16:03 ` [PATCH v2 8/9] dt-bindings: input: elants-i2c: Document common touchscreen properties Michał Mirosław
2019-12-12  0:58   ` Dmitry Osipenko
2019-12-12  1:00     ` Dmitry Osipenko
2019-12-19 21:39   ` Rob Herring
2019-12-11 16:03 ` [PATCH v2 9/9] dt-bindings: input: elants-i2c: Document eKTF3624 Michał Mirosław
2019-12-19 21:43   ` Rob Herring
2019-12-20  1:10     ` Dmitry Osipenko
2019-12-12  0:29 ` Dmitry Osipenko [this message]
2019-12-12 19:24 ` [PATCH v2 0/9] input: elants: Support Asus TF300T touchscreen Dmitry Torokhov
2020-01-07  5:33   ` Dmitry Osipenko
2020-01-08 15:00     ` Johnny.Chuang
2020-01-08 15:37       ` Dmitry Osipenko
2020-01-23 19:16         ` Dmitry Osipenko
2020-02-05 22:04           ` Dmitry Osipenko

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=3da0327c-d7c4-b0f2-9ab4-b7088891ef7c@gmail.com \
    --to=digetx@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=james.chen@emc.com.tw \
    --cc=johnny.chuang@emc.com.tw \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=robh-dt@kernel.org \
    --cc=rydberg@bitmath.org \
    --cc=scott.liu@emc.com.tw \
    /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).