mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07: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>
26 lines
794 B
Plaintext
26 lines
794 B
Plaintext
* Texas Instruments OPT3001 Ambient Light Sensor
|
|
|
|
The driver supports interrupt-driven and interrupt-less operation, depending
|
|
on whether an interrupt property has been populated into the DT. Note that
|
|
the optional generation of IIO events on rising/falling light threshold changes
|
|
requires the use of interrupts. Without interrupts, only the simple reading
|
|
of the current light value is supported through the IIO API.
|
|
|
|
http://www.ti.com/product/opt3001
|
|
|
|
Required properties:
|
|
- compatible: should be "ti,opt3001"
|
|
- reg: the I2C address of the sensor
|
|
|
|
Optional properties:
|
|
- interrupts: interrupt mapping for GPIO IRQ (configure for falling edge)
|
|
|
|
Example:
|
|
|
|
opt3001@44 {
|
|
compatible = "ti,opt3001";
|
|
reg = <0x44>;
|
|
interrupt-parent = <&gpio1>;
|
|
interrupts = <28 IRQ_TYPE_EDGE_FALLING>;
|
|
};
|