Hi Dafna, cc'ing Wolfram and linux-i2c ML Missatge de Dafna Hirschfeld <dafna.hirschfeld@xxxxxxxxxxxxx> del dia dj., 27 de febr. 2020 a les 15:58: > > Convert the binding file i2c-cros-ec-tunnel.txt to yaml format. > > This was tested and verified on ARM and ARM64 with: > > make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml > make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml > > Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@xxxxxxxxxxxxx> >From my side: Reviewed-by: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx> We still need Rob's review and as this is a driver in the I2C subsystem I assume this should go through the Wolfram's tree (note that was not cc'ied, it is now). I can also pick the patch through platform-chrome tree if Wolfram is fine. Thanks, Enric > --- > Changes since v1: > - changing the subject to start with "dt-bindings: i2c: cros-ec-tunnel:" > - changing the license to (GPL-2.0-only OR BSD-2-Clause) > - removing "Guenter Roeck <groeck@xxxxxxxxxxxx>" from the maintainers list > - adding ref: /schemas/i2c/i2c-controller.yaml > > Changes since v2: > - adding another patch that fixes a warning found by this patch > > Changes since v3: > - In the example, change sbs-battery@b to battery@b > > Changes since v4: > - change the name of the yaml file to google,cros-ec-i2c-tunnel.yaml > - make the example more complete by adding spi0 as parent and other properties. > > .../i2c/google,cros-ec-i2c-tunnel.yaml | 69 +++++++++++++++++++ > .../bindings/i2c/i2c-cros-ec-tunnel.txt | 39 ----------- > 2 files changed, 69 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..e26c9fc3e33f > --- /dev/null > +++ b/Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml > @@ -0,0 +1,69 @@ > +# SPDX-License-Identifier: (GPL-2.0-only 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: > + - Benson Leung <bleung@xxxxxxxxxxxx> > + - Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx> > + > +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. > + > +allOf: > + - $ref: /schemas/i2c/i2c-controller.yaml# > + > +properties: > + compatible: > + const: > + google,cros-ec-i2c-tunnel > + > + google,remote-bus: > + $ref: "/schemas/types.yaml#/definitions/uint32" > + description: The EC bus we'd like to talk to. > + > + "#address-cells": true > + "#size-cells": true > + > +patternProperties: > + "^.*@[0-9a-f]+$": > + type: object > + description: One node per I2C device connected to the tunnelled I2C bus. > + > +additionalProperties: false > + > +required: > + - compatible > + - google,remote-bus > + > +examples: > + - | > + spi0 { > + #address-cells = <1>; > + #size-cells = <0>; > + cros-ec@0 { > + compatible = "google,cros-ec-spi"; > + reg = <0>; > + > + i2c-tunnel { > + compatible = "google,cros-ec-i2c-tunnel"; > + #address-cells = <1>; > + #size-cells = <0>; > + google,remote-bus = <0>; > + > + battery: 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>; > - }; > - }; > - } > -- > 2.17.1 >
