[<prev] [next>] [day] [month] [year] [list]
Message-ID: <aTm1PVLrS7Ra0OTF@google.com>
Date: Wed, 10 Dec 2025 18:00:29 +0000
From: Fabio Baltieri <fabiobaltieri@...omium.org>
To: Rob Herring <robh@...nel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Benson Leung <bleung@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Tzung-Bi Shih <tzungbi@...nel.org>, Simon Glass <sjg@...omium.org>,
linux-input@...r.kernel.org, devicetree@...r.kernel.org,
chrome-platform@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 3/3] dt-bindings: google,cros-ec-keyb: add fn-key and
f-keymap props
Hey Rob, thanks for the review.
On Tue, Dec 09, 2025 at 01:22:43PM -0600, Rob Herring wrote:
> On Tue, Dec 09, 2025 at 03:47:06PM +0000, Fabio Baltieri wrote:
> > + 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?
I'm open for suggestions, trying to understand the pattern, these are
specific to this binding I think if anything they should be
google,fn-key and google,fn-keymap, similarly to the existing
google,needs-ghost-filter -- no idea why function-row-physmap was not
prefixed but I guess it slipped in and now it's not worth changing it.
Would it make sense?
Thanks,
Fabio
--
Fabio Baltieri
Powered by blists - more mailing lists