From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Bhanu Prakash Maiya <bhanumaiya@chromium.org>,
linux-arm-kernel@lists.infradead.org
Cc: Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org,
"Lee Jones )" <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Raul E Rangel <rrangel@chromium.org>,
Furquan Shaikh <furquan@chromium.org>,
Duncan Laurie <dlaurie@google.com>,
Eric Peers <epeers@google.com>,
devicetree@vger.kernel.org,
Bhanu Prakash Maiya <bhanumaiya@google.com>
Subject: Re: [PATCH 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart"
Date: Fri, 26 Jun 2020 10:42:29 +0200 [thread overview]
Message-ID: <8ef4bb35-b2c8-ffdf-cefc-38c0d43d89e9@collabora.com> (raw)
In-Reply-To: <20200625131432.2.Icfeab15fa04daaffc61280faf5a75cd9b23ee822@changeid>
Hi Bhanu,
Thank you for the patch.
On 25/6/20 23:34, Bhanu Prakash Maiya wrote:
> Add DT compatible string in
> Documentation/devicetree/bindings/mfd/cros_ec.txt
>
> Signed-off-by: Bhanu Prakash Maiya <bhanumaiya@google.com>
> ---
>
> Documentation/devicetree/bindings/mfd/cros-ec.txt | 9 +++++++--
txt bindings are somewhat deprecated now, this specific binding was already
converted to the new json-schema, although didn't land yet, you should base your
changes on that, you can pick the following patch:
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20200306085513.76024-1-ikjn@chromium.org/
Also, the kernel test robot, reported a build problem, so fix the problems on
the second version.
Thanks,
Enric
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/cros-ec.txt b/Documentation/devicetree/bindings/mfd/cros-ec.txt
> index 4860eabd0f729..ec8c5d7ecc266 100644
> --- a/Documentation/devicetree/bindings/mfd/cros-ec.txt
> +++ b/Documentation/devicetree/bindings/mfd/cros-ec.txt
> @@ -3,7 +3,7 @@ ChromeOS Embedded Controller
> Google's ChromeOS EC is a Cortex-M device which talks to the AP and
> implements various function such as keyboard and battery charging.
>
> -The EC can be connect through various means (I2C, SPI, LPC, RPMSG) and the
> +The EC can be connect through various means (I2C, SPI, UART, LPC, RPMSG) and the
> compatible string used depends on the interface. Each connection method has
> its own driver which connects to the top level interface-agnostic EC driver.
> Other Linux driver (such as cros-ec-keyb for the matrix keyboard) connect to
> @@ -17,6 +17,10 @@ Required properties (SPI):
> - compatible: "google,cros-ec-spi"
> - reg: SPI chip select
>
> +Required properties (UART):
> +- compatible: "google,cros-ec-uart"
> +- reg: UART baudrate, flowcontrol
> +
> Required properties (RPMSG):
> - compatible: "google,cros-ec-rpmsg"
>
> @@ -72,5 +76,6 @@ spi@131b0000 {
> };
> };
>
> -
> Example for LPC is not supplied as it is not yet implemented.
> +
> +Example for UART is not supplied as it is not yet implemented.
>
next prev parent reply other threads:[~2020-06-26 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 21:34 [PATCH 1/2] cros: platform/chrome: Add cros-ec-uart driver for uart support Bhanu Prakash Maiya
2020-06-25 21:34 ` [PATCH 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart" Bhanu Prakash Maiya
2020-06-26 8:42 ` Enric Balletbo i Serra [this message]
2020-06-26 0:18 ` [PATCH 1/2] cros: platform/chrome: Add cros-ec-uart driver for uart support kernel test robot
2020-06-26 8:33 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2020-07-15 7:41 [PATCH 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart" Bhanu Prakash Maiya
2020-07-15 7:56 ` Greg Kroah-Hartman
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=8ef4bb35-b2c8-ffdf-cefc-38c0d43d89e9@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bhanumaiya@chromium.org \
--cc=bhanumaiya@google.com \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dlaurie@google.com \
--cc=epeers@google.com \
--cc=furquan@chromium.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rrangel@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