From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Philip Chen <philipchen@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
swboyd@chromium.org, dianders@chromium.org,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/3] dt-bindings: input: Create macros for cros-ec keymap
Date: Mon, 22 Feb 2021 21:39:14 -0800 [thread overview]
Message-ID: <YDSVAt9vxL5fYKhH@google.com> (raw)
In-Reply-To: <20210115143555.v6.1.Iaa8a60cf2ed4b7ad5e2fbb4ad76a1c600ee36113@changeid>
On Fri, Jan 15, 2021 at 02:36:15PM -0800, Philip Chen wrote:
> In Chrome OS, the keyboard matrix can be split to two groups:
>
> The keymap for the top row keys can be customized based on OEM
> preference, while the keymap for the other keys is generic/fixed
> across boards.
>
> This patch creates marcos for the keymaps of these two groups, making
> it easier to reuse the generic portion of keymap when we override the
> keymap in the board-specific dts for custom top row design.
>
> Signed-off-by: Philip Chen <philipchen@chromium.org>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2021-02-23 5:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 22:36 [PATCH v6 1/3] dt-bindings: input: Create macros for cros-ec keymap Philip Chen
2021-01-15 22:36 ` [PATCH v6 2/3] ARM: dts: cros-ec-keyboard: Use keymap macros Philip Chen
2021-01-15 22:38 ` Stephen Boyd
2021-02-23 5:39 ` Dmitry Torokhov
2021-01-15 22:36 ` [PATCH v6 3/3] dt-bindings: input: Fix the keymap for LOCK key Philip Chen
2021-01-15 22:39 ` Stephen Boyd
2021-02-04 23:59 ` Philip Chen
2021-02-05 21:13 ` Rob Herring
2021-02-23 5:39 ` Dmitry Torokhov
2021-01-15 22:38 ` [PATCH v6 1/3] dt-bindings: input: Create macros for cros-ec keymap Stephen Boyd
2021-01-15 22:59 ` Philip Chen
2021-01-20 15:49 ` Rob Herring
2021-02-23 5:39 ` Dmitry Torokhov [this message]
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=YDSVAt9vxL5fYKhH@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipchen@chromium.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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).