Lines Matching refs:RTC
2 * RTC class driver for "CMOS RTC": PCs, ACPI, etc
23 * bypass the RTC framework, directly reading the RTC during boot
41 /* this is for "generic access to PC-style RTC" using CMOS_READ/CMOS_WRITE */
85 * HPET #1 hijacking the IRQ for this RTC, and being unavailable for
89 * emulation of hardware RTC IRQ facilities using HPET #1. We don't
151 * for RTC and NVRAM and the second only for NVRAM. Caller must
470 * (non-RTC) bit; and SQWE is ignored on many current systems.
511 * RTC registers and NVRAM. Most of those bytes of NVRAM are used
570 /* don't trash RTC registers */
613 * Note that HPET and RTC are almost certainly out of phase,
622 /* All Linux RTC alarms should be treated as if they were oneshot.
691 #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes.
888 /* We want RTC alarms to wake us from e.g. ACPI G2/S5 "soft off", even
956 /* On non-x86 systems, a "CMOS" RTC lives most naturally on platform_bus.
979 * After the RTC handler is installed, the Fixed_RTC event should
980 * be disabled. Only when the RTC alarm is set will it be enabled.
1000 * that this board's RTC is wakeup-capable (per ACPI spec).
1026 dev_info(dev, "RTC can wake from S4\n");
1030 /* RTC always wakes from S1/S2/S3, and often S4/STD */
1053 /* Some machines contain a PNP entry for the RTC, but
1120 /* Platform setup should have set up an RTC device, when PNP is