From: Rob Herring <robh@kernel.org>
To: Charles Wang <charles.goodix@gmail.com>
Cc: krzk@kernel.org, hbarnor@chromium.org, dianders@chromium.org,
conor.dooley@microchip.com, dmitry.torokhov@gmail.com,
jikos@kernel.org, bentiss@kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: input: gt7986u-spifw: Remove hid-report-addr property
Date: Fri, 8 Nov 2024 10:13:50 -0600 [thread overview]
Message-ID: <20241108161350.GA2313139-robh@kernel.org> (raw)
In-Reply-To: <20241108120311.87795-3-charles.goodix@gmail.com>
On Fri, Nov 08, 2024 at 08:03:11PM +0800, Charles Wang wrote:
> Since all boards use the same address, drop the goodix,hid-report-addr
> property and hardcode it in the driver as a default value.
Where's the driver change?
I don't see the point in defining this and then removing it in the next
patch.
>
> Signed-off-by: Charles Wang <charles.goodix@gmail.com>
> ---
> .../devicetree/bindings/input/goodix,gt7986u-spifw.yaml | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/goodix,gt7986u-spifw.yaml b/Documentation/devicetree/bindings/input/goodix,gt7986u-spifw.yaml
> index 8105b9ce2..c9e346a60 100644
> --- a/Documentation/devicetree/bindings/input/goodix,gt7986u-spifw.yaml
> +++ b/Documentation/devicetree/bindings/input/goodix,gt7986u-spifw.yaml
> @@ -36,11 +36,6 @@ properties:
> reset-gpios:
> maxItems: 1
>
> - goodix,hid-report-addr:
> - $ref: /schemas/types.yaml#/definitions/uint32
> - description:
> - The register address for retrieving HID report data.
> -
> spi-max-frequency: true
>
> required:
> @@ -48,7 +43,6 @@ required:
> - reg
> - interrupts
> - reset-gpios
> - - goodix,hid-report-addr
Dropping a required property is an ABI break.
A devicetree that passes with the schema will not work on current
kernels that require this property.
>
> unevaluatedProperties: false
>
> @@ -68,7 +62,6 @@ examples:
> interrupts = <25 IRQ_TYPE_LEVEL_LOW>;
> reset-gpios = <&gpio1 1 GPIO_ACTIVE_LOW>;
> spi-max-frequency = <10000000>;
> - goodix,hid-report-addr = <0x22c8c>;
> };
> };
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-11-08 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 12:03 [PATCH v3 0/2] dt-bindings: input: Goodix GT7986U SPI HID Touchscreen Charles Wang
2024-11-08 12:03 ` [PATCH v3 1/2] " Charles Wang
2024-11-08 13:33 ` Rob Herring (Arm)
2024-11-08 15:13 ` Doug Anderson
2024-11-11 3:03 ` Charles Wang
2024-11-08 16:10 ` Rob Herring
2024-11-11 3:07 ` Charles Wang
2024-11-08 12:03 ` [PATCH v3 2/2] dt-bindings: input: gt7986u-spifw: Remove hid-report-addr property Charles Wang
2024-11-08 13:33 ` Rob Herring (Arm)
2024-11-08 16:13 ` Rob Herring [this message]
2024-11-11 3:32 ` Charles Wang
2024-11-08 15:11 ` [PATCH v3 0/2] dt-bindings: input: Goodix GT7986U SPI HID Touchscreen Doug Anderson
2024-11-11 2:22 ` 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=20241108161350.GA2313139-robh@kernel.org \
--to=robh@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=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).