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>
28 lines
810 B
Plaintext
28 lines
810 B
Plaintext
Motorola mc146818 compatible RTC
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Required properties:
|
|
- compatible : "motorola,mc146818"
|
|
- reg : should contain registers location and length.
|
|
|
|
Optional properties:
|
|
- interrupts : should contain interrupt.
|
|
- ctrl-reg : Contains the initial value of the control register also
|
|
called "Register B".
|
|
- freq-reg : Contains the initial value of the frequency register also
|
|
called "Regsiter A".
|
|
|
|
"Register A" and "B" are usually initialized by the firmware (BIOS for
|
|
instance). If this is not done, it can be performed by the driver.
|
|
|
|
ISA Example:
|
|
|
|
rtc@70 {
|
|
compatible = "motorola,mc146818";
|
|
interrupts = <8 3>;
|
|
interrupt-parent = <&ioapic1>;
|
|
ctrl-reg = <2>;
|
|
freq-reg = <0x26>;
|
|
reg = <1 0x70 2>;
|
|
};
|