From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>, robh@kernel.org
Cc: kernel@collabora.com, bleung@chromium.org, groeck@chromium.org,
sjg@chromium.org, dianders@chromium.org,
devicetree@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH v2 1/3] dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema
Date: Sun, 11 Oct 2020 13:17:14 +0200 [thread overview]
Message-ID: <e8111e8b-c599-7ce2-6148-80a9aedb58c9@collabora.com> (raw)
In-Reply-To: <20201008102825.3812-2-ricardo.canuelo@collabora.com>
Hi Ricardo,
Thank you for the patches.
On 8/10/20 12:28, Ricardo Cañuelo wrote:
> Convert the google,cros-ec-i2c-tunnel binding to YAML and add it as a
> property of google,cros-ec.yaml.
>
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Thanks,
Enric
> ---
> .../i2c/google,cros-ec-i2c-tunnel.yaml | 63 +++++++++++++++++++
> .../bindings/i2c/i2c-cros-ec-tunnel.txt | 39 ------------
> .../bindings/mfd/google,cros-ec.yaml | 5 ++
> 3 files changed, 68 insertions(+), 39 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt
>
> diff --git a/Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml b/Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml
> new file mode 100644
> index 000000000000..f83ff67596e6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml
> @@ -0,0 +1,63 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +
> +$id: http://devicetree.org/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: I2C bus that tunnels through the ChromeOS EC (cros-ec)
> +
> +maintainers:
> + - Doug Anderson <dianders@chromium.org>
> + - Benson Leung <bleung@chromium.org>
> + - Enric Balletbo i Serra <enric.balletbo@collabora.com>
> +
> +description: |
> + On some ChromeOS board designs we've got a connection to the EC
> + (embedded controller) but no direct connection to some devices on the
> + other side of the EC (like a battery and PMIC). To get access to
> + those devices we need to tunnel our i2c commands through the EC.
> +
> + The node for this device should be under a cros-ec node like
> + google,cros-ec-spi or google,cros-ec-i2c.
> +
> +properties:
> + compatible:
> + const: google,cros-ec-i2c-tunnel
> +
> + google,remote-bus:
> + description: The EC bus we'd like to talk to.
> + $ref: /schemas/types.yaml#/definitions/uint32
> +
> +required:
> + - compatible
> + - google,remote-bus
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + spi0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cros-ec@0 {
> + compatible = "google,cros-ec-spi";
> + reg = <0>;
> + spi-max-frequency = <5000000>;
> +
> + i2c-tunnel {
> + compatible = "google,cros-ec-i2c-tunnel";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + google,remote-bus = <0>;
> +
> + battery: sbs-battery@b {
> + compatible = "sbs,sbs-battery";
> + reg = <0xb>;
> + sbs,poll-retry-count = <1>;
> + };
> + };
> + };
> + };
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt b/Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt
> deleted file mode 100644
> index 898f030eba62..000000000000
> --- a/Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt
> +++ /dev/null
> @@ -1,39 +0,0 @@
> -I2C bus that tunnels through the ChromeOS EC (cros-ec)
> -======================================================
> -On some ChromeOS board designs we've got a connection to the EC (embedded
> -controller) but no direct connection to some devices on the other side of
> -the EC (like a battery and PMIC). To get access to those devices we need
> -to tunnel our i2c commands through the EC.
> -
> -The node for this device should be under a cros-ec node like google,cros-ec-spi
> -or google,cros-ec-i2c.
> -
> -
> -Required properties:
> -- compatible: google,cros-ec-i2c-tunnel
> -- google,remote-bus: The EC bus we'd like to talk to.
> -
> -Optional child nodes:
> -- One node per I2C device connected to the tunnelled I2C bus.
> -
> -
> -Example:
> - cros-ec@0 {
> - compatible = "google,cros-ec-spi";
> -
> - ...
> -
> - i2c-tunnel {
> - compatible = "google,cros-ec-i2c-tunnel";
> - #address-cells = <1>;
> - #size-cells = <0>;
> -
> - google,remote-bus = <0>;
> -
> - battery: sbs-battery@b {
> - compatible = "sbs,sbs-battery";
> - reg = <0xb>;
> - sbs,poll-retry-count = <1>;
> - };
> - };
> - }
> diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> index f49c0d5d31ad..c45cf30ea3aa 100644
> --- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> +++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> @@ -71,6 +71,11 @@ properties:
> wakeup-source:
> description: Button can wake-up the system.
>
> +patternProperties:
> + "^i2c-tunnel[0-9]*$":
> + type: object
> + $ref: "/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#"
> +
> required:
> - compatible
>
>
next prev parent reply other threads:[~2020-10-11 11:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 10:28 [PATCH v2 0/3] Fix checker warnings related to cros-ec binding Ricardo Cañuelo
2020-10-08 10:28 ` [PATCH v2 1/3] dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema Ricardo Cañuelo
2020-10-11 11:17 ` Enric Balletbo i Serra [this message]
2020-10-08 10:28 ` [PATCH v2 2/3] dt-bindings: input: convert cros-ec-keyb " Ricardo Cañuelo
2020-10-08 18:32 ` Rob Herring
2020-10-09 5:28 ` Ricardo Cañuelo
2020-10-09 13:23 ` Rob Herring
2020-10-08 10:28 ` [PATCH v2 3/3] mfd: google,cros-ec: add missing properties Ricardo Cañuelo
2020-10-08 18:38 ` Rob Herring
2020-10-09 5:48 ` Ricardo Cañuelo
2020-10-09 13:34 ` Rob Herring
2020-10-13 6:46 ` Ricardo Cañuelo
2020-10-14 2:18 ` Tzung-Bi Shih
2020-10-15 6:52 ` Ricardo Cañuelo
2020-10-15 8:25 ` Enric Balletbo i Serra
2020-10-15 9:50 ` Tzung-Bi Shih
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=e8111e8b-c599-7ce2-6148-80a9aedb58c9@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=kernel@collabora.com \
--cc=ricardo.canuelo@collabora.com \
--cc=robh@kernel.org \
--cc=sjg@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).