i2c.txt 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. Generic device tree bindings for I2C busses
  2. ===========================================
  3. This document describes generic bindings which can be used to describe I2C
  4. busses in a device tree.
  5. Required properties
  6. -------------------
  7. - #address-cells - should be <1>. Read more about addresses below.
  8. - #size-cells - should be <0>.
  9. - compatible - name of I2C bus controller following generic names
  10. recommended practice.
  11. For other required properties e.g. to describe register sets,
  12. clocks, etc. check the binding documentation of the specific driver.
  13. The cells properties above define that an address of children of an I2C bus
  14. are described by a single value. This is usually a 7 bit address. However,
  15. flags can be attached to the address. I2C_TEN_BIT_ADDRESS is used to mark a 10
  16. bit address. It is needed to avoid the ambiguity between e.g. a 7 bit address
  17. of 0x50 and a 10 bit address of 0x050 which, in theory, can be on the same bus.
  18. Another flag is I2C_OWN_SLAVE_ADDRESS to mark addresses on which we listen to
  19. be devices ourselves.
  20. Optional properties
  21. -------------------
  22. These properties may not be supported by all drivers. However, if a driver
  23. wants to support one of the below features, it should adapt the bindings below.
  24. - clock-frequency - frequency of bus clock in Hz.
  25. - wakeup-source - device can be used as a wakeup source.
  26. - interrupts - interrupts used by the device.
  27. - interrupt-names - "irq" and "wakeup" names are recognized by I2C core,
  28. other names are left to individual drivers.
  29. Binding may contain optional "interrupts" property, describing interrupts
  30. used by the device. I2C core will assign "irq" interrupt (or the very first
  31. interrupt if not using interrupt names) as primary interrupt for the slave.
  32. Also, if device is marked as a wakeup source, I2C core will set up "wakeup"
  33. interrupt for the device. If "wakeup" interrupt name is not present in the
  34. binding, then primary interrupt will be used as wakeup interrupt.