Path: blob/master/Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml
26307 views
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)1%YAML 1.22---34$id: http://devicetree.org/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#5$schema: http://devicetree.org/meta-schemas/core.yaml#67title: I2C bus that tunnels through the ChromeOS EC (cros-ec)89maintainers:10- Doug Anderson <dianders@chromium.org>11- Benson Leung <bleung@chromium.org>1213description: |14On some ChromeOS board designs we've got a connection to the EC15(embedded controller) but no direct connection to some devices on the16other side of the EC (like a battery and PMIC). To get access to17those devices we need to tunnel our i2c commands through the EC.1819The node for this device should be under a cros-ec node like20google,cros-ec-spi or google,cros-ec-i2c.2122allOf:23- $ref: /schemas/i2c/i2c-controller.yaml#2425properties:26compatible:27const: google,cros-ec-i2c-tunnel2829google,remote-bus:30description: The EC bus we'd like to talk to.31$ref: /schemas/types.yaml#/definitions/uint323233required:34- compatible35- google,remote-bus3637unevaluatedProperties: false3839examples:40- |41spi {42#address-cells = <1>;43#size-cells = <0>;4445cros-ec@0 {46compatible = "google,cros-ec-spi";47reg = <0>;48spi-max-frequency = <5000000>;49interrupts = <99 0>;5051i2c-tunnel {52compatible = "google,cros-ec-i2c-tunnel";53#address-cells = <1>;54#size-cells = <0>;5556google,remote-bus = <0>;5758battery: sbs-battery@b {59compatible = "sbs,sbs-battery";60reg = <0xb>;61sbs,poll-retry-count = <1>;62};63};64};65};666768