All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Charles Wang <charles.goodix@gmail.com>,
	dmitry.torokhov@gmail.com, hbarnor@chromium.org,
	dianders@chromium.org, conor.dooley@microchip.com
Cc: 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: Mon, 21 Oct 2024 11:41:19 +0200	[thread overview]
Message-ID: <89e22cf5-5247-4218-8757-d34253fbfe37@kernel.org> (raw)
In-Reply-To: <ZxMc-HP8o_qHKhKI@ux-UP-WHL01>

On 19/10/2024 04:46, Charles Wang wrote:
>>>>> +  goodix,hid-report-addr:
>>>>> +    $ref: /schemas/types.yaml#/definitions/uint32
>>>>> +    description:
>>>>> +      The register address for retrieving HID report data.
>>>>> +      This address is related to the device firmware and may
>>>>> +      change after a firmware update.
>>>>
> 
>> How is this supposed to work? DTS will stay fixed, you cannot change it
>> just because firmware changed. User loads new firmware with different
>> address, but DTS will have to use old address - so broken property.
>>
> 
> Sorry for missing this issue in my previous response.
> Honestly, although the likelihood of this address changing is low, it is
> indeed possible for it to change due to a firmware update during the factory
> debugging phase. However, for machines that users have, we will ensure that
> this address will not be altered as a result of a firmware upgrade.

Then it feels like property is not really needed - all boards will have
exactly same value.

Best regards,
Krzysztof


  reply	other threads:[~2024-10-21  9:41 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 [this message]
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
  -- 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=89e22cf5-5247-4218-8757-d34253fbfe37@kernel.org \
    --to=krzk@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=charles.goodix@gmail.com \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.