| Simon Glass | f542841 | 2015-01-26 20:29:37 -0700 | [diff] [blame] | 1 | U-Boot I2C |
| 2 | ---------- |
| 3 | |
| 4 | U-Boot's I2C model has the concept of an offset within a chip (I2C target |
| 5 | device). The offset can be up to 4 bytes long, but is normally 1 byte, |
| 6 | meaning that offsets from 0 to 255 are supported by the chip. This often |
| 7 | corresponds to register numbers. |
| 8 | |
| 9 | Apart from the controller-specific I2C bindings, U-Boot supports a special |
| 10 | property which allows the chip offset length to be selected. |
| 11 | |
| 12 | Optional properties: |
| 13 | - u-boot,i2c-offset-len - length of chip offset in bytes. If omitted the |
| 14 | default value of 1 is used. |
| 15 | |
| 16 | |
| 17 | Example |
| 18 | ------- |
| 19 | |
| 20 | i2c4: i2c@12ca0000 { |
| 21 | cros-ec@1e { |
| 22 | reg = <0x1e>; |
| 23 | compatible = "google,cros-ec"; |
| 24 | i2c-max-frequency = <100000>; |
| 25 | u-boot,i2c-offset-len = <0>; |
| 26 | ec-interrupt = <&gpx1 6 GPIO_ACTIVE_LOW>; |
| 27 | }; |
| 28 | }; |