i2c: allow specifying separate wakeup interrupt in device tree

[cascardo/linux.git] / Documentation / devicetree / bindings / i2c / i2c.txt

diff --git a/Documentation/devicetree/bindings/i2c/i2c.txt b/Documentation/devicetree/bindings/i2c/i2c.txt
index 1175efe..8a99150 100644 (file)
--- a/Documentation/devicetree/bindings/i2c/i2c.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c.txt
@@ -12,7 +12,7 @@ Required properties
 - compatible      - name of I2C bus controller following generic names
                    recommended practice.
 
 - compatible      - name of I2C bus controller following generic names
                    recommended practice.
 

-For other required properties e.g. to describe register sets, interrupts,
+For other required properties e.g. to describe register sets,

 clocks, etc. check the binding documentation of the specific driver.
 
 The cells properties above define that an address of children of an I2C bus
 clocks, etc. check the binding documentation of the specific driver.
 
 The cells properties above define that an address of children of an I2C bus


@@ -29,5 +29,17 @@ Optional properties
 These properties may not be supported by all drivers. However, if a driver
 wants to support one of the below features, it should adapt the bindings below.
 
 These properties may not be supported by all drivers. However, if a driver
 wants to support one of the below features, it should adapt the bindings below.
 

-- clock-frequency      - frequency of bus clock in Hz
+- clock-frequency      - frequency of bus clock in Hz.

 - wakeup-source                - device can be used as a wakeup source.
 - wakeup-source                - device can be used as a wakeup source.

+
+- interrupts           - interrupts used by the device.
+- interrupt-names      - "irq" and "wakeup" names are recognized by I2C core,
+                         other names are left to individual drivers.
+
+Binding may contain optional "interrupts" property, describing interrupts
+used by the device. I2C core will assign "irq" interrupt (or the very first
+interrupt if not using interrupt names) as primary interrupt for the slave.
+
+Also, if device is marked as a wakeup source, I2C core will set up "wakeup"
+interrupt for the device. If "wakeup" interrupt name is not present in the
+binding, then primary interrupt will be used as wakeup interrupt.