From: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Raul E Rangel <rrangel@chromium.org>,
devicetree@vger.kernel.org,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Benson Leung <bleung@chromium.org>,
Duncan Laurie <dlaurie@google.com>,
Guenter Roeck <groeck@chromium.org>,
Rob Herring <robh+dt@kernel.org>, Eric Peers <epeers@google.com>,
Furquan Shaikh <furquan@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Bhanu Prakash Maiya <bhanumaiya@chromium.org>,
Rob Herring <robh@kernel.org>
Subject: [PATCH v6 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart"
Date: Fri, 9 Oct 2020 14:01:55 -0700 [thread overview]
Message-ID: <20201009132732.v6.2.I8d7530d8372e4ef298ddaaaad612a2cdd24ed93e@changeid> (raw)
In-Reply-To: <20201009132732.v6.1.Ic98067cd92a0b7fed9cd3dfb7b4e736e76551cda@changeid>
Add DT compatible string in
Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
Signed-off-by: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
---
Changes in v6:
- No change
Changes in v5:
- No change
Changes in v4:
- Changes in commit message.
Changes in v3:
- Rebased changes on google,cros-ec.yaml
Changes in v2:
- No change
Documentation/devicetree/bindings/mfd/google,cros-ec.yaml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
index 6a7279a85ec1c..552d1c9bf3de4 100644
--- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
+++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
@@ -10,11 +10,12 @@ maintainers:
- Benson Leung <bleung@chromium.org>
- Enric Balletbo i Serra <enric.balletbo@collabora.com>
- Guenter Roeck <groeck@chromium.org>
+ - Bhanu Prakash Maiya <bhanumaiya@chromium.org>
description:
Google's ChromeOS EC is a microcontroller which talks to the AP and
implements various functions such as keyboard and battery charging.
- The EC can be connected through various interfaces (I2C, SPI, and others)
+ The EC can be connected through various interfaces (I2C, SPI, UART and others)
and the compatible string specifies which interface is being used.
properties:
@@ -29,6 +30,9 @@ properties:
- description:
For implementations of the EC is connected through RPMSG.
const: google,cros-ec-rpmsg
+ - description:
+ For implementations of the EC is connected through UART.
+ const: google,cros-ec-uart
google,cros-ec-spi-pre-delay:
description:
--
2.26.2
next prev parent reply other threads:[~2020-10-09 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 21:01 [PATCH v6 1/2] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer Bhanu Prakash Maiya
2020-10-09 21:01 ` Bhanu Prakash Maiya [this message]
2020-10-11 11:59 ` [PATCH v6 2/2] dt-bindings: mfd: Add DT compatible string "google,cros_ec_uart" Enric Balletbo i Serra
2020-10-11 16:38 ` Duncan Laurie
[not found] ` <CADv6+0671i_iopx--7gK93=1n1SfJR=uVgJOePVn-NDM5Nqgmg@mail.gmail.com>
2020-10-11 17:11 ` Enric Balletbo i Serra
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=20201009132732.v6.2.I8d7530d8372e4ef298ddaaaad612a2cdd24ed93e@changeid \
--to=bhanumaiya@chromium.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dlaurie@google.com \
--cc=enric.balletbo@collabora.com \
--cc=epeers@google.com \
--cc=furquan@chromium.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).