| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 1 | \# |
| Alessandro Zummo | c58411e | 2006-03-27 01:16:34 -0800 | [diff] [blame] | 2 | # RTC class/drivers configuration |
| 3 | # |
| 4 | |
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 5 | menu "Real Time Clock" |
| 6 | |
| Alessandro Zummo | c58411e | 2006-03-27 01:16:34 -0800 | [diff] [blame] | 7 | config RTC_LIB |
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 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 | |
| Alessandro Zummo | c5c3e19 | 2006-03-27 01:16:39 -0800 | [diff] [blame] | 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 | |
| Alessandro Zummo | 728a294 | 2006-03-27 01:16:40 -0800 | [diff] [blame] | 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 | |
| Alessandro Zummo | e824290 | 2006-03-27 01:16:41 -0800 | [diff] [blame] | 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 | |
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 76 | comment "RTC drivers" |
| 77 | depends on RTC_CLASS |
| 78 | |
| Alessandro Zummo | 1fec7c6 | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 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 | |
| Alessandro Zummo | edf1aaa | 2006-03-27 01:16:43 -0800 | [diff] [blame] | 89 | config RTC_DRV_DS1672 |
| 90 | tristate "Dallas/Maxim DS1672" |
| 91 | depends on RTC_CLASS && I2C |
| 92 | help |
| 93 | If you say yes here you get support for the |
| 94 | Dallas/Maxim DS1672 timekeeping chip. |
| 95 | |
| 96 | This driver can also be built as a module. If so, the module |
| 97 | will be called rtc-ds1672. |
| 98 | |
| Alessandro Zummo | b5a82d6 | 2006-03-27 01:16:44 -0800 | [diff] [blame] | 99 | config RTC_DRV_PCF8563 |
| 100 | tristate "Philips PCF8563/Epson RTC8564" |
| 101 | depends on RTC_CLASS && I2C |
| 102 | help |
| 103 | If you say yes here you get support for the |
| 104 | Philips PCF8563 RTC chip. The Epson RTC8564 |
| 105 | should work as well. |
| 106 | |
| 107 | This driver can also be built as a module. If so, the module |
| 108 | will be called rtc-pcf8563. |
| 109 | |
| Alessandro Zummo | 7520b94 | 2006-03-27 01:16:45 -0800 | [diff] [blame] | 110 | config RTC_DRV_RS5C372 |
| 111 | tristate "Ricoh RS5C372A/B" |
| 112 | depends on RTC_CLASS && I2C |
| 113 | help |
| 114 | If you say yes here you get support for the |
| 115 | Ricoh RS5C372A and RS5C372B RTC chips. |
| 116 | |
| 117 | This driver can also be built as a module. If so, the module |
| 118 | will be called rtc-rs5c372. |
| 119 | |
| Alessandro Zummo | fd507e2 | 2006-03-27 01:16:45 -0800 | [diff] [blame^] | 120 | config RTC_DRV_EP93XX |
| 121 | tristate "Cirrus Logic EP93XX" |
| 122 | depends on RTC_CLASS && ARCH_EP93XX |
| 123 | help |
| 124 | If you say yes here you get support for the |
| 125 | RTC embedded in the Cirrus Logic EP93XX processors. |
| 126 | |
| 127 | This driver can also be built as a module. If so, the module |
| 128 | will be called rtc-ep93xx. |
| 129 | |
| 130 | |
| Alessandro Zummo | a95579c | 2006-03-27 01:16:42 -0800 | [diff] [blame] | 131 | config RTC_DRV_TEST |
| 132 | tristate "Test driver/device" |
| 133 | depends on RTC_CLASS |
| 134 | help |
| 135 | If you say yes here you get support for the |
| 136 | RTC test driver. It's a software RTC which can be |
| 137 | used to test the RTC subsystem APIs. It gets |
| 138 | the time from the system clock. |
| 139 | You want this driver only if you are doing development |
| 140 | on the RTC subsystem. Please read the source code |
| 141 | for further details. |
| 142 | |
| 143 | This driver can also be built as a module. If so, the module |
| 144 | will be called rtc-test. |
| 145 | |
| Alessandro Zummo | 0c86edc | 2006-03-27 01:16:37 -0800 | [diff] [blame] | 146 | endmenu |