From: Markuss Broks <markuss.broks@gmail.com>
To: Joel Selvaraj <joelselvaraj.oss@gmail.com>,
Caleb Connolly <caleb@connolly.tech>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Henrik Rydberg <rydberg@bitmath.org>,
Arnd Bergmann <arnd@arndb.de>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Jeff LaBundy <jeff@labundy.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jean Delvare <jdelvare@suse.de>,
Max Krummenacher <max.krummenacher@toradex.com>,
Job Noorman <job@noorman.info>,
Alistair Francis <alistair@alistair23.me>,
Chris Morgan <macromorgan@hotmail.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 2/5] Input: add driver for Focaltech FTS touchscreen
Date: Sun, 9 Apr 2023 16:32:27 +0300 [thread overview]
Message-ID: <f9c8e0d4-1d0c-cefc-866c-046d4d374576@gmail.com> (raw)
In-Reply-To: <d40faca2-fe5d-5b5a-eefe-68eb3e5e8125@gmail.com>
Hi Joel,
Sorry for responding late:
On 3/13/23 00:21, Joel Selvaraj wrote:
> Hi Markuss,
>
> Thanks for the quick review! I agree with most of your comments and will
> fix them in a v2 soon. I have a few doubts as discussed below.
>
> On 12/03/23 15:40, Markuss Broks wrote:
>
>> Why is the _ratelimited variant necessary?
> I assumed in case of the interrupt working, but i2c reads fail for some
> reason, it would spam a lot of error messages if the user touches the
> screen continuously, like a swipe up gesture or something.
>
> I referred to ad7879 touchscreen's irq handling code [1] and thought
> it's probably best to do this, to be on the safe side. I will remove
> this if it's not needed in v2.
>
>> Overall, I think it's better to cast the data type to a struct, which
>> would make this seem with less random.
> Sorry, I am not sure I got this right. Do you mean I create an array of
> struct called say "fts_point" that stores the x, y, type, etc. info of
> all the points, then report it separately. Like similar to something
> done by the auo-pixcir touchscreen driver [2]?
By that I meant doing something like the Zinitix driver[1] does. It has
a struct data type for whatever you read from hardware, e.g.
struct point_coord {
__le16 x;
__le16 y;
...
};
from that driver. That way you can cast the data read to that struct and
have it look a bit nicer.
This is just a suggestion though, you have the final choice in what
design you choose for your code :)
>
> If I didn't get this correctly, can you show me some code in mainline,
> that does it? It would be very helpful.
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/input/touchscreen/ad7879.c?h=v6.3-rc1#n250
> [2]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/input/touchscreen/auo-pixcir-ts.c?h=v6.3-rc1#n162
>
>> - Markuss
> Thanks,
> Joel
[1]
https://elixir.free-electrons.com/linux/v6.3-rc5/source/drivers/input/touchscreen/zinitix.c
- Markuss
next prev parent reply other threads:[~2023-04-09 13:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 9:32 [PATCH 0/5] Add support for Focaltech FTS Touchscreen Joel Selvaraj
2023-03-12 9:32 ` [PATCH 1/5] dt-bindings: input: touchscreen: add bindings for focaltech,fts Joel Selvaraj
2023-03-12 20:47 ` Krzysztof Kozlowski
2023-03-13 0:21 ` Joel Selvaraj
2023-03-13 6:42 ` Krzysztof Kozlowski
2023-03-13 6:53 ` Joel Selvaraj
2023-03-14 14:10 ` Rob Herring
2023-03-12 9:32 ` [PATCH 2/5] Input: add driver for Focaltech FTS touchscreen Joel Selvaraj
2023-03-12 20:40 ` Markuss Broks
2023-03-12 22:21 ` Joel Selvaraj
2023-04-09 13:32 ` Markuss Broks [this message]
2023-04-09 14:24 ` Joel Selvaraj
2023-03-14 3:42 ` Jeff LaBundy
2023-03-14 4:33 ` Joel Selvaraj
2023-03-12 9:32 ` [PATCH 3/5] arm64: dts: qcom: sdm845-xiaomi-beryllium-common: add touchscreen related nodes Joel Selvaraj
2023-03-12 9:32 ` [PATCH 4/5] arm64: dts: qcom: sdm845-xiaomi-beryllium-ebbg: introduce support for fts touchscreen Joel Selvaraj
2023-03-12 20:48 ` Krzysztof Kozlowski
2023-03-12 9:32 ` [PATCH 5/5] arm64: dts: qcom: sdm845-shift-axolotl: update focaltech touchscreen properties Joel Selvaraj
2023-03-12 20:49 ` Krzysztof Kozlowski
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=f9c8e0d4-1d0c-cefc-866c-046d4d374576@gmail.com \
--to=markuss.broks@gmail.com \
--cc=agross@kernel.org \
--cc=alistair@alistair23.me \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=caleb@connolly.tech \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jdelvare@suse.de \
--cc=jeff@labundy.com \
--cc=job@noorman.info \
--cc=joelselvaraj.oss@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=max.krummenacher@toradex.com \
--cc=neil.armstrong@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--cc=rydberg@bitmath.org \
--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 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).