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: Fri, 14 Nov 2025 08:14:32 +0100 [thread overview]
Message-ID: <6fed3757-44d0-43f9-b75a-52e1cbab41eb@kernel.org> (raw)
In-Reply-To: <CAAq2-DHouqsbOB75mifXVxQT+jZaho9RBB0zdZ0a3bq3FxDT7w@mail.gmail.com>
On 14/11/2025 07:13, Daniel Peng wrote:
>> On 13/11/2025 11:44, Daniel Peng wrote:
>>> From: Daniel Peng <Daniel_Peng@pegatron.corp-partner.google.com>
>>>
>>> The FocalTech FT8112 touch screen chip same as Ilitek ili2901 controller
>>
>> So keep the device in that binding under enum. No need to create
>> document for every device, even if they were different but here it is
>> pretty obvious - same chip.
>>
>> Best regards,
>> Krzysztof
>
> Sorry for the confusion. Might be I use the wrong description, and make you
> feel that is the same chip and no need to create new binding file.
>
> Here are my question:
> 1. I had referred to ilitek,ili2901.yaml and copied as new file for
> focaltech,ft8112.yaml. Moreover, I also modified to replace related
> information for Focaltech FT8112 touchscreen.
> There are many different descriptions in the file, such as "compatible",
> "reg", "interrupt-parent", "interrupts", "reset-gpios", ... .etc.
> If "No need to create document for every device" now, could you help to
> provide what file that I need to keep the device in the binding under enum?
You wrote it is the same chip as ili2901, so obviously in ili2901.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-11-14 7:14 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
[not found] ` <CAAq2-DHouqsbOB75mifXVxQT+jZaho9RBB0zdZ0a3bq3FxDT7w@mail.gmail.com>
2025-11-14 7:14 ` Krzysztof Kozlowski [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=6fed3757-44d0-43f9-b75a-52e1cbab41eb@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).