From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Sangwon Jee <jeesw@melfas.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Henrik Rydberg <rydberg@bitmath.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kaustabh Chakraborty <kauschluss@disroot.org>
Subject: [PATCH RFC v2 3/5] Input: melfas-mip4 - add support for touchkey input events
Date: Fri, 13 Jun 2025 01:11:35 +0530 [thread overview]
Message-ID: <20250613-mip4-touchkey-v2-3-9bbbe14c016d@disroot.org> (raw)
In-Reply-To: <20250613-mip4-touchkey-v2-0-9bbbe14c016d@disroot.org>
The MIP4 protocol are supposed to support touchscreens, touchkeys, and
combo-devices. The driver handles touchscreen events, but touchkey
events are unimplemented.
Implement them. If compiled with devicetree support, the driver attempts
to retrieve keycodes from a property named "linux,keycodes".
Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
---
drivers/input/touchscreen/melfas_mip4.c | 32 ++++++++++++++++++++++++++++++--
1 file changed, 30 insertions(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/melfas_mip4.c b/drivers/input/touchscreen/melfas_mip4.c
index a6946e3d8376d7e9b4c26f4194409e0ba78bb075..061ac353bc7a2e28f17581411af81f35c89733a1 100644
--- a/drivers/input/touchscreen/melfas_mip4.c
+++ b/drivers/input/touchscreen/melfas_mip4.c
@@ -169,7 +169,7 @@ struct mip4_ts {
unsigned int event_format;
unsigned int key_num;
- unsigned short key_code[MIP4_MAX_KEYS];
+ unsigned int key_code[MIP4_MAX_KEYS];
bool wake_irq_enabled;
@@ -337,8 +337,13 @@ static int mip4_query_device(struct mip4_ts *ts)
ts->ppm_x, ts->ppm_y);
/* Key ts */
- if (ts->node_key > 0)
+ if (ts->node_key > MIP4_MAX_KEYS) {
+ dev_warn(&ts->client->dev,
+ "Too many keys (%u) found\n", ts->node_key);
+ ts->key_num = MIP4_MAX_KEYS;
+ } else {
ts->key_num = ts->node_key;
+ }
}
/* Protocol */
@@ -1080,6 +1085,7 @@ static int mip4_flash_fw(struct mip4_ts *ts,
const u8 *fw_data, u32 fw_size, u32 fw_offset)
{
struct i2c_client *client = ts->client;
+ unsigned int i;
int offset;
u16 buf_addr;
int error, error2;
@@ -1149,6 +1155,11 @@ static int mip4_flash_fw(struct mip4_ts *ts,
input_abs_set_res(ts->input, ABS_X, ts->ppm_x);
input_abs_set_res(ts->input, ABS_Y, ts->ppm_y);
+ for (i = 0; i < ts->key_num; i++) {
+ if (ts->key_code[i])
+ input_set_capability(ts->input, EV_KEY, ts->key_code[i]);
+ }
+
return error ? error : 0;
}
@@ -1425,6 +1436,7 @@ static int mip4_probe(struct i2c_client *client)
{
struct mip4_ts *ts;
struct input_dev *input;
+ unsigned int i;
int error;
if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C)) {
@@ -1471,6 +1483,17 @@ static int mip4_probe(struct i2c_client *client)
input_set_drvdata(input, ts);
+#ifdef CONFIG_OF
+ error = of_property_read_u32_array(client->dev.of_node, "linux,keycodes",
+ ts->key_code, ts->key_num);
+ if (error && ts->key_num) {
+ dev_warn(&client->dev,
+ "Failed to get codes for %u supported keys", ts->key_num);
+ /* Disable touchkey support */
+ ts->key_num = 0;
+ }
+#endif
+
input->keycode = ts->key_code;
input->keycodesize = sizeof(*ts->key_code);
input->keycodemax = ts->key_num;
@@ -1491,6 +1514,11 @@ static int mip4_probe(struct i2c_client *client)
if (error)
return error;
+ for (i = 0; i < ts->key_num; i++) {
+ if (ts->key_code[i])
+ input_set_capability(input, EV_KEY, ts->key_code[i]);
+ }
+
i2c_set_clientdata(client, ts);
error = devm_request_threaded_irq(&client->dev, client->irq,
--
2.49.0
next prev parent reply other threads:[~2025-06-12 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 19:41 [PATCH RFC v2 0/5] Support for MELFAS MIP4 touchkey devices Kaustabh Chakraborty
2025-06-12 19:41 ` [PATCH RFC v2 1/5] dt-bindings: input: melfas-mip4: convert to dtschema Kaustabh Chakraborty
2025-06-13 7:09 ` Krzysztof Kozlowski
2025-06-12 19:41 ` [PATCH RFC v2 2/5] dt-bindings: input: melfas-mip4: document linux,keycodes property Kaustabh Chakraborty
2025-06-12 20:58 ` Rob Herring (Arm)
2025-06-12 19:41 ` Kaustabh Chakraborty [this message]
2025-06-29 5:12 ` [PATCH RFC v2 3/5] Input: melfas-mip4 - add support for touchkey input events Dmitry Torokhov
2025-06-30 18:44 ` Kaustabh Chakraborty
2025-06-12 19:41 ` [PATCH RFC v2 4/5] Input: melfas-mip4 - initialize touch events only if the device is a touchscreen Kaustabh Chakraborty
2025-06-12 19:41 ` [PATCH RFC v2 5/5] Input: melfas-mip4 - add support for event formats 4 and 9 Kaustabh Chakraborty
2025-06-13 8:44 ` [PATCH RFC v2 0/5] Support for MELFAS MIP4 touchkey devices Kaustabh Chakraborty
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=20250613-mip4-touchkey-v2-3-9bbbe14c016d@disroot.org \
--to=kauschluss@disroot.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeesw@melfas.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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