From: Rob Herring <robh@kernel.org>
To: Philip Chen <philipchen@chromium.org>
Cc: swboyd@chromium.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
dianders@chromium.org, dmitry.torokhov@gmail.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: input: Create macros for cros-ec keymap
Date: Wed, 13 Jan 2021 09:30:33 -0600 [thread overview]
Message-ID: <20210113153033.GA2483483@robh.at.kernel.org> (raw)
In-Reply-To: <20210108172316.v4.1.Iaa8a60cf2ed4b7ad5e2fbb4ad76a1c600ee36113@changeid>
On Fri, 08 Jan 2021 17:23:31 -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>
> ---
>
> (no changes since v2)
>
> Changes in v2:
> - Rename CROS_STD_NON_TOP_ROW_KEYMAP to CROS_STD_MAIN_KEYMAP
>
> include/dt-bindings/input/cros-ec-keyboard.h | 103 +++++++++++++++++++
> 1 file changed, 103 insertions(+)
> create mode 100644 include/dt-bindings/input/cros-ec-keyboard.h
>
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-01-13 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 1:23 [PATCH v4 1/2] dt-bindings: input: Create macros for cros-ec keymap Philip Chen
2021-01-09 1:23 ` [PATCH v4 2/2] ARM: dts: cros-ec-keyboard: Use keymap marcos Philip Chen
2021-01-12 2:07 ` Stephen Boyd
2021-01-12 2:07 ` Stephen Boyd
2021-01-13 22:15 ` Philip Chen
2021-01-12 2:06 ` [PATCH v4 1/2] dt-bindings: input: Create macros for cros-ec keymap Stephen Boyd
2021-01-13 15:30 ` Rob Herring [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=20210113153033.GA2483483@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--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