Lines Matching +full:system +full:- +full:on +full:- +full:chips

7 works even with system power off.  Such clocks will normally not track
8 the local time zone or daylight savings time -- unless they dual boot
9 with MS-Windows -- but will instead be set to Coordinated Universal Time
12 The newest non-PC hardware tends to just count seconds, like the time(2)
13 system call reports, but RTCs also very commonly represent time using
16 Linux has two largely-compatible userspace RTC API families you may
20 	so it's not very portable to non-x86 systems.
23 	supported by a wide variety of RTC chips on all systems.
35 Old PC/AT-Compatible driver:  /dev/rtc
36 --------------------------------------
40 actually have a Motorola MC146818 (or clone) on the board. This is the
44 a few ways (enabling longer alarm periods, and wake-from-hibernate).
53 ring on the 30th second of the 30th minute of every hour, for example.
59 the type of interrupt (update-done, alarm-rang, or periodic) that was
61 the last read.  Status information is reported through the pseudo-file
67 select(2) on /dev/rtc -- either will block/stop the user process until
75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
83 an evil user generating lots of IRQs on a slow 386sx-16, where it might have
84 a negative impact on performance. This 64Hz limit can be changed by writing
85 a different value to /proc/sys/dev/rtc/max-user-freq. Note that the
99 Rather than write 50 pages describing the ioctl() and so on, it is
109 --------------------------------------------
111 Because Linux supports many non-ACPI and non-PC platforms, some of which
113 than expecting a single battery-backed MC146818 clone on every system.
122     *	/proc/driver/rtc ... the system clock RTC may expose itself
123 	using a procfs interface. If there is no RTC for the system clock,
128 integrated into embeddable system-on-chip (SOC) processors to discrete chips
130 even support for PC-style RTCs ... including the features exposed on newer PCs
133 The new framework also removes the "one RTC per system" restriction.  For
134 example, maybe the low-power battery-backed RTC is a discrete I2C chip, but
135 a high functionality RTC is integrated into the SOC.  That system might read
136 the system clock from the discrete RTC, but use the integrated one for all