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>
29 lines
831 B
Plaintext
29 lines
831 B
Plaintext
Maxim MAX30100 heart rate and pulse oximeter sensor
|
|
|
|
* https://datasheets.maximintegrated.com/en/ds/MAX30100.pdf
|
|
|
|
Required properties:
|
|
- compatible: must be "maxim,max30100"
|
|
- reg: the I2C address of the sensor
|
|
- interrupts: the sole interrupt generated by the device
|
|
|
|
Refer to interrupt-controller/interrupts.txt for generic
|
|
interrupt client node bindings.
|
|
|
|
Optional properties:
|
|
- maxim,led-current-microamp: configuration for LED current in microamperes
|
|
while the engine is running. First indexed value is the configuration for
|
|
the RED LED, and second value is for the IR LED.
|
|
|
|
Refer to the datasheet for the allowed current values.
|
|
|
|
Example:
|
|
|
|
max30100@57 {
|
|
compatible = "maxim,max30100";
|
|
reg = <0x57>;
|
|
maxim,led-current-microamp = <24000 50000>;
|
|
interrupt-parent = <&gpio1>;
|
|
interrupts = <16 2>;
|
|
};
|