From: Rob Herring <robh@kernel.org>
To: Fabio Baltieri <fabiobaltieri@chromium.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Simon Glass <sjg@chromium.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.orga
Subject: Re: [PATCH v1 3/3] dt-bindings: google,cros-ec-keyb: add fn-key and f-keymap props
Date: Tue, 9 Dec 2025 13:22:43 -0600 [thread overview]
Message-ID: <20251209192243.GA963693-robh@kernel.org> (raw)
In-Reply-To: <20251209154706.529784-4-fabiobaltieri@chromium.org>
On Tue, Dec 09, 2025 at 03:47:06PM +0000, Fabio Baltieri wrote:
> Add binding documentation for the fn-key and fn-keymap properties,
> verify that the two new properties are either both preseent or none.
>
> Signed-off-by: Fabio Baltieri <fabiobaltieri@chromium.org>
> ---
> .../bindings/input/google,cros-ec-keyb.yaml | 60 +++++++++++++++----
> 1 file changed, 49 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml b/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml
> index fefaaf46a240..56adf9026010 100644
> --- a/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml
> +++ b/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml
> @@ -44,6 +44,20 @@ properties:
> where the lower 16 bits are reserved. This property is specified only
> when the keyboard has a custom design for the top row keys.
>
> + fn-key:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + An u32 containing the coordinate of the Fn key, use the MATRIX_KEY(row,
> + col, code) macro, code is ignored.
> +
> + fn-keymap:
If keymap is linux,keymap, then this should perhaps be linux,fn-keymap.
Depends if we still think linux,keymap is Linux specific?
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + minItems: 1
> + maxItems: 32
> + description: |
> + An array of u32 mapping the row, column and codes for the function keys,
> + use the MATRIX_KEY macro to define the elements.
> +
> dependencies:
> function-row-physmap: [ 'linux,keymap' ]
> google,needs-ghost-filter: [ 'linux,keymap' ]
> @@ -51,17 +65,28 @@ dependencies:
> required:
> - compatible
>
> -if:
> - properties:
> - compatible:
> - contains:
> - const: google,cros-ec-keyb
> -then:
> - $ref: /schemas/input/matrix-keymap.yaml#
> - required:
> - - keypad,num-rows
> - - keypad,num-columns
> - - linux,keymap
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: google,cros-ec-keyb
> + then:
> + $ref: /schemas/input/matrix-keymap.yaml#
> + required:
> + - keypad,num-rows
> + - keypad,num-columns
> + - linux,keymap
> + - if:
> + anyOf:
> + - required:
> + - fn-key
> + - required:
> + - fn-keymap
> + then:
> + required:
> + - fn-key
> + - fn-keymap
This can be more concisely written as:
dependencies:
fn-key: [fn-keymap]
fn-keymap: [fn-key]
next prev parent reply other threads:[~2025-12-09 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 15:47 [PATCH v1 0/3] Input: cros_ec_keyb: add function key support Fabio Baltieri
2025-12-09 15:47 ` [PATCH v1 1/3] Input: cros_ec_keyb: clarify key event error message Fabio Baltieri
2025-12-11 13:29 ` Simon Glass
2025-12-13 9:40 ` Dmitry Torokhov
2025-12-09 15:47 ` [PATCH v1 2/3] Input: cros_ec_keyb: add function key support Fabio Baltieri
2025-12-11 13:29 ` Simon Glass
2025-12-15 13:09 ` Fabio Baltieri
2025-12-09 15:47 ` [PATCH v1 3/3] dt-bindings: google,cros-ec-keyb: add fn-key and f-keymap props Fabio Baltieri
2025-12-09 17:24 ` Rob Herring (Arm)
2025-12-09 19:22 ` Rob Herring [this message]
2025-12-10 18:00 ` Fabio Baltieri
2025-12-12 4:44 ` Dmitry Torokhov
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=20251209192243.GA963693-robh@kernel.org \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fabiobaltieri@chromium.org \
--cc=groeck@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.orga \
--cc=sjg@chromium.org \
--cc=tzungbi@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).