Based on kernel version 6.11
. Page generated on 2024-09-24 08:21 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 | # 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> 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: description: The EC bus we'd like to talk to. $ref: /schemas/types.yaml#/definitions/uint32 required: - compatible - google,remote-bus unevaluatedProperties: false examples: - | spi { #address-cells = <1>; #size-cells = <0>; cros-ec@0 { compatible = "google,cros-ec-spi"; reg = <0>; spi-max-frequency = <5000000>; interrupts = <99 0>; 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>; }; }; }; }; |