From: "'dmitry.torokhov@gmail.com'" <dmitry.torokhov@gmail.com>
To: Martin Kepplinger <martin.kepplinger@ginzinger.com>
Cc: Matthias Fend <Matthias.Fend@wolfvision.net>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] Input: st1232 - handle common DT bindings
Date: Mon, 11 Feb 2019 14:21:10 -0800 [thread overview]
Message-ID: <20190211222110.GC149505@dtor-ws> (raw)
In-Reply-To: <c0732084-3baf-949a-83b3-154e2e93463b@ginzinger.com>
On Mon, Feb 11, 2019 at 09:51:58AM +0100, Martin Kepplinger wrote:
> On 11.02.19 09:45, 'dmitry.torokhov@gmail.com' wrote:
> > Hi Matthias,
> >
> > On Mon, Feb 11, 2019 at 07:15:12AM +0000, Matthias Fend wrote:
> >> Hi Dmitry,
> >>
> >> You asked me if I could also include the conversion to touchscreen_report_pos() - which I did in this patch version.
> >> Is there anything else missing?
> >
> > Sorry, gmail decided to mark the v2 patches as spam for some reason :(
> > I fished them out and applied.
> >
> > Matthias, Martin, I noticed that the driver is still using MT-A
> > protocol. Could you convert it to the proper MT-B (slotted) protocol?
> >
>
> Yes, I thought about that actually. type A protocol is what matches the
> controller here... It stores touch points consecutively in memory, but I
> doubt that it tracks them (by keeping them at one position in its
> memory, for instance). But yes, I want to test that.
We still can do MT-B for such devices by employing in-kernel contact
tracking. See input_mt_assign_slots().
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-02-11 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1548757144-2222-1-git-send-email-matthias.fend@wolfvision.net>
[not found] ` <1548757144-2222-2-git-send-email-matthias.fend@wolfvision.net>
2019-02-11 7:15 ` AW: [PATCH 2/2] Input: st1232 - handle common DT bindings Matthias Fend
2019-02-11 8:45 ` 'dmitry.torokhov@gmail.com'
2019-02-11 8:51 ` Martin Kepplinger
2019-02-11 22:21 ` 'dmitry.torokhov@gmail.com' [this message]
[not found] <419160a7-edf5-48cf-85ea-d6d5e9cd6e59.95bf7d06-047e-438c-8c7b-895af195351a.6448af99-cd65-4518-8f79-5ccc17d038ab@emailsignatures365.codetwo.com>
2019-01-28 9:06 ` [PATCH 1/2] dt-bindings: input: touchscreen: st1232i: reference " Matthias Fend
2019-01-28 9:06 ` [PATCH 2/2] Input: st1232 - handle " Matthias Fend
2019-01-28 19:08 ` dmitry.torokhov
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=20190211222110.GC149505@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Matthias.Fend@wolfvision.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=martin.kepplinger@ginzinger.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.