From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Vincent Knecht <vincent.knecht@mailoo.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, w.david0@protonmail.com,
stephan@gerhold.net, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v4 3/5] Input: msg2638 - Add support for msg2138
Date: Mon, 14 Nov 2022 17:15:19 -0800 [thread overview]
Message-ID: <Y3LoJ6KketQZAXvM@google.com> (raw)
In-Reply-To: <20221110171952.34207-4-vincent.knecht@mailoo.org>
On Thu, Nov 10, 2022 at 06:19:46PM +0100, Vincent Knecht wrote:
> msg2138 only supports 2 fingers presses, and needs different processing
> since second finger press is encoded as a delta position wrt. first one
> and the packet/touch_event structs are not the same as msg2638.
>
> Add support for it by implementing distinct structs and irq handler.
>
> Signed-off-by: Vincent Knecht <vincent.knecht@mailoo.org>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2022-11-15 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 17:19 [PATCH v4 0/5] Input: msg2638: Add support for msg2138 and key Vincent Knecht
2022-11-10 17:19 ` [PATCH v4 1/5] Input: msg2638 - Set max finger number and irqhandler from driver data Vincent Knecht
2022-11-15 1:14 ` Dmitry Torokhov
2022-11-10 17:19 ` [PATCH v4 2/5] dt-bindings: input: touchscreen: msg2638: Document msg2138 support Vincent Knecht
2022-11-15 1:15 ` Dmitry Torokhov
2022-11-10 17:19 ` [PATCH v4 3/5] Input: msg2638 - Add support for msg2138 Vincent Knecht
2022-11-15 1:15 ` Dmitry Torokhov [this message]
2022-11-10 17:19 ` [PATCH v4 4/5] dt-bindings: input: touchscreen: msg2638: Document keys support Vincent Knecht
2022-11-10 17:19 ` [PATCH v4 5/5] Input: msg2638 - Add support for msg2138 key events Vincent Knecht
2022-11-15 1:17 ` 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=Y3LoJ6KketQZAXvM@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=vincent.knecht@mailoo.org \
--cc=w.david0@protonmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.