[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a7b384ac-55f4-931b-d8ce-0c74c70f07cd@benettiengineering.com>
Date: Tue, 6 Apr 2021 16:07:20 +0200
From: Giulio Benetti <giulio.benetti@...ettiengineering.com>
To: Jonathan Neuschäfer <j.neuschaefer@....net>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Jonathan Neuschäfer <j.ne@...teo.net>,
Henrik Rydberg <rydberg@...math.org>,
linux-input@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: touchscreen: Add HY46XX bindings
Hi Jonathan,
On 4/6/21 3:37 PM, Jonathan Neuschäfer wrote:
> In the binding:
>> +properties:
>> + compatible:
>> + enum:
>> + - hycon,hycon-hy4613
>> + - hycon,hycon-hy4614
>> + - hycon,hycon-hy4621
>> + - hycon,hycon-hy4623
>> + - hycon,hycon-hy4633
>> + - hycon,hycon-hy4635
>
> In the example:
>> + hycon-hy4633@1c {
>> + compatible = "hycon,hy4633";
>> + reg = <0x1c>;
>> + interrupt-parent = <&gpio2>;
>> + interrupts = <5 IRQ_TYPE_EDGE_FALLING>;
>> + reset-gpios = <&gpio2 6 GPIO_ACTIVE_LOW>;
>> + };
>
>
> Rob's devicetree lint bot detected the mismatch in compatible string
> here.
>
> I personally think 'hycon,hy4633' looks better than 'hycon,hycon-hy4633',
> because it isn't so redundant.
>
Thank you, I've realized it after submitting patches and waited for
other comments. I've already fixed it the way you've pointed.
Kind regards
--
Giulio Benetti
Benetti Engineering sas
> Best regards,
> Jonathan Neuschäfer
>
Powered by blists - more mailing lists