[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHCN7xJmJH1gqnE1TBi7hEYnhg0aV8TOW8==QxXV3CEOOk560g@mail.gmail.com>
Date: Mon, 4 Nov 2019 08:19:28 -0600
From: Adam Ford <aford173@...il.com>
To: Sven Van Asbroeck <thesven73@...il.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Marek Vasut <marex@...x.de>, linux-input@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] Input: ili210x - add ILI2117 support
On Mon, Nov 4, 2019 at 7:49 AM Sven Van Asbroeck <thesven73@...il.com> wrote:
>
> On Mon, Nov 4, 2019 at 2:01 AM Dmitry Torokhov
> <dmitry.torokhov@...il.com> wrote:
> >
> > Can you please tell me what device you have? Do the patches work for
> > you?
>
> I have an ILI2117A/ILI2118A.
>
> I'll try out the patches today. I'm stuck with a 4.1 vendor kernel, so
> I'll need to backport the (patched) mainline driver to 4.1 before
> I'm able to test.
>
> I wil try Marek's patch, and Dmitry's rebased patch from
> https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/log/?h=ili2xxx-touchscreen
> and let you know the results.
For what it's worth, I tried the 3-patch series from that branch on
5.4-RC5, but the ts_calibrate and ts_test_mt do not appear to receive
touch info. They execute when I 'export
TSLIB_TSDEVICE=/dev/input/event0' but I don't get touch data.
If I do a hex-dump of /dev/event0 and it dumps data if and only if I
hold my finger on the touch screen for a while.
I'll try just doing the 1st patch to see if it it's any better.
adam
>
> If the problem with Dmitry's patch is located in ili251x_read_touch_data,
> then using a ILI2117A should work fine.
Powered by blists - more mailing lists