From: Nikita Travkin <nikita@trvn.ru>
To: Luca Weiss <luca@z3ntu.xyz>
Cc: dmitry.torokhov@gmail.com, ~postmarketos/upstreaming@lists.sr.ht,
robh+dt@kernel.org, Michael.Srba@seznam.cz,
linus.walleij@linaro.org, broonie@kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
phone-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] dt-bindings: input: zinitix: Document touch-keys support
Date: Wed, 27 Oct 2021 23:54:38 +0500 [thread overview]
Message-ID: <351bd499d1326fda5ed9d5c06dce344e@trvn.ru> (raw)
In-Reply-To: <4350691.LvFx2qVVIh@g550jk>
Hi Luca,
Luca Weiss писал(а) 27.10.2021 23:33:
> Hi Nikita,
>
> On Mittwoch, 27. Oktober 2021 20:13:49 CEST Nikita Travkin wrote:
>> In some configrations the touch controller can support the touch-keys.
>> Doucument the linux,keycodes property that enables those keys and
>> specifies the keycodes that should be used to report the key events.
>>
>> Signed-off-by: Nikita Travkin <nikita@trvn.ru>
>> ---
>> .../bindings/input/touchscreen/zinitix,bt400.yaml | 8
>> ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/input/touchscreen/zinitix,bt400.yaml
>> b/Documentation/devicetree/bindings/input/touchscreen/zinitix,bt400.yaml
>> index b4e5ba7c0b49..40b243c07fd4 100644
>> ---
>> a/Documentation/devicetree/bindings/input/touchscreen/zinitix,bt400.yaml
>> +++
>> b/Documentation/devicetree/bindings/input/touchscreen/zinitix,bt400.yaml
>> @@
>> -79,6 +79,14 @@ properties:
>> $ref: /schemas/types.yaml#/definitions/uint32
>> enum: [1, 2]
>>
>> + linux,keycodes:
>> + description: |
>> + This property specifies an array of keycodes assigned to the
>> + touch-keys that can be present in some touchscreen
>> configurations.
>> + $ref: /schemas/input/input.yaml#/properties/linux,keycodes
>> + minItems: 1
>
> I think this would suggest all devices using the driver must have at
> least
> keycode declared which doesn't seem to be the desired behavior?
As I haven't added the property to the "required" list I'd read this as
"If the property is defined it must contain from one to eight elements"
so I think that *technically* the schema is correct. (Otherwise the
dt_schema_check would fail verifying the example) However this indeed
may be true that I could give a better description than "can be present
in some touchscreen configurations."
Thanks,
Nikita
> Regards,
> Luca
>
>> + maxItems: 8
>> +
>> touchscreen-size-x: true
>> touchscreen-size-y: true
>> touchscreen-fuzz-x: true
next prev parent reply other threads:[~2021-10-27 18:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 18:13 [PATCH 0/6] Add touch-keys support to the Zinitix touch driver Nikita Travkin
2021-10-27 18:13 ` [PATCH 1/6] input: touchscreen: zinitix: Make sure the IRQ is allocated before it gets enabled Nikita Travkin
2021-11-09 4:37 ` Linus Walleij
2021-10-27 18:13 ` [PATCH 2/6] dt-bindings: input/ts/zinitix: Convert to YAML, fix and extend Nikita Travkin
2021-11-01 21:39 ` Rob Herring
2021-11-09 4:39 ` Linus Walleij
2021-10-27 18:13 ` [PATCH 3/6] Input: zinitix - Handle proper supply names Nikita Travkin
2021-10-27 18:30 ` Luca Weiss
2021-10-27 18:13 ` [PATCH 4/6] input: touchscreen: zinitix: Add compatible for bt532 Nikita Travkin
2021-11-09 4:41 ` Linus Walleij
2021-10-27 18:13 ` [PATCH 5/6] dt-bindings: input: zinitix: Document touch-keys support Nikita Travkin
2021-10-27 18:33 ` Luca Weiss
2021-10-27 18:54 ` Nikita Travkin [this message]
2021-11-01 21:41 ` Rob Herring
2021-10-27 18:13 ` [PATCH 6/6] input: touchscreen: zinitix: Add touchkey support Nikita Travkin
2021-11-09 4:42 ` Linus Walleij
2021-11-10 6:01 ` kernel test robot
2021-11-09 4:45 ` [PATCH 0/6] Add touch-keys support to the Zinitix touch driver Linus Walleij
2021-11-09 15:23 ` Nikita Travkin
2021-11-11 10:40 ` Linus Walleij
2022-01-04 21:04 ` Linus Walleij
2022-01-05 5:10 ` Nikita Travkin
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=351bd499d1326fda5ed9d5c06dce344e@trvn.ru \
--to=nikita@trvn.ru \
--cc=Michael.Srba@seznam.cz \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®