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
Subject: Re: [PATCH RFC v2 0/5] Support for MELFAS MIP4 touchkey devices
Date: Fri, 13 Jun 2025 08:44:43 +0000 [thread overview]
Message-ID: <e6b71b3d3cacc2f112e62c57fd0c3c65@disroot.org> (raw)
In-Reply-To: <20250613-mip4-touchkey-v2-0-9bbbe14c016d@disroot.org>
On 2025-06-12 19:41, Kaustabh Chakraborty wrote:
> 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.
I see that there are 2 dts(i) files which use the compatible
"melfas,mip4_ts", as discovered from a simple grep in arch/. They are:
- arm64/qcom/msm8916-lg-m216.dts
- arm64/mediatek/mt8173-elm-hana.dtsi
Is it possible to change all references of the compatible to something more
generic, such as "melfas,mip4"?
prev parent reply other threads:[~2025-06-13 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 19:41 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 ` [PATCH RFC v2 3/5] Input: melfas-mip4 - add support for touchkey input events Kaustabh Chakraborty
2025-06-29 5:12 ` 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 ` Kaustabh Chakraborty [this message]
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=e6b71b3d3cacc2f112e62c57fd0c3c65@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®