From: Dmitry Mastykin <mastichi@gmail.com>
To: job@noorman.info, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
felix@kaechele.ca
Cc: Dmitry Mastykin <mastichi@gmail.com>
Subject: [PATCH v2] Input: himax_hx83112b - add support for HX83102J
Date: Thu, 20 Feb 2025 16:07:49 +0300 [thread overview]
Message-ID: <20250220130749.2019419-1-mastichi@gmail.com> (raw)
Tested on: Starry Electronic XR109IA2T LCM
Signed-off-by: Dmitry Mastykin <mastichi@gmail.com>
---
v2: Add compatible
drivers/input/touchscreen/himax_hx83112b.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/input/touchscreen/himax_hx83112b.c b/drivers/input/touchscreen/himax_hx83112b.c
index 896a145ddb2b..8f112e3038dd 100644
--- a/drivers/input/touchscreen/himax_hx83112b.c
+++ b/drivers/input/touchscreen/himax_hx83112b.c
@@ -399,6 +399,12 @@ static const struct himax_chip hx83100a_chip = {
.read_events = hx83100a_read_events,
};
+static const struct himax_chip hx83102j_chip = {
+ .id = 0x831029,
+ .check_id = himax_check_product_id,
+ .read_events = himax_read_events,
+};
+
static const struct himax_chip hx83112b_chip = {
.id = 0x83112b,
.check_id = himax_check_product_id,
@@ -407,6 +413,7 @@ static const struct himax_chip hx83112b_chip = {
static const struct i2c_device_id himax_ts_id[] = {
{ "hx83100a", (kernel_ulong_t)&hx83100a_chip },
+ { "hx83102j", (kernel_ulong_t)&hx83102j_chip },
{ "hx83112b", (kernel_ulong_t)&hx83112b_chip },
{ /* sentinel */ }
};
@@ -415,6 +422,7 @@ MODULE_DEVICE_TABLE(i2c, himax_ts_id);
#ifdef CONFIG_OF
static const struct of_device_id himax_of_match[] = {
{ .compatible = "himax,hx83100a", .data = &hx83100a_chip },
+ { .compatible = "himax,hx83102j", .data = &hx83102j_chip },
{ .compatible = "himax,hx83112b", .data = &hx83112b_chip },
{ /* sentinel */ }
};
--
2.34.1
reply other threads:[~2025-02-20 13:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250220130749.2019419-1-mastichi@gmail.com \
--to=mastichi@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=felix@kaechele.ca \
--cc=job@noorman.info \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).