From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matthias Fend <Matthias.Fend@wolfvision.net>
Cc: Martin Kepplinger <martink@posteo.de>,
Dixit Parmar <dixitparmar19@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] Face lift for st1232 touchscreen driver
Date: Mon, 28 Oct 2019 21:09:33 -0700 [thread overview]
Message-ID: <20191029040933.GC57214@dtor-ws> (raw)
In-Reply-To: <VI1PR08MB37588375F08EA4F692AE475D85660@VI1PR08MB3758.eurprd08.prod.outlook.com>
On Mon, Oct 28, 2019 at 07:28:51AM +0000, Matthias Fend wrote:
> Hi Dmitry,
>
> > -----Ursprüngliche Nachricht-----
> > Von: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > Gesendet: Dienstag, 22. Oktober 2019 21:56
> > An: Martin Kepplinger <martink@posteo.de>
> > Cc: Dixit Parmar <dixitparmar19@gmail.com>; Henrik Rydberg
> > <rydberg@bitmath.org>; Kuninori Morimoto
> > <kuninori.morimoto.gx@renesas.com>; Matthias Fend
> > <Matthias.Fend@wolfvision.net>; linux-input@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Betreff: [PATCH 0/8] Face lift for st1232 touchscreen driver
> >
> > This series cleans up the driver and switches it over to the slotted
> > multi-touch protocol (MT-B) that should reduce the traffic between kernel
> > and userspace.
> >
> > Note that I do not have hardware, so I would appreciate if you could try
> > running it and tell me if it is broken or not.
>
> Looks good. I tested the series from your st1232 branch [1] and could not see any regressions.
> Note that I my 'real' application only supports ONE finger. So, the other fingers are just tested with debug output.
Thank you for testing. I committed the patches.
--
Dmitry
prev parent reply other threads:[~2019-10-29 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 19:56 [PATCH 0/8] Face lift for st1232 touchscreen driver Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 1/8] Input: st1232 - simplify parsing of read buffer Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 2/8] Input: st1232 - do not unconditionally configure as wakeup source Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 3/8] Input: st1232 - rely on I2C core to configure wakeup interrupt Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 4/8] Input: st1232 - do not reset the chip too early Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 5/8] Input: st1232 - do not allocate fingers data separately Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 6/8] Input: st1232 - do not set parent device explicitly Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 7/8] Input: st1232 - note that the receive buffer is DMA-safe Dmitry Torokhov
2019-10-22 19:56 ` [PATCH 8/8] Input: st1232 - switch to using MT-B protocol Dmitry Torokhov
2019-10-28 7:28 ` AW: [PATCH 0/8] Face lift for st1232 touchscreen driver Matthias Fend
2019-10-29 4:09 ` Dmitry Torokhov [this message]
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=20191029040933.GC57214@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Matthias.Fend@wolfvision.net \
--cc=dixitparmar19@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=rydberg@bitmath.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).