From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Nikita Travkin <nikita@trvn.ru>, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Input: zinitix - Read and cache device version numbers
Date: Sat, 31 Aug 2024 19:07:02 -0700 [thread overview]
Message-ID: <ZtPMRlR3X_s2-O9R@google.com> (raw)
In-Reply-To: <20240830-zinitix-tk-versions-v2-1-90eae6817eda@linaro.org>
Hi Linus,
On Fri, Aug 30, 2024 at 04:04:27PM +0200, Linus Walleij wrote:
> The chip hardware revision, firmware version and regdata
> revision is needed to discern because for example touchkeys
> are handled by different registers on different versions of
> the chip. Example output from BT404:
>
> Zinitix-TS 3-0020: chip revision 4040 firmware version 0088
> regdata version 0004
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Move read status into the per-device struct.
Thanks for making this change.
> ---
> drivers/input/touchscreen/zinitix.c | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/drivers/input/touchscreen/zinitix.c b/drivers/input/touchscreen/zinitix.c
> index 1df93c96f6bf..e47e0bff80db 100644
> --- a/drivers/input/touchscreen/zinitix.c
> +++ b/drivers/input/touchscreen/zinitix.c
> @@ -150,6 +150,10 @@ struct bt541_ts_data {
> u32 zinitix_mode;
> u32 keycodes[MAX_SUPPORTED_BUTTON_NUM];
> int num_keycodes;
> + bool read_versioninfo;
I renamed this to "have_versioninfo" and applied.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-09-01 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 14:04 [PATCH v2 0/2] Input: zinitix - Handle chip revisions for touchkeys Linus Walleij
2024-08-30 14:04 ` [PATCH v2 1/2] Input: zinitix - Read and cache device version numbers Linus Walleij
2024-09-01 2:07 ` Dmitry Torokhov [this message]
2024-08-30 14:04 ` [PATCH v2 2/2] Input: zinitix - Varying icon status registers Linus Walleij
2024-09-01 2:09 ` 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=ZtPMRlR3X_s2-O9R@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=nikita@trvn.ru \
/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.