From: Krzysztof Kozlowski <krzk@kernel.org>
To: Fabio Baltieri <fabiobaltieri@chromium.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
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.org
Subject: Re: [PATCH v2 2/2] dt-bindings: google,cros-ec-keyb: add use-fn-overlay prop
Date: Mon, 29 Dec 2025 15:59:44 +0100 [thread overview]
Message-ID: <c539aa2a-e9be-40e7-9b75-1723bdaf0a39@kernel.org> (raw)
In-Reply-To: <aVKDJhVuOz-V9tb2@google.com>
On 29/12/2025 14:33, Fabio Baltieri wrote:
> On Mon, Dec 29, 2025 at 01:49:05PM +0100, Krzysztof Kozlowski wrote:
>> On 27/12/2025 16:48, Fabio Baltieri wrote:
>>> On Sat, Dec 27, 2025 at 01:44:26PM +0100, Krzysztof Kozlowski wrote:
>>>>> diff --git a/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml b/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml
>>>>> index fefaaf46a240..437575cdf352 100644
>>>>> --- a/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml
>>>>> +++ b/Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml
>>>>> @@ -44,6 +44,14 @@ 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.
>>>>>
>>>>> + google,use-fn-overlay:
>>>>> + description: |
>>>>> + Use a function key overlay. This allows defining an extra set of codes
>>>>
>>>> What is a function key overlay? Overlays are DT term and therefore are
>>>> not suitable for bindings.
>>>
>>> Ok, guess I can rename it to `use-fn-key` or `use-fn-layer`, open to
>>> suggestions really.
>>
>> Use as Linux should use? Then it's software, so not suitable for DT.
>
> Sorry I'm not sure how I understand the comment, this describes how the
> driver handles a keyboard with Fn keys, the codes are defined in the DT
Exactly. The purpose of DT is not to describe how driver should handle
anything.
See also DTS101 from this year's ELCE.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-29 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 15:22 [PATCH v2 0/2] Input: cros_ec_keyb: add function key support Fabio Baltieri
2025-12-24 15:22 ` [PATCH v2 1/2] Input: cros_ec_keyb - " Fabio Baltieri
2025-12-27 14:24 ` Simon Glass
2025-12-29 16:28 ` Fabio Baltieri
2025-12-24 15:22 ` [PATCH v2 2/2] dt-bindings: google,cros-ec-keyb: add use-fn-overlay prop Fabio Baltieri
2025-12-27 12:44 ` Krzysztof Kozlowski
2025-12-27 15:48 ` Fabio Baltieri
2025-12-29 12:49 ` Krzysztof Kozlowski
2025-12-29 13:33 ` Fabio Baltieri
2025-12-29 14:59 ` Krzysztof Kozlowski [this message]
2025-12-29 15:39 ` Fabio Baltieri
2025-12-30 7:26 ` Krzysztof Kozlowski
2025-12-30 11:42 ` Fabio Baltieri
2025-12-27 12:44 ` Krzysztof Kozlowski
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=c539aa2a-e9be-40e7-9b75-1723bdaf0a39@kernel.org \
--to=krzk@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.org \
--cc=robh@kernel.org \
--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).