projects / linux-2.6-block.git / blame
| Commit | Line | Data |
|---|---|---|
| 0c86edc0 | 1 | \# |
| c58411e9 AZ |
2 | # RTC class/drivers configuration |
| 3 | # | |
| 4 | ||
| 0c86edc0 AZ |
5 | menu "Real Time Clock" |
| 6 | ||
| c58411e9 | 7 | config RTC_LIB |
| 0c86edc0 AZ |
8 | tristate |
| 9 | ||
| 10 | config RTC_CLASS | |
| 11 | tristate "RTC class" | |
| 12 | depends on EXPERIMENTAL | |
| 13 | default n | |
| 14 | select RTC_LIB | |
| 15 | help | |
| 16 | Generic RTC class support. If you say yes here, you will | |
| 17 | be allowed to plug one or more RTCs to your system. You will | |
| 18 | probably want to enable one of more of the interfaces below. | |
| 19 | ||
| 20 | This driver can also be built as a module. If so, the module | |
| 21 | will be called rtc-class. | |
| 22 | ||
| 23 | config RTC_HCTOSYS | |
| 24 | bool "Set system time from RTC on startup" | |
| 25 | depends on RTC_CLASS = y | |
| 26 | default y | |
| 27 | help | |
| 28 | If you say yes here, the system time will be set using | |
| 29 | the value read from the specified RTC device. This is useful | |
| 30 | in order to avoid unnecessary fschk runs. | |
| 31 | ||
| 32 | config RTC_HCTOSYS_DEVICE | |
| 33 | string "The RTC to read the time from" | |
| 34 | depends on RTC_HCTOSYS = y | |
| 35 | default "rtc0" | |
| 36 | help | |
| 37 | The RTC device that will be used as the source for | |
| 38 | the system time, usually rtc0. | |
| 39 | ||
| 40 | comment "RTC interfaces" | |
| 41 | depends on RTC_CLASS | |
| 42 | ||
| c5c3e192 AZ |
43 | config RTC_INTF_SYSFS |
| 44 | tristate "sysfs" | |
| 45 | depends on RTC_CLASS && SYSFS | |
| 46 | default RTC_CLASS | |
| 47 | help | |
| 48 | Say yes here if you want to use your RTC using the sysfs | |
| 49 | interface, /sys/class/rtc/rtcX . | |
| 50 | ||
| 51 | This driver can also be built as a module. If so, the module | |
| 52 | will be called rtc-sysfs. | |
| 53 | ||
| 728a2947 AZ |
54 | config RTC_INTF_PROC |
| 55 | tristate "proc" | |
| 56 | depends on RTC_CLASS && PROC_FS | |
| 57 | default RTC_CLASS | |
| 58 | help | |
| 59 | Say yes here if you want to use your RTC using the proc | |
| 60 | interface, /proc/driver/rtc . | |
| 61 | ||
| 62 | This driver can also be built as a module. If so, the module | |
| 63 | will be called rtc-proc. | |
| 64 | ||
| e824290e AZ |
65 | config RTC_INTF_DEV |
| 66 | tristate "dev" | |
| 67 | depends on RTC_CLASS | |
| 68 | default RTC_CLASS | |
| 69 | help | |
| 70 | Say yes here if you want to use your RTC using the dev | |
| 71 | interface, /dev/rtc . | |
| 72 | ||
| 73 | This driver can also be built as a module. If so, the module | |
| 74 | will be called rtc-dev. | |
| 75 | ||
| 0c86edc0 AZ |
76 | comment "RTC drivers" |
| 77 | depends on RTC_CLASS | |
| 78 | ||
| 1fec7c66 AZ |
79 | config RTC_DRV_X1205 |
| 80 | tristate "Xicor/Intersil X1205" | |
| 81 | depends on RTC_CLASS && I2C | |
| 82 | help | |
| 83 | If you say yes here you get support for the | |
| 84 | Xicor/Intersil X1205 RTC chip. | |
| 85 | ||
| 86 | This driver can also be built as a module. If so, the module | |
| 87 | will be called rtc-x1205. | |
| 88 | ||
| a95579cd AZ |
89 | config RTC_DRV_TEST |
| 90 | tristate "Test driver/device" | |
| 91 | depends on RTC_CLASS | |
| 92 | help | |
| 93 | If you say yes here you get support for the | |
| 94 | RTC test driver. It's a software RTC which can be | |
| 95 | used to test the RTC subsystem APIs. It gets | |
| 96 | the time from the system clock. | |
| 97 | You want this driver only if you are doing development | |
| 98 | on the RTC subsystem. Please read the source code | |
| 99 | for further details. | |
| 100 | ||
| 101 | This driver can also be built as a module. If so, the module | |
| 102 | will be called rtc-test. | |
| 103 | ||
| 0c86edc0 | 104 | endmenu |