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>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Johnny Chuang" <johnny.chuang.emc@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Hutterer <peter.hutterer@who-t.net>
Subject: Re: [PATCH RESEND v8 0/4] input: elants: Support Asus TF300T and Nexus 7 touchscreens
Date: Thu, 10 Dec 2020 23:13:30 +0300	[thread overview]
Message-ID: <76f75e8f-1895-6f51-eb1d-7d212a7e917f@gmail.com> (raw)
In-Reply-To: <cover.1604942771.git.mirq-linux@rere.qmqm.pl>

09.11.2020 20:28, Michał Mirosław пишет:
> This series cleans up the driver a bit and implements changes needed to
> support EKTF3624-based touchscreen used in Asus TF300T, Google Nexus 7
> and similar Tegra3-based tablets.
> 
> ---
> v2: extended with Dmitry's patches (replaced v1 patches 3 and 4)
> v3: rebased for v5.7-rc1
> v4: rebased onto v5.7-rc2+ (current Linus' master)
>     update "remove unused axes" and "refactor
>       elants_i2c_execute_command()" patches after review
>     add David's patch converting DT binding to YAML
> v5: rebased onto dtor/input/for-linus
> v6: rebased onto newer dtor/input/for-linus
>     remove yet unused constants from patch 1
>     added a new drive-by cleanup (last patch)
> v7: rebased onto current dtor/input/for-next
> v8: rebased onto current dtor/input/for-linus
> ---
> 
> Dmitry Osipenko (1):
>   input: elants: support 0x66 reply opcode for reporting touches
> 
> Michał Mirosław (3):
>   input: elants: document some registers and values
>   input: elants: support old touch report format
>   input: elants: read touchscreen size for EKTF3624
> 
>  drivers/input/touchscreen/elants_i2c.c | 149 +++++++++++++++++++++----
>  1 file changed, 127 insertions(+), 22 deletions(-)
> 

This patchset missed another kernel release cycle and touchscreen
hardware remains unusable on Nexus 7 [1] and other Asus devices.

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi?h=v5.10-rc7#n845

Dmitry Torokhov, could you please take a look at the v8 and let us know
whether it's good already or something needs to be improved?

  parent reply	other threads:[~2020-12-10 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 17:28 [PATCH RESEND v8 0/4] input: elants: Support Asus TF300T and Nexus 7 touchscreens Michał Mirosław
2020-11-09 17:28 ` [PATCH RESEND v8 1/4] input: elants: document some registers and values Michał Mirosław
2020-11-09 17:28 ` [PATCH RESEND v8 2/4] input: elants: support old touch report format Michał Mirosław
2020-11-09 17:28 ` [PATCH RESEND v8 3/4] input: elants: read touchscreen size for EKTF3624 Michał Mirosław
2020-11-09 17:28 ` [PATCH RESEND v8 4/4] input: elants: support 0x66 reply opcode for reporting touches Michał Mirosław
2020-12-10 20:13 ` Dmitry Osipenko [this message]
2020-12-11  6:53 [PATCH RESEND v8 0/4] input: elants: Support Asus TF300T and Nexus 7 touchscreens Michał Mirosław

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=76f75e8f-1895-6f51-eb1d-7d212a7e917f@gmail.com \
    --to=digetx@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=johnny.chuang.emc@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=peter.hutterer@who-t.net \
    /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).