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 08:36:08 +0000 [thread overview]
Message-ID: <070f94b5-afe9-4098-8a6c-ae98104f94bb@microchip.com> (raw)
In-Reply-To: <6e703599-0389-435e-b163-55e5a046a8f5@linaro.org>
Hi Krzysztof,
On 08/02/24 12:59 pm, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 08/02/2024 04:59, Dharma.B@microchip.com wrote:
>>>> +
>>>> +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.
>
> Why linux,keycodes? Is the size restricted in any other referenced schema?
Sorry, I misinterpreted the statement "entire property(ies) coming from
input.yaml".
The linux,keycodes size should be restricted to maxitems 8 here.
I will drop only the optional property "autorepeat".
Thanks.
>
> Best regards,
> Krzysztof
>
--
With Best Regards,
Dharma B.
prev parent reply other threads:[~2024-02-08 8:36 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
2024-02-08 7:29 ` Krzysztof Kozlowski
2024-02-08 8:36 ` Dharma.B [this message]
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=070f94b5-afe9-4098-8a6c-ae98104f94bb@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).