From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Joel Selvaraj <joelselvaraj.oss@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Henrik Rydberg <rydberg@bitmath.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Dang Huynh <danct12@riseup.net>,
Amit Pundir <amit.pundir@linaro.org>
Subject: Re: [PATCH v10 2/2] Input: Add Novatek NT36xxx touchscreen driver
Date: Fri, 1 Sep 2023 02:37:37 +0200 [thread overview]
Message-ID: <5b46f0ab-afb4-475d-b338-ed230c8b4343@linaro.org> (raw)
In-Reply-To: <500b52ee-02e5-4809-b03b-21a9ad6d2b30@gmail.com>
On 18.08.2023 00:17, Joel Selvaraj wrote:
> Hi Konrad,
>
> On 8/16/23 12:36, Konrad Dybcio wrote:
>> Do you have your end outcome somewhere?
>
> Here is the driver changes on top of upstream "drivers/input/touchscreen/novatek-nvt-ts.c"
>
> Link: https://gitlab.com/sdm845-mainline/linux/-/commit/d2f7702a7f6a72eaf2655840036668398942c194
>
> and here is how I specified it in the Poco F1 dts:
>
> Link: https://gitlab.com/sdm845-mainline/linux/-/commit/4dd6e4578cc737d2584c7f9657f9f185effe9035
>
> Regards
> Joel Selvaraj
Hm, the one present in mainline is quite lackluster compared to this
one that Angelo made..
Konrad
prev parent reply other threads:[~2023-09-01 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 23:38 [PATCH v10 0/2] Add Novatek NT36xxx touchscreen driver Konrad Dybcio
2023-08-08 23:38 ` [PATCH v10 1/2] dt-bindings: touchscreen: Add binding for Novatek NT36xxx ICs Konrad Dybcio
2023-08-08 23:38 ` [PATCH v10 2/2] Input: Add Novatek NT36xxx touchscreen driver Konrad Dybcio
2023-08-16 1:09 ` Joel Selvaraj
2023-08-16 17:36 ` Konrad Dybcio
2023-08-17 22:17 ` Joel Selvaraj
2023-09-01 0:37 ` Konrad Dybcio [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=5b46f0ab-afb4-475d-b338-ed230c8b4343@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=amit.pundir@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=danct12@riseup.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=joelselvaraj.oss@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@kernel.org \
--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).