From: Charles Wang <charles.goodix@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Krzysztof Kozlowski <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: Fri, 1 Nov 2024 09:32:52 +0800 [thread overview]
Message-ID: <ZyQvxKi8dYOv1AOg@ux-UP-WHL01> (raw)
In-Reply-To: <CAD=FV=UNKECLn=3VrjsJfA+HTNa9Gag1qw5jOcBvw7=ZtkZEnw@mail.gmail.com>
Hi Doug,
On Thu, Oct 31, 2024 at 10:58:07AM -0700, Doug Anderson wrote:
> Hi,
>
> On Wed, Oct 30, 2024 at 7:37 PM Charles Wang <charles.goodix@gmail.com> wrote:
> >
> > > > + goodix,hid-report-addr:
> > >
> > > I do not see this patch addressing previous review. Sending something
> > > like this as v1 after long discussions also does not help.
> > >
> > > No, you keep sending the same and the same, without improvements.
> > >
> >
> > I apologize for overlooking the discussions regarding this issue.
> >
> > I would like to clarify that while the current boards use the same address,
> > but newly designed boards in the future may require different addresses.
> >
> > Retaining this property would likely offer more flexibility.
>
> I don't feel very strongly about it, but maybe Krzysztof does?
> Possibly the path of least resistance would be:
>
> 1. You drop the property from the bindings.
>
> 2. You hardcode it in the driver to be the normal value.
>
> 3. If/when someone actually needs a different value then we can add it
> as an optional property in the bindings and fall back to the default
> value if the property isn't present.
>
> What do you think? If you feel strongly about keeping the
> "hid-report-addr" then you can certainly keep making your case.
> However, it's probably best to wait to get agreement from Krzysztof
> (or one of the other DT maintainers) before sending your next version
> unless you're going to take the "path of least resistance" that I talk
> about above.
>
Agreed, let's wait and see the opinions of Krzysztof (or the other DT
maintainers).
Thanks,
Charles
next prev parent reply other threads:[~2024-11-01 1:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 11:46 [PATCH] dt-bindings: input: Goodix SPI HID Touchscreen 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 [this message]
2024-11-04 19:36 ` Doug Anderson
2024-11-06 3:20 ` Charles Wang
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 2:08 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
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
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=ZyQvxKi8dYOv1AOg@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;
as well as URLs for NNTP newsgroup(s).