|
| 1 | +Invensense MPU-3050 Gyroscope device tree bindings |
| 2 | + |
| 3 | +Required properties: |
| 4 | + - compatible : should be "invensense,mpu3050" |
| 5 | + - reg : the I2C address of the sensor |
| 6 | + |
| 7 | +Optional properties: |
| 8 | + - interrupt-parent : should be the phandle for the interrupt controller |
| 9 | + - interrupts : interrupt mapping for the trigger interrupt from the |
| 10 | + internal oscillator. The following IRQ modes are supported: |
| 11 | + IRQ_TYPE_EDGE_RISING, IRQ_TYPE_EDGE_FALLING, IRQ_TYPE_LEVEL_HIGH and |
| 12 | + IRQ_TYPE_LEVEL_LOW. The driver should detect and configure the hardware |
| 13 | + for the desired interrupt type. |
| 14 | + - vdd-supply : supply regulator for the main power voltage. |
| 15 | + - vlogic-supply : supply regulator for the signal voltage. |
| 16 | + - mount-matrix : see iio/mount-matrix.txt |
| 17 | + |
| 18 | +Optional subnodes: |
| 19 | + - The MPU-3050 will pass through and forward the I2C signals from the |
| 20 | + incoming I2C bus, alternatively drive traffic to a slave device (usually |
| 21 | + an accelerometer) on its own initiative. Therefore is supports a subnode |
| 22 | + i2c gate node. For details see: i2c/i2c-gate.txt |
| 23 | + |
| 24 | +Example: |
| 25 | + |
| 26 | +mpu3050@68 { |
| 27 | + compatible = "invensense,mpu3050"; |
| 28 | + reg = <0x68>; |
| 29 | + interrupt-parent = <&foo>; |
| 30 | + interrupts = <12 IRQ_TYPE_EDGE_FALLING>; |
| 31 | + vdd-supply = <&bar>; |
| 32 | + vlogic-supply = <&baz>; |
| 33 | + |
| 34 | + /* External I2C interface */ |
| 35 | + i2c-gate { |
| 36 | + #address-cells = <1>; |
| 37 | + #size-cells = <0>; |
| 38 | + |
| 39 | + fnord@18 { |
| 40 | + compatible = "fnord"; |
| 41 | + reg = <0x18>; |
| 42 | + interrupt-parent = <&foo>; |
| 43 | + interrupts = <13 IRQ_TYPE_EDGE_FALLING>; |
| 44 | + }; |
| 45 | + }; |
| 46 | +}; |
0 commit comments