From: Charles Wang <charles.goodix@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: krzk@kernel.org, dmitry.torokhov@gmail.com, hbarnor@chromium.org,
conor.dooley@microchip.com, jikos@kernel.org, bentiss@kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: input: Goodix SPI HID Touchscreen
Date: Sat, 19 Oct 2024 10:55:55 +0800 [thread overview]
Message-ID: <ZxMfu4yxk961mZWB@ux-UP-WHL01> (raw)
In-Reply-To: <CAD=FV=UFrk4QCxWzV9zUZnjhwiFf22Fji5KH83svdwba2mPVBA@mail.gmail.com>
Hi Doug
On Fri, Oct 18, 2024 at 01:48:56PM -0700, Doug Anderson wrote:
>
> On Thu, Oct 17, 2024 at 7:09 PM Charles Wang <charles.goodix@gmail.com> wrote:
> >
> > The Goodix GT7986U touch controller report touch data according to the
> > HID protocol through the SPI bus. However, it is incompatible with
> > Microsoft's HID-over-SPI protocol.
> >
> > Signed-off-by: Charles Wang <charles.goodix@gmail.com>
> > ---
> > .../bindings/input/goodix,gt7375p.yaml | 68 ++++++++++++++++---
> > 1 file changed, 58 insertions(+), 10 deletions(-)
>
> I'm happy to let device tree folks make the call here, but IMO it
> would be much cleaner to just consider the I2C-connected GT7986U and
> the SPI-connected GT7986U to be different things and just use a
> different compatible string for them. So essentially go back to your
> v7 patch from before [1] but change the compatible to
> "goodix,gt7986u-spi". If, for instance, this device also had a USB
> interface then I don't think we'd try to cram it into the same
> bindings even though the same physical chip was present...
>
Honestly, I agree with this approach, but Krzysztof seems to prefer
extending the existing binding.
Best regards,
Charles
next prev parent reply other threads:[~2024-10-19 2:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 2:08 [PATCH] dt-bindings: input: Goodix SPI HID Touchscreen Charles Wang
2024-10-18 5:59 ` Krzysztof Kozlowski
2024-10-18 11:18 ` Charles Wang
2024-10-18 11:41 ` Krzysztof Kozlowski
2024-10-19 2:46 ` Charles Wang
2024-10-21 9:41 ` Krzysztof Kozlowski
2024-10-18 20:48 ` Doug Anderson
2024-10-19 2:55 ` Charles Wang [this message]
2024-10-21 9:43 ` Krzysztof Kozlowski
2024-10-21 15:37 ` Doug Anderson
2024-10-22 7:19 ` Charles Wang
2024-10-22 16:12 ` Doug Anderson
2024-10-23 6:44 ` Charles Wang
2024-10-23 19:35 ` Doug Anderson
2024-10-25 11:33 ` Charles Wang
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 11:46 Charles Wang
2024-10-25 12:03 ` Krzysztof Kozlowski
2024-10-25 15:29 ` Doug Anderson
2024-10-25 15:58 ` Rob Herring
2024-10-25 16:19 ` Doug Anderson
2024-10-25 17:14 ` Dmitry Torokhov
2024-10-30 7:05 ` Charles Wang
2024-10-28 7:17 ` Krzysztof Kozlowski
2024-10-30 6:57 ` Charles Wang
2024-10-30 18:14 ` Doug Anderson
2024-10-31 7:11 ` Charles Wang
2024-10-30 4:34 ` Charles Wang
2024-10-31 2:37 ` Charles Wang
2024-10-31 17:58 ` Doug Anderson
2024-11-01 1:32 ` Charles Wang
2024-11-04 19:36 ` Doug Anderson
2024-11-06 3:20 ` Charles Wang
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=ZxMfu4yxk961mZWB@ux-UP-WHL01 \
--to=charles.goodix@gmail.com \
--cc=bentiss@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hbarnor@chromium.org \
--cc=jikos@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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