linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Dharma.B@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <dmitry.torokhov@gmail.com>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<conor+dt@kernel.org>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>, <claudiu.beznea@tuxon.dev>,
	<linux-input@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: input: atmel,captouch: convert bindings to YAML
Date: Thu, 8 Feb 2024 03:59:55 +0000	[thread overview]
Message-ID: <09c25824-f56b-4598-b8cc-1df992812754@microchip.com> (raw)
In-Reply-To: <982e81db-3bf9-49e9-b57f-a91612d62f5c@linaro.org>

Hi Krzysztof,

On 07/02/24 8:45 pm, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 07/02/2024 10:08, Dharma Balasubiramani wrote:
>> Convert the Atmel capacitive touchscreen bindings to YAML format.
>>
>> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.co
> 
> Thank you for your patch. There is something to discuss/improve.
> 
>> +
>> +properties:
>> +  compatible:
>> +    const: atmel,captouch
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  interrupts:
>> +    maxItems: 1
>> +
>> +  linux,keycodes:
>> +    minItems: 1
>> +    maxItems: 8
>> +
>> +  autorepeat:
>> +    type: boolean
> 
> You can drop entire property, coming from input.yaml.

Sure, I will drop the 'linux,keycodes' and 'autorepeat' properties.
> 
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - interrupts
>> +  - linux,keycodes
>> +
>> +additionalProperties: false
> 
> Instead:
> unevaluatedProperties: false

Noted, Thanks.
> 
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/interrupt-controller/irq.h>
>> +    #include <dt-bindings/input/linux-event-codes.h>
>> +    i2c {
>> +      #address-cells = <1>;
>> +      #size-cells = <0>;
>> +      atmel-captouch@51 {
> 
> Instead:
> touchscreen? touchpad? if none of these, then just "touch@51"

I will go with touch@51.

Thanks.
> 
>> +        compatible = "atmel,captouch";
>> +        reg = <0x51>;
> 
> 
> Best regards,
> Krzysztof
> 

-- 
With Best Regards,
Dharma B.


  reply	other threads:[~2024-02-08  4:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  9:08 [PATCH] dt-bindings: input: atmel,captouch: convert bindings to YAML Dharma Balasubiramani
2024-02-07 15:15 ` Krzysztof Kozlowski
2024-02-08  3:59   ` Dharma.B [this message]
2024-02-08  7:29     ` Krzysztof Kozlowski
2024-02-08  8:36       ` Dharma.B

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=09c25824-f56b-4598-b8cc-1df992812754@microchip.com \
    --to=dharma.b@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).