diff options
author | Simon Glass <sjg@chromium.org> | 2015-01-27 06:29:37 +0300 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-01-30 03:10:01 +0300 |
commit | 7132b9fd68a1c76bf557d56dd62756a6607cf761 (patch) | |
tree | 01e328c5353ed266cf7b6e22efb7540116f13d64 /doc/device-tree-bindings/i2c | |
parent | 189d80166b31db55b99190be3164c8d3348b57fc (diff) | |
download | u-boot-7132b9fd68a1c76bf557d56dd62756a6607cf761.tar.xz |
dm: i2c: dts: Support an offset-len device tree property
Since U-Boot can support different offset lengths (0-4 bytes), add a device
tree property to specify this. This avoids hard-coding it in the driver.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/device-tree-bindings/i2c')
-rw-r--r-- | doc/device-tree-bindings/i2c/i2c.txt | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/device-tree-bindings/i2c/i2c.txt b/doc/device-tree-bindings/i2c/i2c.txt new file mode 100644 index 0000000000..ea918dd61d --- /dev/null +++ b/doc/device-tree-bindings/i2c/i2c.txt @@ -0,0 +1,28 @@ +U-Boot I2C +---------- + +U-Boot's I2C model has the concept of an offset within a chip (I2C target +device). The offset can be up to 4 bytes long, but is normally 1 byte, +meaning that offsets from 0 to 255 are supported by the chip. This often +corresponds to register numbers. + +Apart from the controller-specific I2C bindings, U-Boot supports a special +property which allows the chip offset length to be selected. + +Optional properties: +- u-boot,i2c-offset-len - length of chip offset in bytes. If omitted the + default value of 1 is used. + + +Example +------- + +i2c4: i2c@12ca0000 { + cros-ec@1e { + reg = <0x1e>; + compatible = "google,cros-ec"; + i2c-max-frequency = <100000>; + u-boot,i2c-offset-len = <0>; + ec-interrupt = <&gpx1 6 GPIO_ACTIVE_LOW>; + }; +}; |