1*4882a593SmuzhiyunWhat: /sys/class/rtc/ 2*4882a593SmuzhiyunDate: March 2006 3*4882a593SmuzhiyunKernelVersion: 2.6.17 4*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 5*4882a593SmuzhiyunDescription: 6*4882a593Smuzhiyun The rtc/ class subdirectory belongs to the RTC subsystem. 7*4882a593Smuzhiyun 8*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/ 9*4882a593SmuzhiyunDate: March 2006 10*4882a593SmuzhiyunKernelVersion: 2.6.17 11*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 12*4882a593SmuzhiyunDescription: 13*4882a593Smuzhiyun The /sys/class/rtc/rtc{0,1,2,3,...} directories correspond 14*4882a593Smuzhiyun to each RTC device. 15*4882a593Smuzhiyun 16*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/date 17*4882a593SmuzhiyunDate: March 2006 18*4882a593SmuzhiyunKernelVersion: 2.6.17 19*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 20*4882a593SmuzhiyunDescription: 21*4882a593Smuzhiyun (RO) RTC-provided date in YYYY-MM-DD format 22*4882a593Smuzhiyun 23*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/hctosys 24*4882a593SmuzhiyunDate: September 2009 25*4882a593SmuzhiyunKernelVersion: 2.6.32 26*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 27*4882a593SmuzhiyunDescription: 28*4882a593Smuzhiyun (RO) 1 if the RTC provided the system time at boot via the 29*4882a593Smuzhiyun CONFIG_RTC_HCTOSYS kernel option, 0 otherwise 30*4882a593Smuzhiyun 31*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/max_user_freq 32*4882a593SmuzhiyunDate: October 2007 33*4882a593SmuzhiyunKernelVersion: 2.6.24 34*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 35*4882a593SmuzhiyunDescription: 36*4882a593Smuzhiyun (RW) The maximum interrupt rate an unprivileged user may request 37*4882a593Smuzhiyun from this RTC. 38*4882a593Smuzhiyun 39*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/name 40*4882a593SmuzhiyunDate: March 2006 41*4882a593SmuzhiyunKernelVersion: 2.6.17 42*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 43*4882a593SmuzhiyunDescription: 44*4882a593Smuzhiyun (RO) The name of the RTC corresponding to this sysfs directory 45*4882a593Smuzhiyun 46*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/range 47*4882a593SmuzhiyunDate: January 2018 48*4882a593SmuzhiyunKernelVersion: 4.16 49*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 50*4882a593SmuzhiyunDescription: 51*4882a593Smuzhiyun Valid time range for the RTC, as seconds from epoch, formatted 52*4882a593Smuzhiyun as [min, max] 53*4882a593Smuzhiyun 54*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/since_epoch 55*4882a593SmuzhiyunDate: March 2006 56*4882a593SmuzhiyunKernelVersion: 2.6.17 57*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 58*4882a593SmuzhiyunDescription: 59*4882a593Smuzhiyun (RO) RTC-provided time as the number of seconds since the epoch 60*4882a593Smuzhiyun 61*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/time 62*4882a593SmuzhiyunDate: March 2006 63*4882a593SmuzhiyunKernelVersion: 2.6.17 64*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 65*4882a593SmuzhiyunDescription: 66*4882a593Smuzhiyun (RO) RTC-provided time in 24-hour notation (hh:mm:ss) 67*4882a593Smuzhiyun 68*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/offset 69*4882a593SmuzhiyunDate: February 2016 70*4882a593SmuzhiyunKernelVersion: 4.6 71*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 72*4882a593SmuzhiyunDescription: 73*4882a593Smuzhiyun (RW) The amount which the rtc clock has been adjusted in 74*4882a593Smuzhiyun firmware. Visible only if the driver supports clock offset 75*4882a593Smuzhiyun adjustment. The unit is parts per billion, i.e. The number of 76*4882a593Smuzhiyun clock ticks which are added to or removed from the rtc's base 77*4882a593Smuzhiyun clock per billion ticks. A positive value makes a day pass more 78*4882a593Smuzhiyun slowly, longer, and a negative value makes a day pass more 79*4882a593Smuzhiyun quickly. 80*4882a593Smuzhiyun 81*4882a593SmuzhiyunWhat: /sys/class/rtc/rtcX/wakealarm 82*4882a593SmuzhiyunDate: February 2007 83*4882a593SmuzhiyunKernelVersion: 2.6.20 84*4882a593SmuzhiyunContact: linux-rtc@vger.kernel.org 85*4882a593SmuzhiyunDescription: 86*4882a593Smuzhiyun (RW) The time at which the clock will generate a system wakeup 87*4882a593Smuzhiyun event. This is a one shot wakeup event, so must be reset after 88*4882a593Smuzhiyun wake if a daily wakeup is required. Format is seconds since the 89*4882a593Smuzhiyun epoch by default, or if there's a leading +, seconds in the 90*4882a593Smuzhiyun future, or if there is a leading +=, seconds ahead of the 91*4882a593Smuzhiyun current alarm. 92