#
# [31mCONFIG_RTC[0m class/drivers configuration
#
config [31mCONFIG_RTC_LIB[0m
bool
config [31mCONFIG_RTC_MC146818_LIB[0m
bool
select [31mCONFIG_RTC_LIB[0m
menuconfig [31mCONFIG_RTC_CLASS[0m
bool "Real Time Clock"
default n
depends on ![31mCONFIG_S390[0m && ![31mCONFIG_UML[0m
select [31mCONFIG_RTC_LIB[0m
help
Generic [31mCONFIG_RTC[0m class support. If you say yes here, you will
be allowed to plug one or more RTCs to your system. You will
probably want to enable one or more of the interfaces below.
if [31mCONFIG_RTC_CLASS[0m
config [31mCONFIG_RTC_HCTOSYS[0m
bool "Set system time from RTC on startup and resume"
default y
help
If you say yes here, the system time (wall clock) will be set using
the value read from a specified [31mCONFIG_RTC[0m device. This is useful to avoid
unnecessary fsck runs at boot time, and to network better.
config [31mCONFIG_RTC_HCTOSYS_DEVICE[0m
string "RTC used to set the system time"
depends on [31mCONFIG_RTC_HCTOSYS[0m
default "rtc0"
help
The [31mCONFIG_RTC[0m device that will be used to (re)initialize the system
clock, usually rtc0. Initialization is done when the system
starts up, and when it resumes from a low power state. This
device should record time in UTC, since the kernel won't do
timezone correction.
The driver for this [31mCONFIG_RTC[0m device must be loaded before late_initcall
functions run, so it must usually be statically linked.
This clock should be battery-backed, so that it reads the correct
time when the system boots from a power-off state. Otherwise, your
system will need an external clock source (like an NTP server).
If the clock you specify here is not battery backed, it may still
be useful to reinitialize system time when resuming from system
sleep states. Do not specify an [31mCONFIG_RTC[0m here unless it stays powered
during all this system's supported sleep states.
config [31mCONFIG_RTC_SYSTOHC[0m
bool "Set the RTC time based on NTP synchronization"
default y
help
If you say yes here, the system time (wall clock) will be stored
in the [31mCONFIG_RTC[0m specified by [31mCONFIG_RTC_HCTOSYS_DEVICE[0m approximately every 11
minutes if userspace reports synchronized NTP status.
config [31mCONFIG_RTC_SYSTOHC_DEVICE[0m
string "RTC used to synchronize NTP adjustment"
depends on [31mCONFIG_RTC_SYSTOHC[0m
default [31mCONFIG_RTC_HCTOSYS_DEVICE[0m if [31mCONFIG_RTC_HCTOSYS[0m
default "rtc0"
help
The [31mCONFIG_RTC[0m device used for NTP synchronization. The main difference
between [31mCONFIG_RTC_HCTOSYS_DEVICE[0m and [31mCONFIG_RTC_SYSTOHC_DEVICE[0m is that this
one can sleep when setting time, because it runs in the workqueue
context.
config [31mCONFIG_RTC_DEBUG[0m
bool "RTC debug support"
help
Say yes here to enable debugging support in the [31mCONFIG_RTC[0m framework
and individual [31mCONFIG_RTC[0m drivers.
comment "RTC interfaces"
config [31mCONFIG_RTC_INTF_SYSFS[0m
bool "/sys/class/rtc/rtcN (sysfs)"
depends on [31mCONFIG_SYSFS[0m
default [31mCONFIG_RTC_CLASS[0m
help
Say yes here if you want to use your RTCs using sysfs interfaces,
/sys/class/rtc/rtc0 through /sys/.../rtcN.
If unsure, say Y.
config [31mCONFIG_RTC_INTF_PROC[0m
bool "/proc/driver/rtc (procfs for rtcN)"
depends on [31mCONFIG_PROC_FS[0m
default [31mCONFIG_RTC_CLASS[0m
help
Say yes here if you want to use your system clock [31mCONFIG_RTC[0m through
the proc interface, /proc/driver/rtc.
Other RTCs will not be available through that API.
If there is no [31mCONFIG_RTC[0m for the system clock, then the first [31mCONFIG_RTC[0m(rtc0)
is used by default.
If unsure, say Y.
config [31mCONFIG_RTC_INTF_DEV[0m
bool "/dev/rtcN (character devices)"
default [31mCONFIG_RTC_CLASS[0m
help
Say yes here if you want to use your RTCs using the /dev
interfaces, which "udev" sets up as /dev/rtc0 through
/dev/rtcN.
You may want to set up a symbolic link so one of these
can be accessed as /dev/rtc, which is a name
expected by "hwclock" and some other programs. Recent
versions of "udev" are known to set up the symlink for you.
If unsure, say Y.
config [31mCONFIG_RTC_INTF_DEV_UIE_EMUL[0m
bool "RTC UIE emulation on dev interface"
depends on [31mCONFIG_RTC_INTF_DEV[0m
help
Provides an emulation for RTC_UIE if the underlying rtc chip
driver does not expose RTC_UIE ioctls. Those requests generate
once-per-second update interrupts, used for synchronization.
The emulation code will read the time from the hardware
clock several times per second, please enable this option
only if you know that you really need it.
config [31mCONFIG_RTC_DRV_TEST[0m
tristate "Test driver/device"
help
If you say yes here you get support for the
[31mCONFIG_RTC[0m test driver. It's a software [31mCONFIG_RTC[0m which can be
used to test the [31mCONFIG_RTC[0m subsystem APIs. It gets
the time from the system clock.
You want this driver only if you are doing development
on the [31mCONFIG_RTC[0m subsystem. Please read the source code
for further details.
This driver can also be built as a module. If so, the module
will be called rtc-test.
comment "I2C RTC drivers"
if [31mCONFIG_I2C[0m
config [31mCONFIG_RTC_DRV_88PM860X[0m
tristate "Marvell 88PM860x"
depends on [31mCONFIG_MFD_88PM860X[0m
help
If you say yes here you get support for [31mCONFIG_RTC[0m function in Marvell
88PM860x chips.
This driver can also be built as a module. If so, the module
will be called rtc-88pm860x.
config [31mCONFIG_RTC_DRV_88PM80X[0m
tristate "Marvell 88PM80x"
depends on [31mCONFIG_MFD_88PM800[0m
help
If you say yes here you get support for [31mCONFIG_RTC[0m function in Marvell
88PM80x chips.
This driver can also be built as a module. If so, the module
will be called rtc-88pm80x.
config [31mCONFIG_RTC_DRV_ABB5ZES3[0m
select [31mCONFIG_REGMAP_I2C[0m
tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
help
If you say yes here you get support for the Abracon
AB-RTCMC-32.768kHz-B5ZE-S3 [31mCONFIG_I2C[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-ab-b5ze-s3.
config [31mCONFIG_RTC_DRV_ABX80X[0m
tristate "Abracon ABx80x"
help
If you say yes here you get support for Abracon AB080X and AB180X
families of ultra-low-power battery- and capacitor-backed real-time
clock chips.
This driver can also be built as a module. If so, the module
will be called rtc-abx80x.
config [31mCONFIG_RTC_DRV_AC100[0m
tristate "X-Powers AC100"
depends on [31mCONFIG_MFD_AC100[0m
help
If you say yes here you get support for the real-time clock found
in X-Powers AC100 family peripheral ICs.
This driver can also be built as a module. If so, the module
will be called rtc-ac100.
config [31mCONFIG_RTC_DRV_AS3722[0m
tristate "ams AS3722 RTC driver"
depends on [31mCONFIG_MFD_AS3722[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m of ams AS3722 PMIC
chips.
This driver can also be built as a module. If so, the module
will be called rtc-as3722.
config [31mCONFIG_RTC_DRV_DS1307[0m
tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025, ISL12057"
help
If you say yes here you get support for various compatible [31mCONFIG_RTC[0m
chips (often with battery backup) connected with [31mCONFIG_I2C[0m. This driver
should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
EPSON RX-8025, Intersil ISL12057 and probably other chips. In some
cases the [31mCONFIG_RTC[0m must already have been initialized (by manufacturing or
a bootloader).
The first seven registers on these chips hold an [31mCONFIG_RTC[0m, and other
registers may add features such as [31mCONFIG_NVRAM[0m, a trickle charger for
the [31mCONFIG_RTC[0m/[31mCONFIG_NVRAM[0m backup power, and alarms. [31mCONFIG_NVRAM[0m is visible in
sysfs, but other chip features may not be available.
This driver can also be built as a module. If so, the module
will be called rtc-ds1307.
config [31mCONFIG_RTC_DRV_DS1307_HWMON[0m
bool "HWMON support for rtc-ds1307"
depends on [31mCONFIG_RTC_DRV_DS1307[0m && [31mCONFIG_HWMON[0m
depends on !([31mCONFIG_RTC_DRV_DS1307[0m=y && [31mCONFIG_HWMON[0m=m)
default y
help
Say Y here if you want to expose temperature sensor data on
rtc-ds1307 (only DS3231)
config [31mCONFIG_RTC_DRV_DS1307_CENTURY[0m
bool "Century bit support for rtc-ds1307"
depends on [31mCONFIG_RTC_DRV_DS1307[0m
default n
help
The DS1307 driver suffered from a bug where it was enabling the
century bit inconditionnally but never used it when reading the time.
It made the driver unable to support dates beyond 2099.
Setting this option will add proper support for the century bit but if
the time was previously set using a kernel predating this option,
reading the date will return a date in the next century.
To solve that, you could boot a kernel without this option set, set
the [31mCONFIG_RTC[0m date and then boot a kernel with this option set.
config [31mCONFIG_RTC_DRV_DS1374[0m
tristate "Dallas/Maxim DS1374"
help
If you say yes here you get support for Dallas Semiconductor
DS1374 real-time clock chips. If an interrupt is associated
with the device, the alarm functionality is supported.
This driver can also be built as a module. If so, the module
will be called rtc-ds1374.
config [31mCONFIG_RTC_DRV_DS1374_WDT[0m
bool "Dallas/Maxim DS1374 watchdog timer"
depends on [31mCONFIG_RTC_DRV_DS1374[0m
help
If you say Y here you will get support for the
watchdog timer in the Dallas Semiconductor DS1374
real-time clock chips.
config [31mCONFIG_RTC_DRV_DS1672[0m
tristate "Dallas/Maxim DS1672"
help
If you say yes here you get support for the
Dallas/Maxim DS1672 timekeeping chip.
This driver can also be built as a module. If so, the module
will be called rtc-ds1672.
config [31mCONFIG_RTC_DRV_HYM8563[0m
tristate "Haoyu Microelectronics HYM8563"
depends on [31mCONFIG_OF[0m
help
Say Y to enable support for the HYM8563 [31mCONFIG_I2C[0m [31mCONFIG_RTC[0m chip. Apart
from the usual rtc functions it provides a clock output of
up to 32kHz.
This driver can also be built as a module. If so, the module
will be called rtc-hym8563.
config [31mCONFIG_RTC_DRV_LP8788[0m
tristate "TI LP8788 RTC driver"
depends on [31mCONFIG_MFD_LP8788[0m
help
Say Y to enable support for the LP8788 [31mCONFIG_RTC[0m/ALARM driver.
config [31mCONFIG_RTC_DRV_MAX6900[0m
tristate "Maxim MAX6900"
help
If you say yes here you will get support for the
Maxim MAX6900 [31mCONFIG_I2C[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-max6900.
config [31mCONFIG_RTC_DRV_MAX8907[0m
tristate "Maxim MAX8907"
depends on [31mCONFIG_MFD_MAX8907[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of Maxim MAX8907 PMIC.
This driver can also be built as a module. If so, the module
will be called rtc-max8907.
config [31mCONFIG_RTC_DRV_MAX8925[0m
tristate "Maxim MAX8925"
depends on [31mCONFIG_MFD_MAX8925[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of Maxim MAX8925 PMIC.
This driver can also be built as a module. If so, the module
will be called rtc-max8925.
config [31mCONFIG_RTC_DRV_MAX8998[0m
tristate "Maxim MAX8998"
depends on [31mCONFIG_MFD_MAX8998[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of Maxim MAX8998 PMIC.
This driver can also be built as a module. If so, the module
will be called rtc-max8998.
config [31mCONFIG_RTC_DRV_MAX8997[0m
tristate "Maxim MAX8997"
depends on [31mCONFIG_MFD_MAX8997[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of Maxim MAX8997 PMIC.
This driver can also be built as a module. If so, the module
will be called rtc-max8997.
config [31mCONFIG_RTC_DRV_MAX77686[0m
tristate "Maxim MAX77686"
depends on [31mCONFIG_MFD_MAX77686[0m || [31mCONFIG_MFD_MAX77620[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of Maxim MAX77686/MAX77620/MAX77802 PMIC.
This driver can also be built as a module. If so, the module
will be called rtc-max77686.
config [31mCONFIG_RTC_DRV_RK808[0m
tristate "Rockchip RK808/RK818 RTC"
depends on [31mCONFIG_MFD_RK808[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of RK808 and RK818 PMIC.
This driver can also be built as a module. If so, the module
will be called rk808-rtc.
config [31mCONFIG_RTC_DRV_RS5C372[0m
tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
help
If you say yes here you get support for the
Ricoh R2025S/[31mCONFIG_D[0m, RS5C372A, RS5C372B, RV5C386, and RV5C387A [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-rs5c372.
config [31mCONFIG_RTC_DRV_ISL1208[0m
tristate "Intersil ISL1208"
help
If you say yes here you get support for the
Intersil ISL1208 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-isl1208.
config [31mCONFIG_RTC_DRV_ISL12022[0m
tristate "Intersil ISL12022"
help
If you say yes here you get support for the
Intersil ISL12022 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-isl12022.
config [31mCONFIG_RTC_DRV_X1205[0m
tristate "Xicor/Intersil X1205"
help
If you say yes here you get support for the
Xicor/Intersil X1205 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-x1205.
config [31mCONFIG_RTC_DRV_PCF8523[0m
tristate "NXP PCF8523"
help
If you say yes here you get support for the NXP PCF8523 [31mCONFIG_RTC[0m
chips.
This driver can also be built as a module. If so, the module
will be called rtc-pcf8523.
config [31mCONFIG_RTC_DRV_PCF85063[0m
tristate "NXP PCF85063"
help
If you say yes here you get support for the PCF85063 [31mCONFIG_RTC[0m chip
This driver can also be built as a module. If so, the module
will be called rtc-pcf85063.
config [31mCONFIG_RTC_DRV_PCF8563[0m
tristate "Philips PCF8563/Epson RTC8564"
help
If you say yes here you get support for the
Philips PCF8563 [31mCONFIG_RTC[0m chip. The Epson RTC8564
should work as well.
This driver can also be built as a module. If so, the module
will be called rtc-pcf8563.
config [31mCONFIG_RTC_DRV_PCF8583[0m
tristate "Philips PCF8583"
help
If you say yes here you get support for the Philips PCF8583
[31mCONFIG_RTC[0m chip found on Acorn RiscPCs. This driver supports the
platform specific method of retrieving the current year from
the [31mCONFIG_RTC[0m's [31mCONFIG_SRAM[0m. It will work on other platforms with the same
chip, but the year will probably have to be tweaked.
This driver can also be built as a module. If so, the module
will be called rtc-pcf8583.
config [31mCONFIG_RTC_DRV_M41T80[0m
tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
help
If you say Y here you will get support for the ST M41T60
and M41T80 [31mCONFIG_RTC[0m chips series. Currently, the following chips are
supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
M41ST85, M41ST87, and MicroCrystal RV4162.
This driver can also be built as a module. If so, the module
will be called rtc-m41t80.
config [31mCONFIG_RTC_DRV_M41T80_WDT[0m
bool "ST M41T65/M41T80 series RTC watchdog timer"
depends on [31mCONFIG_RTC_DRV_M41T80[0m
help
If you say Y here you will get support for the
watchdog timer in the ST M41T60 and M41T80 [31mCONFIG_RTC[0m chips series.
config [31mCONFIG_RTC_DRV_BQ32K[0m
tristate "TI BQ32000"
help
If you say Y here you will get support for the TI
BQ32000 [31mCONFIG_I2C[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-bq32k.
config [31mCONFIG_RTC_DRV_DM355EVM[0m
tristate "TI DaVinci DM355 EVM RTC"
depends on [31mCONFIG_MFD_DM355EVM_MSP[0m
help
Supports the [31mCONFIG_RTC[0m firmware in the MSP430 on the DM355 [31mCONFIG_EVM[0m.
config [31mCONFIG_RTC_DRV_TWL92330[0m
bool "TI TWL92330/Menelaus"
depends on [31mCONFIG_MENELAUS[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on the
TWL92330 "Menelaus" power management chip, used with OMAP2
platforms. The support is integrated with the rest of
the Menelaus driver; it's not separate module.
config [31mCONFIG_RTC_DRV_TWL4030[0m
tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
depends on [31mCONFIG_TWL4030_CORE[0m
depends on [31mCONFIG_OF[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on the
TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
This driver can also be built as a module. If so, the module
will be called rtc-twl.
config [31mCONFIG_RTC_DRV_PALMAS[0m
tristate "TI Palmas RTC driver"
depends on [31mCONFIG_MFD_PALMAS[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m of TI PALMA series PMIC
chips.
This driver can also be built as a module. If so, the module
will be called rtc-palma.
config [31mCONFIG_RTC_DRV_TPS6586X[0m
tristate "TI TPS6586X RTC driver"
depends on [31mCONFIG_MFD_TPS6586X[0m
help
TI Power Management IC TPS6586X supports [31mCONFIG_RTC[0m functionality
along with alarm. This driver supports the [31mCONFIG_RTC[0m driver for
the TPS6586X [31mCONFIG_RTC[0m module.
config [31mCONFIG_RTC_DRV_TPS65910[0m
tristate "TI TPS65910 RTC driver"
depends on [31mCONFIG_RTC_CLASS[0m && [31mCONFIG_MFD_TPS65910[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on the
TPS65910 chips.
This driver can also be built as a module. If so, the module
will be called rtc-tps65910.
config [31mCONFIG_RTC_DRV_TPS80031[0m
tristate "TI TPS80031/TPS80032 RTC driver"
depends on [31mCONFIG_MFD_TPS80031[0m
help
TI Power Management IC TPS80031 supports [31mCONFIG_RTC[0m functionality
along with alarm. This driver supports the [31mCONFIG_RTC[0m driver for
the TPS80031 [31mCONFIG_RTC[0m module.
config [31mCONFIG_RTC_DRV_RC5T583[0m
tristate "RICOH 5T583 RTC driver"
depends on [31mCONFIG_MFD_RC5T583[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on the
RICOH 5T583 chips.
This driver can also be built as a module. If so, the module
will be called rtc-rc5t583.
config [31mCONFIG_RTC_DRV_S35390A[0m
tristate "Seiko Instruments S-35390A"
select [31mCONFIG_BITREVERSE[0m
help
If you say yes here you will get support for the Seiko
Instruments S-35390A.
This driver can also be built as a module. If so the module
will be called rtc-s35390a.
config [31mCONFIG_RTC_DRV_FM3130[0m
tristate "Ramtron FM3130"
help
If you say Y here you will get support for the
Ramtron FM3130 [31mCONFIG_RTC[0m chips.
Ramtron FM3130 is a chip with two separate devices inside,
[31mCONFIG_RTC[0m clock and FRAM. This driver provides only [31mCONFIG_RTC[0m functionality.
This driver can also be built as a module. If so the module
will be called rtc-fm3130.
config [31mCONFIG_RTC_DRV_RX8010[0m
tristate "Epson RX8010SJ"
depends on [31mCONFIG_I2C[0m
help
If you say yes here you get support for the Epson RX8010SJ [31mCONFIG_RTC[0m
chip.
This driver can also be built as a module. If so, the module
will be called rtc-rx8010.
config [31mCONFIG_RTC_DRV_RX8581[0m
tristate "Epson RX-8581"
help
If you say yes here you will get support for the Epson RX-8581.
This driver can also be built as a module. If so the module
will be called rtc-rx8581.
config [31mCONFIG_RTC_DRV_RX8025[0m
tristate "Epson RX-8025SA/NB"
help
If you say yes here you get support for the Epson
RX-8025SA/NB [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-rx8025.
config [31mCONFIG_RTC_DRV_EM3027[0m
tristate "EM Microelectronic EM3027"
help
If you say yes here you get support for the EM
Microelectronic EM3027 [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-em3027.
config [31mCONFIG_RTC_DRV_RV8803[0m
tristate "Micro Crystal RV8803, Epson RX8900"
help
If you say yes here you get support for the Micro Crystal RV8803 and
Epson RX8900 [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-rv8803.
config [31mCONFIG_RTC_DRV_S5M[0m
tristate "Samsung S2M/S5M series"
depends on [31mCONFIG_MFD_SEC_CORE[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_REGMAP_IRQ[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of Samsung S2MPS14 and S5M PMIC series.
This driver can also be built as a module. If so, the module
will be called rtc-s5m.
endif # [31mCONFIG_I2C[0m
comment "SPI RTC drivers"
if [31mCONFIG_SPI_MASTER[0m
config [31mCONFIG_RTC_DRV_M41T93[0m
tristate "ST M41T93"
help
If you say yes here you will get support for the
ST M41T93 [31mCONFIG_SPI[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-m41t93.
config [31mCONFIG_RTC_DRV_M41T94[0m
tristate "ST M41T94"
help
If you say yes here you will get support for the
ST M41T94 [31mCONFIG_SPI[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-m41t94.
config [31mCONFIG_RTC_DRV_DS1302[0m
tristate "Dallas/Maxim DS1302"
depends on [31mCONFIG_SPI[0m
help
If you say yes here you get support for the Dallas [31mCONFIG_DS1302[0m [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-ds1302.
config [31mCONFIG_RTC_DRV_DS1305[0m
tristate "Dallas/Maxim DS1305/DS1306"
help
Select this driver to get support for the Dallas/Maxim DS1305
and DS1306 real time clock chips. These support a trickle
charger, alarms, and [31mCONFIG_NVRAM[0m in addition to the clock.
This driver can also be built as a module. If so, the module
will be called rtc-ds1305.
config [31mCONFIG_RTC_DRV_DS1343[0m
select [31mCONFIG_REGMAP_SPI[0m
tristate "Dallas/Maxim DS1343/DS1344"
help
If you say yes here you get support for the
Dallas/Maxim DS1343 and DS1344 real time clock chips.
Support for trickle charger, alarm is provided.
This driver can also be built as a module. If so, the module
will be called rtc-ds1343.
config [31mCONFIG_RTC_DRV_DS1347[0m
select [31mCONFIG_REGMAP_SPI[0m
tristate "Dallas/Maxim DS1347"
help
If you say yes here you get support for the
Dallas/Maxim DS1347 chips.
This driver only supports the [31mCONFIG_RTC[0m feature, and not other chip
features such as alarms.
This driver can also be built as a module. If so, the module
will be called rtc-ds1347.
config [31mCONFIG_RTC_DRV_DS1390[0m
tristate "Dallas/Maxim DS1390/93/94"
help
If you say yes here you get support for the
Dallas/Maxim DS1390/93/94 chips.
This driver supports the [31mCONFIG_RTC[0m feature and trickle charging but not
other chip features such as alarms.
This driver can also be built as a module. If so, the module
will be called rtc-ds1390.
config [31mCONFIG_RTC_DRV_MAX6916[0m
tristate "Maxim MAX6916"
help
If you say yes here you will get support for the
Maxim MAX6916 [31mCONFIG_SPI[0m [31mCONFIG_RTC[0m chip.
This driver only supports the [31mCONFIG_RTC[0m feature, and not other chip
features such as alarms.
This driver can also be built as a module. If so, the module
will be called rtc-max6916.
config [31mCONFIG_RTC_DRV_R9701[0m
tristate "Epson RTC-9701JE"
help
If you say yes here you will get support for the
Epson [31mCONFIG_RTC[0m-9701JE [31mCONFIG_SPI[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-r9701.
config [31mCONFIG_RTC_DRV_RX4581[0m
tristate "Epson RX-4581"
help
If you say yes here you will get support for the Epson RX-4581.
This driver can also be built as a module. If so the module
will be called rtc-rx4581.
config [31mCONFIG_RTC_DRV_RX6110[0m
tristate "Epson RX-6110"
select [31mCONFIG_REGMAP_SPI[0m
help
If you say yes here you will get support for the Epson RX-6610.
This driver can also be built as a module. If so the module
will be called rtc-rx6110.
config [31mCONFIG_RTC_DRV_RS5C348[0m
tristate "Ricoh RS5C348A/B"
help
If you say yes here you get support for the
Ricoh RS5C348A and RS5C348B [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-rs5c348.
config [31mCONFIG_RTC_DRV_MAX6902[0m
tristate "Maxim MAX6902"
help
If you say yes here you will get support for the
Maxim MAX6902 [31mCONFIG_SPI[0m [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-max6902.
config [31mCONFIG_RTC_DRV_PCF2123[0m
tristate "NXP PCF2123"
help
If you say yes here you get support for the NXP PCF2123
[31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-pcf2123.
config [31mCONFIG_RTC_DRV_MCP795[0m
tristate "Microchip MCP795"
help
If you say yes here you will get support for the Microchip MCP795.
This driver can also be built as a module. If so the module
will be called rtc-mcp795.
endif # [31mCONFIG_SPI_MASTER[0m
#
# Helper to resolve issues with configs that have [31mCONFIG_SPI[0m enabled but [31mCONFIG_I2C[0m
# modular. See [31mCONFIG_SND_SOC_I2C_AND_SPI[0m for more information
#
config [31mCONFIG_RTC_I2C_AND_SPI[0m
tristate
default m if [31mCONFIG_I2C[0m=m
default y if [31mCONFIG_I2C[0m=y
default y if [31mCONFIG_SPI_MASTER[0m=y
select [31mCONFIG_REGMAP_I2C[0m if [31mCONFIG_I2C[0m
select [31mCONFIG_REGMAP_SPI[0m if [31mCONFIG_SPI_MASTER[0m
comment "SPI and I2C RTC drivers"
config [31mCONFIG_RTC_DRV_DS3232[0m
tristate "Dallas/Maxim DS3232/DS3234"
depends on [31mCONFIG_RTC_I2C_AND_SPI[0m
help
If you say yes here you get support for Dallas Semiconductor
DS3232 and DS3234 real-time clock chips. If an interrupt is associated
with the device, the alarm functionality is supported.
This driver can also be built as a module. If so, the module
will be called rtc-ds3232.
config [31mCONFIG_RTC_DRV_PCF2127[0m
tristate "NXP PCF2127"
depends on [31mCONFIG_RTC_I2C_AND_SPI[0m
help
If you say yes here you get support for the NXP PCF2127/29 [31mCONFIG_RTC[0m
chips.
This driver can also be built as a module. If so, the module
will be called rtc-pcf2127.
config [31mCONFIG_RTC_DRV_RV3029C2[0m
tristate "Micro Crystal RV3029/3049"
depends on [31mCONFIG_RTC_I2C_AND_SPI[0m
help
If you say yes here you get support for the Micro Crystal
RV3029 and RV3049 [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-rv3029c2.
config [31mCONFIG_RTC_DRV_RV3029_HWMON[0m
bool "HWMON support for RV3029/3049"
depends on [31mCONFIG_RTC_DRV_RV3029C2[0m && [31mCONFIG_HWMON[0m
depends on !([31mCONFIG_RTC_DRV_RV3029C2[0m=y && [31mCONFIG_HWMON[0m=m)
default y
help
Say Y here if you want to expose temperature sensor data on
rtc-rv3029.
comment "Platform RTC drivers"
# this 'CMOS' [31mCONFIG_RTC[0m driver is arch dependent because it requires
# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
# global rtc_lock ... it's not yet just another platform_device.
config [31mCONFIG_RTC_DRV_CMOS[0m
tristate "PC-style 'CMOS'"
depends on [31mCONFIG_X86[0m || [31mCONFIG_ARM[0m || [31mCONFIG_M32R[0m || [31mCONFIG_PPC[0m || [31mCONFIG_MIPS[0m || [31mCONFIG_SPARC64[0m || [31mCONFIG_MN10300[0m
default y if [31mCONFIG_X86[0m
select [31mCONFIG_RTC_MC146818_LIB[0m
help
Say "yes" here to get direct support for the real time clock
found in every PC or [31mCONFIG_ACPI[0m-based system, and some other boards.
Specifically the original MC146818, compatibles like those in
PC south bridges, the DS12887 or M48T86, some multifunction
or LPC bus chips, and so on.
Your system will need to define the platform device used by
this driver, otherwise it won't be accessible. This means
you can safely enable this driver if you don't know whether
or not your board has this kind of hardware.
This driver can also be built as a module. If so, the module
will be called rtc-cmos.
config [31mCONFIG_RTC_DRV_ALPHA[0m
bool "Alpha PC-style CMOS"
depends on [31mCONFIG_ALPHA[0m
select [31mCONFIG_RTC_MC146818_LIB[0m
default y
help
Direct support for the real-time clock found on every Alpha
system, specifically MC146818 compatibles. If in doubt, say Y.
config [31mCONFIG_RTC_DRV_VRTC[0m
tristate "Virtual RTC for Intel MID platforms"
depends on [31mCONFIG_X86_INTEL_MID[0m
default y if [31mCONFIG_X86_INTEL_MID[0m
help
Say "yes" here to get direct support for the real time clock
found on Moorestown platforms. The VRTC is a emulated [31mCONFIG_RTC[0m that
derives its clock source from a real [31mCONFIG_RTC[0m in the PMIC. The MC146818
style programming interface is mostly conserved, but any
updates are done via IPC calls to the system controller FW.
config [31mCONFIG_RTC_DRV_DS1216[0m
tristate "Dallas DS1216"
depends on [31mCONFIG_SNI_RM[0m
help
If you say yes here you get support for the Dallas DS1216 [31mCONFIG_RTC[0m chips.
config [31mCONFIG_RTC_DRV_DS1286[0m
tristate "Dallas DS1286"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the Dallas DS1286 [31mCONFIG_RTC[0m chips.
config [31mCONFIG_RTC_DRV_DS1511[0m
tristate "Dallas DS1511"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the
Dallas DS1511 timekeeping/watchdog chip.
This driver can also be built as a module. If so, the module
will be called rtc-ds1511.
config [31mCONFIG_RTC_DRV_DS1553[0m
tristate "Maxim/Dallas DS1553"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the
Maxim/Dallas DS1553 timekeeping chip.
This driver can also be built as a module. If so, the module
will be called rtc-ds1553.
config [31mCONFIG_RTC_DRV_DS1685_FAMILY[0m
tristate "Dallas/Maxim DS1685 Family"
help
If you say yes here you get support for the Dallas/Maxim DS1685
family of real time chips. This family includes the DS1685/DS1687,
DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
DS17885/DS17887 chips.
This driver can also be built as a module. If so, the module
will be called rtc-ds1685.
choice
prompt "Subtype"
depends on [31mCONFIG_RTC_DRV_DS1685_FAMILY[0m
default [31mCONFIG_RTC_DRV_DS1685[0m
config [31mCONFIG_RTC_DRV_DS1685[0m
bool "DS1685/DS1687"
help
This enables support for the Dallas/Maxim DS1685/DS1687 real time
clock chip.
This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
systems, as well as EPPC-405-UC modules by electronic system design
GmbH.
config [31mCONFIG_RTC_DRV_DS1689[0m
bool "DS1689/DS1693"
help
This enables support for the Dallas/Maxim DS1689/DS1693 real time
clock chip.
This is an older [31mCONFIG_RTC[0m chip, supplanted by the DS1685/DS1687 above,
which supports a few minor features such as Vcc, Vbat, and Power
Cycle counters, plus a customer-specific, 8-byte [31mCONFIG_ROM[0m/Serial number.
It also works for the even older DS1688/DS1691 [31mCONFIG_RTC[0m chips, which are
virtually the same and carry the same model number. Both chips
have 114 bytes of user [31mCONFIG_NVRAM[0m.
config [31mCONFIG_RTC_DRV_DS17285[0m
bool "DS17285/DS17287"
help
This enables support for the Dallas/Maxim DS17285/DS17287 real time
clock chip.
This chip features 2kb of extended NV-[31mCONFIG_SRAM[0m. It may possibly be
found in some SGI O2 systems (rare).
config [31mCONFIG_RTC_DRV_DS17485[0m
bool "DS17485/DS17487"
help
This enables support for the Dallas/Maxim DS17485/DS17487 real time
clock chip.
This chip features 4kb of extended NV-[31mCONFIG_SRAM[0m.
config [31mCONFIG_RTC_DRV_DS17885[0m
bool "DS17885/DS17887"
help
This enables support for the Dallas/Maxim DS17885/DS17887 real time
clock chip.
This chip features 8kb of extended NV-[31mCONFIG_SRAM[0m.
endchoice
config [31mCONFIG_RTC_DS1685_PROC_REGS[0m
bool "Display register values in /proc"
depends on [31mCONFIG_RTC_DRV_DS1685_FAMILY[0m && [31mCONFIG_PROC_FS[0m
help
Enable this to display a readout of all of the [31mCONFIG_RTC[0m registers in
/proc/drivers/rtc. Keep in mind that this can potentially lead
to lost interrupts, as reading Control Register [31mCONFIG_C[0m will clear
all pending IRQ flags.
Unless you are debugging this driver, choose N.
config [31mCONFIG_RTC_DS1685_SYSFS_REGS[0m
bool "SysFS access to RTC register bits"
depends on [31mCONFIG_RTC_DRV_DS1685_FAMILY[0m && [31mCONFIG_SYSFS[0m
help
Enable this to provide access to the [31mCONFIG_RTC[0m control register bits
in /sys. Some of the bits are read-write, others are read-only.
Keep in mind that reading Control [31mCONFIG_C[0m's bits automatically clears
all pending IRQ flags - this can cause lost interrupts.
If you know that you need access to these bits, choose Y, Else N.
config [31mCONFIG_RTC_DRV_DS1742[0m
tristate "Maxim/Dallas DS1742/1743"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the
Maxim/Dallas DS1742/1743 timekeeping chip.
This driver can also be built as a module. If so, the module
will be called rtc-ds1742.
config [31mCONFIG_RTC_DRV_DS2404[0m
tristate "Maxim/Dallas DS2404"
help
If you say yes here you get support for the
Dallas DS2404 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-ds2404.
config [31mCONFIG_RTC_DRV_DA9052[0m
tristate "Dialog DA9052/DA9053 RTC"
depends on [31mCONFIG_PMIC_DA9052[0m
help
Say y here to support the [31mCONFIG_RTC[0m driver for Dialog Semiconductor
DA9052-BC and DA9053-AA/Bx PMICs.
config [31mCONFIG_RTC_DRV_DA9055[0m
tristate "Dialog Semiconductor DA9055 RTC"
depends on [31mCONFIG_MFD_DA9055[0m
help
If you say yes here you will get support for the
[31mCONFIG_RTC[0m of the Dialog DA9055 PMIC.
This driver can also be built as a module. If so, the module
will be called rtc-da9055
config [31mCONFIG_RTC_DRV_DA9063[0m
tristate "Dialog Semiconductor DA9063/DA9062 RTC"
depends on [31mCONFIG_MFD_DA9063[0m || [31mCONFIG_MFD_DA9062[0m
help
If you say yes here you will get support for the [31mCONFIG_RTC[0m subsystem
for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
This driver can also be built as a module. If so, the module
will be called "rtc-da9063".
config [31mCONFIG_RTC_DRV_EFI[0m
tristate "EFI RTC"
depends on [31mCONFIG_EFI[0m && ![31mCONFIG_X86[0m
help
If you say yes here you will get support for the [31mCONFIG_EFI[0m
Real Time Clock.
This driver can also be built as a module. If so, the module
will be called rtc-efi.
config [31mCONFIG_RTC_DRV_STK17TA8[0m
tristate "Simtek STK17TA8"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the
Simtek STK17TA8 timekeeping chip.
This driver can also be built as a module. If so, the module
will be called rtc-stk17ta8.
config [31mCONFIG_RTC_DRV_M48T86[0m
tristate "ST M48T86/Dallas DS12887"
help
If you say Y here you will get support for the
ST M48T86 and Dallas DS12887 [31mCONFIG_RTC[0m chips.
This driver can also be built as a module. If so, the module
will be called rtc-m48t86.
config [31mCONFIG_RTC_DRV_M48T35[0m
tristate "ST M48T35"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say Y here you will get support for the
ST M48T35 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module, if so, the module
will be called "rtc-m48t35".
config [31mCONFIG_RTC_DRV_M48T59[0m
tristate "ST M48T59/M48T08/M48T02"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say Y here you will get support for the
ST M48T59 [31mCONFIG_RTC[0m chip and compatible ST M48T08 and M48T02.
These chips are usually found in Sun [31mCONFIG_SPARC[0m and UltraSPARC
workstations.
This driver can also be built as a module, if so, the module
will be called "rtc-m48t59".
config [31mCONFIG_RTC_DRV_MSM6242[0m
tristate "Oki MSM6242"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the Oki MSM6242
timekeeping chip. It is used in some Amiga models (e.g. A2000).
This driver can also be built as a module. If so, the module
will be called rtc-msm6242.
config [31mCONFIG_RTC_DRV_BQ4802[0m
tristate "TI BQ4802"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say Y here you will get support for the TI
BQ4802 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-bq4802.
config [31mCONFIG_RTC_DRV_RP5C01[0m
tristate "Ricoh RP5C01"
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the Ricoh RP5C01
timekeeping chip. It is used in some Amiga models (e.g. A3000
and A4000).
This driver can also be built as a module. If so, the module
will be called rtc-rp5c01.
config [31mCONFIG_RTC_DRV_V3020[0m
tristate "EM Microelectronic V3020"
help
If you say yes here you will get support for the
EM Microelectronic v3020 [31mCONFIG_RTC[0m chip.
This driver can also be built as a module. If so, the module
will be called rtc-v3020.
config [31mCONFIG_RTC_DRV_WM831X[0m
tristate "Wolfson Microelectronics WM831x RTC"
depends on [31mCONFIG_MFD_WM831X[0m
help
If you say yes here you will get support for the [31mCONFIG_RTC[0m subsystem
of the Wolfson Microelectronics WM831X series PMICs.
This driver can also be built as a module. If so, the module
will be called "rtc-wm831x".
config [31mCONFIG_RTC_DRV_WM8350[0m
tristate "Wolfson Microelectronics WM8350 RTC"
depends on [31mCONFIG_MFD_WM8350[0m
help
If you say yes here you will get support for the [31mCONFIG_RTC[0m subsystem
of the Wolfson Microelectronics WM8350.
This driver can also be built as a module. If so, the module
will be called "rtc-wm8350".
config [31mCONFIG_RTC_DRV_SPEAR[0m
tristate "SPEAR ST RTC"
depends on [31mCONFIG_PLAT_SPEAR[0m || [31mCONFIG_COMPILE_TEST[0m
default y
help
If you say Y here you will get support for the [31mCONFIG_RTC[0m found on
spear
config [31mCONFIG_RTC_DRV_PCF50633[0m
depends on [31mCONFIG_MFD_PCF50633[0m
tristate "NXP PCF50633 RTC"
help
If you say yes here you get support for the [31mCONFIG_RTC[0m subsystem of the
NXP PCF50633 used in embedded systems.
config [31mCONFIG_RTC_DRV_AB3100[0m
tristate "ST-Ericsson AB3100 RTC"
depends on [31mCONFIG_AB3100_CORE[0m
default y if [31mCONFIG_AB3100_CORE[0m
help
Select this to enable the ST-Ericsson AB3100 Mixed Signal IC [31mCONFIG_RTC[0m
support. This chip contains a battery- and capacitor-backed [31mCONFIG_RTC[0m.
config [31mCONFIG_RTC_DRV_AB8500[0m
tristate "ST-Ericsson AB8500 RTC"
depends on [31mCONFIG_AB8500_CORE[0m
select [31mCONFIG_RTC_INTF_DEV[0m
select [31mCONFIG_RTC_INTF_DEV_UIE_EMUL[0m
help
Select this to enable the ST-Ericsson AB8500 power management IC [31mCONFIG_RTC[0m
support. This chip contains a battery- and capacitor-backed [31mCONFIG_RTC[0m.
config [31mCONFIG_RTC_DRV_NUC900[0m
tristate "NUC910/NUC920 RTC driver"
depends on [31mCONFIG_ARCH_W90X900[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m subsystem of the
NUC910/NUC920 used in embedded systems.
config [31mCONFIG_RTC_DRV_OPAL[0m
tristate "IBM OPAL RTC driver"
depends on [31mCONFIG_PPC_POWERNV[0m
default y
help
If you say yes here you get support for the PowerNV platform [31mCONFIG_RTC[0m
driver based on OPAL interfaces.
This driver can also be built as a module. If so, the module
will be called rtc-opal.
config [31mCONFIG_RTC_DRV_ZYNQMP[0m
tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
depends on [31mCONFIG_OF[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m controller found on
Xilinx Zynq Ultrascale+ MPSoC.
comment "on-CPU RTC drivers"
config [31mCONFIG_RTC_DRV_ASM9260[0m
tristate "Alphascale asm9260 RTC"
depends on [31mCONFIG_MACH_ASM9260[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on the
Alphascale asm9260 SoC.
This driver can also be built as a module. If so, the module
will be called rtc-asm9260.
config [31mCONFIG_RTC_DRV_DAVINCI[0m
tristate "TI DaVinci RTC"
depends on [31mCONFIG_ARCH_DAVINCI_DM365[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on the
DaVinci platforms (DM365).
This driver can also be built as a module. If so, the module
will be called rtc-davinci.
config [31mCONFIG_RTC_DRV_DIGICOLOR[0m
tristate "Conexant Digicolor RTC"
depends on [31mCONFIG_ARCH_DIGICOLOR[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the [31mCONFIG_RTC[0m on Conexant
Digicolor platforms. This currently includes the CX92755 SoC.
This driver can also be built as a module. If so, the module
will be called rtc-digicolor.
config [31mCONFIG_RTC_DRV_IMXDI[0m
tristate "Freescale IMX DryIce Real Time Clock"
depends on [31mCONFIG_ARCH_MXC[0m
help
Support for Freescale IMX DryIce [31mCONFIG_RTC[0m
This driver can also be built as a module, if so, the module
will be called "rtc-imxdi".
config [31mCONFIG_RTC_DRV_OMAP[0m
tristate "TI OMAP Real Time Clock"
depends on [31mCONFIG_ARCH_OMAP[0m || [31mCONFIG_ARCH_DAVINCI[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_OF[0m
depends on [31mCONFIG_PINCTRL[0m
select [31mCONFIG_GENERIC_PINCONF[0m
help
Say "yes" here to support the on chip real time clock
present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
This driver can also be built as a module, if so, module
will be called rtc-omap.
config [31mCONFIG_HAVE_S3C_RTC[0m
bool
help
This will include [31mCONFIG_RTC[0m support for Samsung SoCs. If
you want to include [31mCONFIG_RTC[0m support for any machine, kindly
select this in the respective mach-XXXX/Kconfig file.
config [31mCONFIG_RTC_DRV_S3C[0m
tristate "Samsung S3C series SoC RTC"
depends on [31mCONFIG_ARCH_S3C64XX[0m || [31mCONFIG_HAVE_S3C_RTC[0m || [31mCONFIG_COMPILE_TEST[0m
help
[31mCONFIG_RTC[0m (Realtime Clock) driver for the clock inbuilt into the
Samsung S3C24XX series of SoCs. This can provide periodic
interrupt rates from 1Hz to 64Hz for user programs, and
wakeup from Alarm.
The driver currently supports the common features on all the
S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
and S3C2442.
This driver can also be build as a module. If so, the module
will be called rtc-s3c.
config [31mCONFIG_RTC_DRV_EP93XX[0m
tristate "Cirrus Logic EP93XX"
depends on [31mCONFIG_ARCH_EP93XX[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the
[31mCONFIG_RTC[0m embedded in the Cirrus Logic EP93XX processors.
This driver can also be built as a module. If so, the module
will be called rtc-ep93xx.
config [31mCONFIG_RTC_DRV_SA1100[0m
tristate "SA11x0/PXA2xx/PXA910"
depends on [31mCONFIG_ARCH_SA1100[0m || [31mCONFIG_ARCH_PXA[0m || [31mCONFIG_ARCH_MMP[0m
help
If you say Y here you will get access to the real time clock
built into your SA11x0 or PXA2xx CPU.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-sa1100.
config [31mCONFIG_RTC_DRV_SH[0m
tristate "SuperH On-Chip RTC"
depends on [31mCONFIG_SUPERH[0m && [31mCONFIG_HAVE_CLK[0m
help
Say Y here to enable support for the on-chip [31mCONFIG_RTC[0m found in
most SuperH processors.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-sh.
config [31mCONFIG_RTC_DRV_VR41XX[0m
tristate "NEC VR41XX"
depends on [31mCONFIG_CPU_VR41XX[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say Y here you will get access to the real time clock
built into your NEC VR41XX CPU.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-vr41xx.
config [31mCONFIG_RTC_DRV_PL030[0m
tristate "ARM AMBA PL030 RTC"
depends on [31mCONFIG_ARM_AMBA[0m
help
If you say Y here you will get access to [31mCONFIG_ARM[0m AMBA
PrimeCell PL030 [31mCONFIG_RTC[0m found on certain [31mCONFIG_ARM[0m SOCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-pl030.
config [31mCONFIG_RTC_DRV_PL031[0m
tristate "ARM AMBA PL031 RTC"
depends on [31mCONFIG_ARM_AMBA[0m
help
If you say Y here you will get access to [31mCONFIG_ARM[0m AMBA
PrimeCell PL031 [31mCONFIG_RTC[0m found on certain [31mCONFIG_ARM[0m SOCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-pl031.
config [31mCONFIG_RTC_DRV_AT32AP700X[0m
tristate "AT32AP700X series RTC"
depends on [31mCONFIG_PLATFORM_AT32AP[0m || [31mCONFIG_COMPILE_TEST[0m
help
Driver for the internal [31mCONFIG_RTC[0m (Realtime Clock) on Atmel [31mCONFIG_AVR32[0m
AT32AP700x family processors.
config [31mCONFIG_RTC_DRV_AT91RM9200[0m
tristate "AT91RM9200 or some AT91SAM9 RTC"
depends on [31mCONFIG_ARCH_AT91[0m || [31mCONFIG_COMPILE_TEST[0m
help
Driver for the internal [31mCONFIG_RTC[0m (Realtime Clock) module found on
Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
this is powered by the backup power supply.
config [31mCONFIG_RTC_DRV_AT91SAM9[0m
tristate "AT91SAM9 RTT as RTC"
depends on [31mCONFIG_ARCH_AT91[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_MFD_SYSCON[0m
help
Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
can be used as an [31mCONFIG_RTC[0m thanks to the backup power supply (e.g. a
small coin cell battery) which keeps this block and the GPBR
(General Purpose Backup Registers) block powered when the device
is shutdown.
Some AT91SAM9 SoCs provide a real [31mCONFIG_RTC[0m block, on those ones you'd
probably want to use the real [31mCONFIG_RTC[0m block instead of the "RTT as an
RTC" driver.
config [31mCONFIG_RTC_DRV_AU1XXX[0m
tristate "Au1xxx Counter0 RTC support"
depends on [31mCONFIG_MIPS_ALCHEMY[0m
help
This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
counter) to be used as a [31mCONFIG_RTC[0m.
This driver can also be built as a module. If so, the module
will be called rtc-au1xxx.
config [31mCONFIG_RTC_DRV_BFIN[0m
tristate "Blackfin On-Chip RTC"
depends on [31mCONFIG_BLACKFIN[0m && ![31mCONFIG_BF561[0m
help
If you say yes here you will get support for the
Blackfin On-Chip Real Time Clock.
This driver can also be built as a module. If so, the module
will be called rtc-bfin.
config [31mCONFIG_RTC_DRV_RS5C313[0m
tristate "Ricoh RS5C313"
depends on [31mCONFIG_SH_LANDISK[0m
help
If you say yes here you get support for the Ricoh RS5C313 [31mCONFIG_RTC[0m chips.
config [31mCONFIG_RTC_DRV_GENERIC[0m
tristate "Generic RTC support"
# Please consider writing a new [31mCONFIG_RTC[0m driver instead of using the generic
# [31mCONFIG_RTC[0m abstraction
depends on [31mCONFIG_PARISC[0m || [31mCONFIG_M68K[0m || [31mCONFIG_PPC[0m || [31mCONFIG_SUPERH32[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y or [31mCONFIG_M[0m here to enable [31mCONFIG_RTC[0m support on systems using the generic
[31mCONFIG_RTC[0m abstraction. If you do not know what you are doing, you should
just say Y.
config [31mCONFIG_RTC_DRV_PXA[0m
tristate "PXA27x/PXA3xx"
depends on [31mCONFIG_ARCH_PXA[0m
select [31mCONFIG_RTC_DRV_SA1100[0m
help
If you say Y here you will get access to the real time clock
built into your [31mCONFIG_PXA27x[0m or [31mCONFIG_PXA3xx[0m CPU. This [31mCONFIG_RTC[0m is actually 2 RTCs
consisting of an SA1100 compatible [31mCONFIG_RTC[0m and the extended PXA [31mCONFIG_RTC[0m.
This [31mCONFIG_RTC[0m driver uses PXA [31mCONFIG_RTC[0m registers available since pxa27x
series (RDxR, RYxR) instead of legacy RCNR, RTAR.
config [31mCONFIG_RTC_DRV_VT8500[0m
tristate "VIA/WonderMedia 85xx SoC RTC"
depends on [31mCONFIG_ARCH_VT8500[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say Y here you will get access to the real time clock
built into your VIA VT8500 SoC or its relatives.
config [31mCONFIG_RTC_DRV_SUN4V[0m
bool "SUN4V Hypervisor RTC"
depends on [31mCONFIG_SPARC64[0m
help
If you say Y here you will get support for the Hypervisor
based [31mCONFIG_RTC[0m on SUN4V systems.
config [31mCONFIG_RTC_DRV_SUN6I[0m
tristate "Allwinner A31 RTC"
default [31mCONFIG_MACH_SUN6I[0m || [31mCONFIG_MACH_SUN8I[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_ARCH_SUNXI[0m
help
If you say Y here you will get support for the [31mCONFIG_RTC[0m found in
some Allwinner SoCs like the A31 or the A64.
config [31mCONFIG_RTC_DRV_SUNXI[0m
tristate "Allwinner sun4i/sun7i RTC"
depends on [31mCONFIG_MACH_SUN4I[0m || [31mCONFIG_MACH_SUN7I[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say Y here you will get support for the [31mCONFIG_RTC[0m found on
Allwinner A10/A20.
config [31mCONFIG_RTC_DRV_STARFIRE[0m
bool "Starfire RTC"
depends on [31mCONFIG_SPARC64[0m
help
If you say Y here you will get support for the [31mCONFIG_RTC[0m found on
Starfire systems.
config [31mCONFIG_RTC_DRV_TX4939[0m
tristate "TX4939 SoC"
depends on [31mCONFIG_SOC_TX4939[0m
help
Driver for the internal [31mCONFIG_RTC[0m (Realtime Clock) module found on
Toshiba TX4939 SoC.
config [31mCONFIG_RTC_DRV_MV[0m
tristate "Marvell SoC RTC"
depends on [31mCONFIG_ARCH_DOVE[0m || [31mCONFIG_ARCH_MVEBU[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you will get support for the in-chip [31mCONFIG_RTC[0m
that can be found in some of Marvell's SoC devices, such as
the Kirkwood 88F6281 and 88F6192.
This driver can also be built as a module. If so, the module
will be called rtc-mv.
config [31mCONFIG_RTC_DRV_ARMADA38X[0m
tristate "Armada 38x Marvell SoC RTC"
depends on [31mCONFIG_ARCH_MVEBU[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you will get support for the in-chip [31mCONFIG_RTC[0m
that can be found in the Armada 38x Marvell's SoC device
This driver can also be built as a module. If so, the module
will be called armada38x-rtc.
config [31mCONFIG_RTC_DRV_GEMINI[0m
tristate "Gemini SoC RTC"
depends on [31mCONFIG_ARCH_GEMINI[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
help
If you say Y here you will get support for the
[31mCONFIG_RTC[0m found on Gemini SoC's.
This driver can also be built as a module. If so, the module
will be called rtc-gemini.
config [31mCONFIG_RTC_DRV_PS3[0m
tristate "PS3 RTC"
depends on [31mCONFIG_PPC_PS3[0m
help
If you say yes here you will get support for the [31mCONFIG_RTC[0m on PS3.
This driver can also be built as a module. If so, the module
will be called rtc-ps3.
config [31mCONFIG_RTC_DRV_COH901331[0m
tristate "ST-Ericsson COH 901 331 RTC"
depends on [31mCONFIG_ARCH_U300[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say Y here you will get access to ST-Ericsson
COH 901 331 [31mCONFIG_RTC[0m clock found in some ST-Ericsson Mobile
Platforms.
This driver can also be built as a module. If so, the module
will be called "rtc-coh901331".
config [31mCONFIG_RTC_DRV_STMP[0m
tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
depends on [31mCONFIG_ARCH_MXS[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_STMP_DEVICE[0m
help
If you say yes here you will get support for the onboard
STMP3xxx/i.MX23/i.MX28 [31mCONFIG_RTC[0m.
This driver can also be built as a module. If so, the module
will be called rtc-stmp3xxx.
config [31mCONFIG_RTC_DRV_PCAP[0m
tristate "PCAP RTC"
depends on [31mCONFIG_EZX_PCAP[0m
help
If you say Y here you will get support for the [31mCONFIG_RTC[0m found on
the PCAP2 ASIC used on some Motorola phones.
config [31mCONFIG_RTC_DRV_MC13XXX[0m
depends on [31mCONFIG_MFD_MC13XXX[0m
tristate "Freescale MC13xxx RTC"
help
This enables support for the RTCs found on Freescale's PMICs
MC13783 and MC13892.
config [31mCONFIG_RTC_DRV_MPC5121[0m
tristate "Freescale MPC5121 built-in RTC"
depends on [31mCONFIG_PPC_MPC512x[0m || [31mCONFIG_PPC_MPC52xx[0m
help
If you say yes here you will get support for the
built-in [31mCONFIG_RTC[0m on MPC5121 or on MPC5200.
This driver can also be built as a module. If so, the module
will be called rtc-mpc5121.
config [31mCONFIG_RTC_DRV_JZ4740[0m
tristate "Ingenic JZ4740 SoC"
depends on [31mCONFIG_MACH_INGENIC[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the Ingenic JZ47xx SoCs [31mCONFIG_RTC[0m
controllers.
This driver can also be buillt as a module. If so, the module
will be called rtc-jz4740.
config [31mCONFIG_RTC_DRV_LPC24XX[0m
tristate "NXP RTC for LPC178x/18xx/408x/43xx"
depends on [31mCONFIG_ARCH_LPC18XX[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_OF[0m && [31mCONFIG_HAS_IOMEM[0m
help
This enables support for the NXP [31mCONFIG_RTC[0m found which can be found on
NXP LPC178x/18xx/408x/43xx devices.
If you have one of the devices above enable this driver to use
the hardware [31mCONFIG_RTC[0m. This driver can also be built as a module. If
so, the module will be called rtc-lpc24xx.
config [31mCONFIG_RTC_DRV_LPC32XX[0m
depends on [31mCONFIG_ARCH_LPC32XX[0m || [31mCONFIG_COMPILE_TEST[0m
tristate "NXP LPC32XX RTC"
help
This enables support for the NXP [31mCONFIG_RTC[0m in the LPC32XX
This driver can also be built as a module. If so, the module
will be called rtc-lpc32xx.
config [31mCONFIG_RTC_DRV_PM8XXX[0m
tristate "Qualcomm PMIC8XXX RTC"
depends on [31mCONFIG_MFD_PM8XXX[0m || [31mCONFIG_MFD_SPMI_PMIC[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the
Qualcomm PMIC8XXX [31mCONFIG_RTC[0m.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-pm8xxx.
config [31mCONFIG_RTC_DRV_TEGRA[0m
tristate "NVIDIA Tegra Internal RTC driver"
depends on [31mCONFIG_ARCH_TEGRA[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the
Tegra 200 series internal [31mCONFIG_RTC[0m module.
This drive can also be built as a module. If so, the module
will be called rtc-tegra.
config [31mCONFIG_RTC_DRV_TILE[0m
tristate "Tilera hypervisor RTC support"
depends on [31mCONFIG_TILE[0m
help
Enable support for the Linux driver side of the Tilera
hypervisor's real-time clock interface.
config [31mCONFIG_RTC_DRV_PUV3[0m
tristate "PKUnity v3 RTC support"
depends on [31mCONFIG_ARCH_PUV3[0m
help
This enables support for the [31mCONFIG_RTC[0m in the PKUnity-v3 SoCs.
This drive can also be built as a module. If so, the module
will be called rtc-puv3.
config [31mCONFIG_RTC_DRV_LOONGSON1[0m
tristate "loongson1 RTC support"
depends on [31mCONFIG_MACH_LOONGSON32[0m
help
This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
counter) to be used as a [31mCONFIG_RTC[0m.
This driver can also be built as a module. If so, the module
will be called rtc-ls1x.
config [31mCONFIG_RTC_DRV_MXC[0m
tristate "Freescale MXC Real Time Clock"
depends on [31mCONFIG_ARCH_MXC[0m
help
If you say yes here you get support for the Freescale MXC
[31mCONFIG_RTC[0m module.
This driver can also be built as a module, if so, the module
will be called "rtc-mxc".
config [31mCONFIG_RTC_DRV_SNVS[0m
tristate "Freescale SNVS RTC support"
select [31mCONFIG_REGMAP_MMIO[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_OF[0m
help
If you say yes here you get support for the Freescale SNVS
Low Power (LP) [31mCONFIG_RTC[0m module.
This driver can also be built as a module, if so, the module
will be called "rtc-snvs".
config [31mCONFIG_RTC_DRV_SIRFSOC[0m
tristate "SiRFSOC RTC"
depends on [31mCONFIG_ARCH_SIRF[0m
help
Say "yes" here to support the real time clock on SiRF SOC chips.
This driver can also be built as a module called rtc-sirfsoc.
config [31mCONFIG_RTC_DRV_ST_LPC[0m
tristate "STMicroelectronics LPC RTC"
depends on [31mCONFIG_ARCH_STI[0m
depends on [31mCONFIG_OF[0m
help
Say Y here to include STMicroelectronics Low Power Controller
(LPC) based [31mCONFIG_RTC[0m support.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rtc-st-lpc.
config [31mCONFIG_RTC_DRV_MOXART[0m
tristate "MOXA ART RTC"
depends on [31mCONFIG_ARCH_MOXART[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the MOXA ART
[31mCONFIG_RTC[0m module.
This driver can also be built as a module. If so, the module
will be called rtc-moxart
config [31mCONFIG_RTC_DRV_MT6397[0m
tristate "Mediatek Real Time Clock driver"
depends on [31mCONFIG_MFD_MT6397[0m || ([31mCONFIG_COMPILE_TEST[0m && [31mCONFIG_IRQ_DOMAIN[0m)
help
This selects the Mediatek(R) [31mCONFIG_RTC[0m driver. [31mCONFIG_RTC[0m is part of Mediatek
MT6397 PMIC. You should enable MT6397 PMIC MFD before select
Mediatek(R) [31mCONFIG_RTC[0m driver.
If you want to use Mediatek(R) [31mCONFIG_RTC[0m interface, select Y or [31mCONFIG_M[0m here.
config [31mCONFIG_RTC_DRV_XGENE[0m
tristate "APM X-Gene RTC"
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_ARCH_XGENE[0m || [31mCONFIG_COMPILE_TEST[0m
help
If you say yes here you get support for the [31mCONFIG_APM[0m X-Gene SoC real time
clock.
This driver can also be built as a module, if so, the module
will be called "rtc-xgene".
config [31mCONFIG_RTC_DRV_PIC32[0m
tristate "Microchip PIC32 RTC"
depends on [31mCONFIG_MACH_PIC32[0m
default y
help
If you say yes here you get support for the PIC32 [31mCONFIG_RTC[0m module.
This driver can also be built as a module. If so, the module
will be called rtc-pic32
config [31mCONFIG_RTC_DRV_R7301[0m
tristate "EPSON TOYOCOM RTC-7301SF/DG"
select [31mCONFIG_REGMAP_MMIO[0m
depends on [31mCONFIG_OF[0m && [31mCONFIG_HAS_IOMEM[0m
help
If you say yes here you get support for the EPSON TOYOCOM
[31mCONFIG_RTC[0m-7301SF/DG chips.
This driver can also be built as a module. If so, the module
will be called rtc-r7301.
comment "HID Sensor RTC drivers"
config [31mCONFIG_RTC_DRV_HID_SENSOR_TIME[0m
tristate "HID Sensor Time"
depends on [31mCONFIG_USB_HID[0m
select [31mCONFIG_IIO[0m
select [31mCONFIG_HID_SENSOR_HUB[0m
select [31mCONFIG_HID_SENSOR_IIO_COMMON[0m
help
Say yes here to build support for the [31mCONFIG_HID[0m Sensors of type Time.
This drivers makes such sensors available as RTCs.
If this driver is compiled as a module, it will be named
rtc-hid-sensor-time.
endif # [31mCONFIG_RTC_CLASS[0m