mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-27 13:05:03 +08: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>
31 lines
645 B
Plaintext
31 lines
645 B
Plaintext
ST M41T80 family of RTC and compatible
|
|
|
|
Required properties:
|
|
- compatible: should be one of:
|
|
"st,m41t62",
|
|
"st,m41t65",
|
|
"st,m41t80",
|
|
"st,m41t81",
|
|
"st,m41t81s",
|
|
"st,m41t82",
|
|
"st,m41t83",
|
|
"st,m41t84",
|
|
"st,m41t85",
|
|
"st,m41t87",
|
|
"microcrystal,rv4162",
|
|
- reg: I2C bus address of the device
|
|
|
|
Optional properties:
|
|
- interrupts: rtc alarm interrupt.
|
|
- clock-output-names: From common clock binding to override the default output
|
|
clock name
|
|
- wakeup-source: Enables wake up of host system on alarm
|
|
|
|
Example:
|
|
rtc@68 {
|
|
compatible = "st,m41t80";
|
|
reg = <0x68>;
|
|
interrupt-parent = <&UIC0>;
|
|
interrupts = <0x9 0x8>;
|
|
};
|