From: Rob Herring <robh@kernel.org>
To: Philip Chen <philipchen@chromium.org>
Cc: devicetree@vger.kernel.org, Guenter Roeck <groeck@chromium.org>,
swboyd@chromium.org, linux-input@vger.kernel.org,
dianders@chromium.org, Simon Glass <sjg@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Benson Leung <bleung@chromium.org>,
dmitry.torokhov@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>
Subject: Re: [PATCH v7 1/2] dt-bindings: input: cros-ec-keyb: Add a new property
Date: Mon, 25 Jan 2021 17:15:40 -0600 [thread overview]
Message-ID: <20210125231540.GA1223505@robh.at.kernel.org> (raw)
In-Reply-To: <20210115122412.v7.1.I025fb861cd5fa0ef5286b7dce514728e9df7ae74@changeid>
On Fri, 15 Jan 2021 12:24:29 -0800, Philip Chen wrote:
> Add a new property `function-row-physmap` to the
> device tree for the custom keyboard top row design.
>
> The property describes the rows/columns of the top row keys
> from left to right.
>
> Signed-off-by: Philip Chen <philipchen@chromium.org>
> ---
>
> Changes in v7:
> - Use MATRIX_KEY macro to describe `function-row-physmap`
>
> Changes in v6:
> - remove $ref and add `function-row-physmap` to the example
>
> Changes in v5:
> - add minItems and maxItems for `function-row-physmap`
>
> Changes in v2:
> - add `function-row-physmap` instead of `google,custom-keyb-top-row`
>
> .../bindings/input/google,cros-ec-keyb.yaml | 24 +++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-01-25 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 20:24 [PATCH v7 1/2] dt-bindings: input: cros-ec-keyb: Add a new property Philip Chen
2021-01-15 20:24 ` [PATCH v7 2/2] Input: cros-ec-keyb - Expose function row physical map to userspace Philip Chen
2021-01-15 20:34 ` Stephen Boyd
2021-02-04 23:58 ` Philip Chen
2021-02-23 5:07 ` Dmitry Torokhov
2021-01-15 20:34 ` [PATCH v7 1/2] dt-bindings: input: cros-ec-keyb: Add a new property Stephen Boyd
2021-01-25 23:15 ` Rob Herring [this message]
2021-02-23 5:07 ` Dmitry Torokhov
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=20210125231540.GA1223505@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-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipchen@chromium.org \
--cc=robh+dt@kernel.org \
--cc=sjg@chromium.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).