mirror of
https://github.com/torvalds/linux.git
synced 2026-04-21 08:13:56 -04:00
791d3ef2e1
'interrupt-parent' is often documented as part of define bindings, but it is really outside the scope of a device binding. It's never required in a given node as it is often inherited from a parent node. Or it can be implicit if a parent node is an 'interrupt-controller' node. So remove it from all the binding files. Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org>
23 lines
549 B
Plaintext
23 lines
549 B
Plaintext
* ST UVIS25 uv sensor
|
|
|
|
Required properties:
|
|
- compatible: should be "st,uvis25"
|
|
- reg: i2c address of the sensor / spi cs line
|
|
|
|
Optional properties:
|
|
- interrupts: interrupt mapping for IRQ. It should be configured with
|
|
flags IRQ_TYPE_LEVEL_HIGH, IRQ_TYPE_EDGE_RISING, IRQ_TYPE_LEVEL_LOW or
|
|
IRQ_TYPE_EDGE_FALLING.
|
|
|
|
Refer to interrupt-controller/interrupts.txt for generic interrupt
|
|
client node bindings.
|
|
|
|
Example:
|
|
|
|
uvis25@47 {
|
|
compatible = "st,uvis25";
|
|
reg = <0x47>;
|
|
interrupt-parent = <&gpio0>;
|
|
interrupts = <0 IRQ_TYPE_EDGE_RISING>;
|
|
};
|