From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Rob Herring <robh@kernel.org>
Cc: Sangwon Jee <jeesw@melfas.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Henrik Rydberg <rydberg@bitmath.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/4] dt-bindings: input: melfas-mip4: document linux,keycodes property
Date: Wed, 14 May 2025 18:13:55 +0000 [thread overview]
Message-ID: <2d990082fe70c2f63f5fbae2efaa3c76@disroot.org> (raw)
In-Reply-To: <20250509220658.GA74742-robh@kernel.org>
On 2025-05-09 22:06, Rob Herring wrote:
> On Sat, May 03, 2025 at 02:38:27PM +0530, Kaustabh Chakraborty wrote:
>> Document the linux,keycodes property. The property values are key codes
>> which are used in input key events generated by the touchkey device.
>>
>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
>> ---
>> Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt | 2 ++
>> 1 file changed, 2 insertions(+)
>
> Convert to DT schema if you want to add to this.
Sure will. Who would be the maintainer of this driver though?
MAINTAINERS says that the driver is 'Supported' but Sangwon's
e-mail is bouncing.
>
> Rob
next prev parent reply other threads:[~2025-05-14 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 9:08 [PATCH RFC 0/4] Support for MELFAS MIP4 touchkey devices Kaustabh Chakraborty
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 [this message]
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=2d990082fe70c2f63f5fbae2efaa3c76@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;
as well as URLs for NNTP newsgroup(s).