From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Peng <daniel_peng@pegatron.corp-partner.google.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: input: i2c-hid: Introduce FocalTech FT8112
Date: Thu, 13 Nov 2025 11:52:42 +0100 [thread overview]
Message-ID: <7904826d-043d-4e63-9d38-e0763b3822ba@kernel.org> (raw)
In-Reply-To: <CAAq2-DFJ2HZQ=p5J7wppQWYh9tqrFxNqexYXFcVB=b1ufWgmXg@mail.gmail.com>
On 13/11/2025 11:44, Daniel Peng wrote:
> Hi Krzysztof,
>
> Sorry for the confusion.
> I just refer ilitek,ili2901.yaml as example to modify correct information
> for this device. And I create document file for FocalTech FT8112 device for
> Skywalker platform only.
> Moreover, modified related interrupt and reset gpio to map for Skywaler
> platform(MT8189).
>
> I think it would be good to create document. If any, please let me know.
>
Please don't top post.
There is no need for new document, everything is identical, so just add
new compatible to the other binding.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-13 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 6:00 [PATCH v4 1/2] dt-bindings: input: i2c-hid: Introduce FocalTech FT8112 daniel_peng
2025-11-13 6:00 ` [PATCH v4 2/2] HID: i2c-hid: Add " daniel_peng
2025-11-13 18:47 ` Doug Anderson
2025-11-13 7:56 ` [PATCH v4 1/2] dt-bindings: input: i2c-hid: Introduce " Krzysztof Kozlowski
[not found] ` <CAAq2-DFJ2HZQ=p5J7wppQWYh9tqrFxNqexYXFcVB=b1ufWgmXg@mail.gmail.com>
2025-11-13 10:52 ` Krzysztof Kozlowski [this message]
[not found] ` <CAAq2-DHouqsbOB75mifXVxQT+jZaho9RBB0zdZ0a3bq3FxDT7w@mail.gmail.com>
2025-11-14 7:14 ` Krzysztof Kozlowski
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=7904826d-043d-4e63-9d38-e0763b3822ba@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel_peng@pegatron.corp-partner.google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).