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 0/4] Support for MELFAS MIP4 touchkey devices
Date: Sat, 03 May 2025 14:38:26 +0530 [thread overview]
Message-ID: <20250503-mip4-touchkey-v1-0-b483cda29a5b@disroot.org> (raw)
MIP4 is a protocol developed and used by MELFAS in its touchscreen and
touchkey devices. The MIP4 touchscreen driver acknowledges the
touchscreen capabilities, but touchkeys are left unimplemented.
Apart from touchscreen + touchkey devices, the protocol is also used by
devices which are, functionally, touchkey devices. Thus, the driver
should also be compatible with those devices. This series aims to
introduce such required changes.
RFC: How should the compatible string be handled? The string defined in
dtschema is 'melfas,mip4_ts', which implies that it's a MIP4 touchscreen
by MELFAS.
Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
---
Kaustabh Chakraborty (4):
dt-bindings: input: melfas-mip4: document linux,keycodes property
Input: melfas-mip4 - add support for touchkey input events
Input: melfas-mip4 - initialize touch events only if the device is a touchscreen
Input: melfas-mip4 - add support for event formats 4 and 9
.../bindings/input/touchscreen/melfas_mip4.txt | 2 +
drivers/input/touchscreen/melfas_mip4.c | 98 ++++++++++++++++------
2 files changed, 74 insertions(+), 26 deletions(-)
---
base-commit: 3e039dcc9c1320c0d33ddd51c372dcc91d3ea3c7
change-id: 20250501-mip4-touchkey-66a113226bce
Best regards,
--
Kaustabh Chakraborty <kauschluss@disroot.org>
next reply other threads:[~2025-05-03 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 9:08 Kaustabh Chakraborty [this message]
2025-05-03 9:08 ` [PATCH RFC 1/4] dt-bindings: input: melfas-mip4: document linux,keycodes property Kaustabh Chakraborty
2025-05-09 22:06 ` Rob Herring
2025-05-14 18:13 ` Kaustabh Chakraborty
2025-05-03 9:08 ` [PATCH RFC 2/4] Input: melfas-mip4 - add support for touchkey input events Kaustabh Chakraborty
2025-05-03 9:08 ` [PATCH RFC 3/4] Input: melfas-mip4 - initialize touch events only if the device is a touchscreen Kaustabh Chakraborty
2025-05-03 9:08 ` [PATCH RFC 4/4] Input: melfas-mip4 - add support for event formats 4 and 9 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=20250503-mip4-touchkey-v1-0-b483cda29a5b@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
all inboxes | Powered by JetHome®