From: Krzysztof Kozlowski <krzk@kernel.org>
To: Charles Wang <charles.goodix@gmail.com>
Cc: jikos@kernel.org, bentiss@kernel.org, hbarnor@chromium.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v8 2/2] dt-bindings: input: Goodix SPI HID Touchscreen
Date: Mon, 30 Sep 2024 08:42:22 +0200 [thread overview]
Message-ID: <8d5ff5c7-1f66-4a1b-a235-868d13afe03e@kernel.org> (raw)
In-Reply-To: <ZvoZbWQx5BfMI_Cd@ux-UP-WHL01>
On 30/09/2024 05:22, Charles Wang wrote:
> Hi Krzysztof,
> Thank you very much for your advice.
>
> On Thu, Sep 26, 2024 at 02:32:05PM +0200, Krzysztof Kozlowski wrote:
>> On 26/09/2024 11:57, Charles Wang wrote:
>>>>> 1 file changed, 71 insertions(+)
>>>>> create mode 100644 Documentation/devicetree/bindings/input/goodix,gt7986u.yaml
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/input/goodix,gt7986u.yaml b/Documentation/devicetree/bindings/input/goodix,gt7986u.yaml
>>>>> new file mode 100644
>>>>> index 000000000..849117639
>>>>> --- /dev/null
>>>>> +++ b/Documentation/devicetree/bindings/input/goodix,gt7986u.yaml
>>>>> @@ -0,0 +1,71 @@
>>>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>>>> +%YAML 1.2
>>>>> +---
>>>>> +$id: http://devicetree.org/schemas/input/goodix,gt7986u.yaml#
>>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>>> +
>>>>> +title: GOODIX GT7986U SPI HID Touchscreen
>>>>> +
>>>>> +maintainers:
>>>>> + - Charles Wang <charles.goodix@gmail.com>
>>>>> +
>>>>> +description: Supports the Goodix GT7986U touchscreen.
>>>>> + This touch controller reports data packaged according to the HID protocol,
>>>>> + but is incompatible with Microsoft's HID-over-SPI protocol.
>>>>> +
>>>>> +allOf:
>>>>> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
>>>>> +
>>>>> +properties:
>>>>> + compatible:
>>>>> + enum:
>>>>> + - goodix,gt7986u-spi
>>>>
>>>> NAK, you duplicate again the binding. You cannot have bus-flavors.
>>>> Device is the same.
>>>>
>>>
>>> Could you provide some suggestions regarding this issue?
>>
>> What is exactly the question or problem? There is a binding for this
>> device. Extend it with SPI parts, e.g.
>> https://elixir.bootlin.com/linux/v6.4-rc7/source/Documentation/devicetree/bindings/iio/accel/adi,adxl313.yaml#L22
>>
>
> This seems a little different from the adxl313.yaml.
Hm? I am reading below:
>
> The issue we're encountering involves the chip model gt7986u,
> which supports both I2C and SPI interfaces. For the I2C interface
> (using the HID-over-I2C driver), it has already been declared in
> the goodix,gt7375p.yaml file as follows:
>
> i2c {
> #address-cells = <1>;
> #size-cells = <0>;
>
> ap_ts: touchscreen@5d {
> compatible = "goodix,gt7986u";
> }
> }
>
> Currently, our design requires utilizing the SPI interface with
> a custom SPI driver. However, the declarations within the binding
> file have led to conflicts, as shown here:
>
> spi {
> #address-cells = <1>;
> #size-cells = <0>;
>
> touchscreen@0 {
> compatible = "goodix,gt7986u";
> }
> }
>
> Should I consider merging both YAML files into a single one to fix this?
And there is no difference. I don't understand the problem.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-30 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 4:42 [PATCH v8 0/2] HID: add initial support for Goodix HID-over-SPI touchscreen Charles Wang
2024-09-26 4:42 ` [PATCH v8 1/2] HID: hid-goodix: Add Goodix HID-over-SPI driver Charles Wang
2024-09-26 4:42 ` [PATCH v8 2/2] dt-bindings: input: Goodix SPI HID Touchscreen Charles Wang
2024-09-26 6:29 ` Krzysztof Kozlowski
2024-09-26 9:57 ` Charles Wang
2024-09-26 12:32 ` Krzysztof Kozlowski
2024-09-30 3:22 ` Charles Wang
2024-09-30 6:42 ` Krzysztof Kozlowski [this message]
2024-09-30 7:56 ` Charles Wang
2024-09-30 8:08 ` Krzysztof Kozlowski
2024-10-08 8:18 ` Charles Wang
2024-09-26 11:13 ` Conor Dooley
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=8d5ff5c7-1f66-4a1b-a235-868d13afe03e@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=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 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).