From: Stephen Boyd <swboyd@chromium.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
chrome-platform@lists.linux.dev,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
"Joseph S. Barrera III" <joebar@chromium.org>
Subject: [PATCH v2 0/2] Input: cros-ec-keyb: Better matrixless support
Date: Fri, 29 Apr 2022 16:31:10 -0700 [thread overview]
Message-ID: <20220429233112.2851665-1-swboyd@chromium.org> (raw)
This is a followup to my previous patch[1] that skips keyboard registration
when the matrix properties aren't present. This adds a compatible string
for this scenario so we can ease existing DTBs over to the new design.
Changes from v1 (https://lore.kernel.org/r/20220427203026.828183-1-swboyd@chromium.org):
* Better enforcement of properties in DT binding
* Skip registration by means of adding compatible to device id list
Stephen Boyd (2):
dt-bindings: google,cros-ec-keyb: Introduce switches only compatible
Input: cros-ec-keyb - skip keyboard registration for switches
compatible
.../bindings/input/google,cros-ec-keyb.yaml | 95 +++++++++++++++++--
drivers/input/keyboard/cros_ec_keyb.c | 15 ++-
2 files changed, 102 insertions(+), 8 deletions(-)
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>
Cc: Benson Leung <bleung@chromium.org>
Cc: Guenter Roeck <groeck@chromium.org>
Cc: Douglas Anderson <dianders@chromium.org>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>
Cc: "Joseph S. Barrera III" <joebar@chromium.org>
[1] https://lore.kernel.org/all/20220425210726.3813477-1-swboyd@chromium.org/
base-commit: 4352e23a7ff2f8a4ff229dd1283ed2f2b708ec51
--
https://chromeos.dev
next reply other threads:[~2022-04-29 23:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 23:31 Stephen Boyd [this message]
2022-04-29 23:31 ` [PATCH v2 1/2] dt-bindings: google,cros-ec-keyb: Introduce switches only compatible Stephen Boyd
2022-05-02 17:00 ` Doug Anderson
2022-05-02 17:43 ` Dmitry Torokhov
2022-05-02 20:41 ` Stephen Boyd
2022-05-02 23:49 ` Stephen Boyd
2022-05-03 1:09 ` Doug Anderson
2022-05-12 10:22 ` Dmitry Torokhov
2022-05-12 18:58 ` Stephen Boyd
2022-05-12 20:11 ` Stephen Boyd
2022-05-12 23:31 ` Dmitry Torokhov
2022-05-12 23:46 ` Stephen Boyd
2022-05-12 23:53 ` Stephen Boyd
2022-05-13 19:07 ` Dmitry Torokhov
2022-04-29 23:31 ` [PATCH v2 2/2] Input: cros-ec-keyb - skip keyboard registration for switches compatible Stephen Boyd
2022-05-02 17:02 ` Doug Anderson
2022-05-02 22:02 ` Stephen Boyd
2022-05-03 1:06 ` Doug Anderson
2022-05-03 2:18 ` Stephen Boyd
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=20220429233112.2851665-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=hsinyi@chromium.org \
--cc=joebar@chromium.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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).