[PATCH] RTC framework driver for CMOS RTCs
This is an "RTC framework" driver for the "CMOS" RTCs which are standard on
PCs and some other platforms. That's MC146818 compatible silicon.
Advantages of this vs. drivers/char/rtc.c (use one _or_ the other, only
one will be able to claim the RTC irq) include:
- This leverages both the new RTC framework and the driver model; both
PNPACPI and platform device modes are supported. (A separate patch
creates a platform device on PCs where PNPACPI isn't configured.)
- It supports common extensions like longer alarms. (A separate patch
exports that information from ACPI through platform_data.)
- Likewise, system wakeup events use "real driver model support", with
policy control via sysfs "wakeup" attributes and and using normal rtc
ioctls to manage wakeup. (Patch in the works. The ACPI hooks are
known; /proc/acpi/alarm can vanish. Making it work with EFI will
be a minor challenge to someone with e.g. a MiniMac.)
It's not yet been tested on non-x86 systems, without ACPI, or with HPET.
And the RTC framework will surely have teething pains on "mainstream"
PC-based systems (though must embedded Linux systems use it heavily), not
limited to sorting out the "/dev/rtc0" issue (udev easily tweaked). Also,
the ALSA rtctimer code doesn't use the new RTC API.
Otherwise, this should be a no-known-regressions replacement for the old
drivers/char/rtc.c driver, and should help the non-embedded distros (and
the new timekeeping code) start to switch to the framework.
Note also that any systems using "rtc-m48t86" are candidates to switch over
to this more functional driver; the platform data is different, and the way
bytes are read is different, but otherwise those chips should be compatible.
[akpm@osdl.org: sparc32 fix]
[akpm@osdl.org: sparc64 fix]
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: Woody Suwalski <woodys@xandros.com>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-02-10 17:46:02 +08:00
|
|
|
#
|
2006-03-27 17:16:34 +08:00
|
|
|
# RTC class/drivers configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config RTC_LIB
|
2011-04-30 06:03:11 +08:00
|
|
|
bool
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2016-06-01 22:46:23 +08:00
|
|
|
config RTC_MC146818_LIB
|
|
|
|
|
bool
|
|
|
|
|
select RTC_LIB
|
|
|
|
|
|
2007-07-31 15:39:46 +08:00
|
|
|
menuconfig RTC_CLASS
|
2011-04-30 06:03:11 +08:00
|
|
|
bool "Real Time Clock"
|
2006-03-27 17:16:37 +08:00
|
|
|
default n
|
2011-08-19 03:11:59 +08:00
|
|
|
depends on !S390 && !UML
|
2006-03-27 17:16:37 +08:00
|
|
|
select RTC_LIB
|
|
|
|
|
help
|
|
|
|
|
Generic RTC class support. If you say yes here, you will
|
2015-05-10 03:21:54 +08:00
|
|
|
be allowed to plug one or more RTCs to your system. You will
|
2006-07-01 00:18:41 +08:00
|
|
|
probably want to enable one or more of the interfaces below.
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2007-07-31 15:39:46 +08:00
|
|
|
if RTC_CLASS
|
|
|
|
|
|
2006-03-27 17:16:37 +08:00
|
|
|
config RTC_HCTOSYS
|
2007-05-08 15:33:42 +08:00
|
|
|
bool "Set system time from RTC on startup and resume"
|
2006-03-27 17:16:37 +08:00
|
|
|
default y
|
|
|
|
|
help
|
2007-05-08 15:33:42 +08:00
|
|
|
If you say yes here, the system time (wall clock) will be set using
|
|
|
|
|
the value read from a specified RTC device. This is useful to avoid
|
|
|
|
|
unnecessary fsck runs at boot time, and to network better.
|
2006-03-27 17:16:37 +08:00
|
|
|
|
|
|
|
|
config RTC_HCTOSYS_DEVICE
|
2007-05-08 15:33:42 +08:00
|
|
|
string "RTC used to set the system time"
|
2015-06-12 11:10:16 +08:00
|
|
|
depends on RTC_HCTOSYS
|
2006-03-27 17:16:37 +08:00
|
|
|
default "rtc0"
|
|
|
|
|
help
|
2007-05-08 15:33:42 +08:00
|
|
|
The RTC device that will be used to (re)initialize the system
|
2009-01-07 06:42:17 +08:00
|
|
|
clock, usually rtc0. Initialization is done when the system
|
|
|
|
|
starts up, and when it resumes from a low power state. This
|
2007-11-15 08:58:29 +08:00
|
|
|
device should record time in UTC, since the kernel won't do
|
|
|
|
|
timezone correction.
|
2007-05-08 15:33:42 +08:00
|
|
|
|
2007-07-21 19:37:56 +08:00
|
|
|
The driver for this RTC device must be loaded before late_initcall
|
|
|
|
|
functions run, so it must usually be statically linked.
|
|
|
|
|
|
2007-05-08 15:33:42 +08:00
|
|
|
This clock should be battery-backed, so that it reads the correct
|
2009-01-07 06:42:17 +08:00
|
|
|
time when the system boots from a power-off state. Otherwise, your
|
2007-05-08 15:33:42 +08:00
|
|
|
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
|
2008-02-06 17:38:40 +08:00
|
|
|
sleep states. Do not specify an RTC here unless it stays powered
|
2007-05-08 15:33:42 +08:00
|
|
|
during all this system's supported sleep states.
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2015-06-12 11:10:16 +08:00
|
|
|
config RTC_SYSTOHC
|
|
|
|
|
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 RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
|
|
|
|
|
minutes if userspace reports synchronized NTP status.
|
|
|
|
|
|
|
|
|
|
config RTC_SYSTOHC_DEVICE
|
|
|
|
|
string "RTC used to synchronize NTP adjustment"
|
|
|
|
|
depends on RTC_SYSTOHC
|
|
|
|
|
default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
|
|
|
|
|
default "rtc0"
|
|
|
|
|
help
|
|
|
|
|
The RTC device used for NTP synchronization. The main difference
|
|
|
|
|
between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
|
|
|
|
|
one can sleep when setting time, because it runs in the workqueue
|
|
|
|
|
context.
|
|
|
|
|
|
2006-10-01 14:28:14 +08:00
|
|
|
config RTC_DEBUG
|
|
|
|
|
bool "RTC debug support"
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable debugging support in the RTC framework
|
|
|
|
|
and individual RTC drivers.
|
|
|
|
|
|
2017-07-06 17:42:02 +08:00
|
|
|
config RTC_NVMEM
|
|
|
|
|
bool "RTC non volatile storage support"
|
|
|
|
|
select NVMEM
|
|
|
|
|
default RTC_CLASS
|
|
|
|
|
help
|
|
|
|
|
Say yes here to add support for the non volatile (often battery
|
|
|
|
|
backed) storage present on RTCs.
|
|
|
|
|
|
2006-03-27 17:16:37 +08:00
|
|
|
comment "RTC interfaces"
|
|
|
|
|
|
2006-03-27 17:16:39 +08:00
|
|
|
config RTC_INTF_SYSFS
|
2014-12-21 04:41:11 +08:00
|
|
|
bool "/sys/class/rtc/rtcN (sysfs)"
|
2007-07-31 15:39:46 +08:00
|
|
|
depends on SYSFS
|
2012-10-11 06:54:06 +08:00
|
|
|
default RTC_CLASS
|
2006-03-27 17:16:39 +08:00
|
|
|
help
|
2006-10-01 14:28:14 +08:00
|
|
|
Say yes here if you want to use your RTCs using sysfs interfaces,
|
|
|
|
|
/sys/class/rtc/rtc0 through /sys/.../rtcN.
|
2006-03-27 17:16:39 +08:00
|
|
|
|
2009-01-07 06:42:17 +08:00
|
|
|
If unsure, say Y.
|
2006-03-27 17:16:39 +08:00
|
|
|
|
2006-03-27 17:16:40 +08:00
|
|
|
config RTC_INTF_PROC
|
2014-12-21 04:41:11 +08:00
|
|
|
bool "/proc/driver/rtc (procfs for rtcN)"
|
2007-07-31 15:39:46 +08:00
|
|
|
depends on PROC_FS
|
2012-10-11 06:54:06 +08:00
|
|
|
default RTC_CLASS
|
2006-03-27 17:16:40 +08:00
|
|
|
help
|
2012-10-05 08:13:45 +08:00
|
|
|
Say yes here if you want to use your system clock RTC through
|
|
|
|
|
the proc interface, /proc/driver/rtc.
|
|
|
|
|
Other RTCs will not be available through that API.
|
|
|
|
|
If there is no RTC for the system clock, then the first RTC(rtc0)
|
|
|
|
|
is used by default.
|
2006-03-27 17:16:40 +08:00
|
|
|
|
2009-01-07 06:42:17 +08:00
|
|
|
If unsure, say Y.
|
2006-03-27 17:16:40 +08:00
|
|
|
|
2006-03-27 17:16:41 +08:00
|
|
|
config RTC_INTF_DEV
|
2014-12-21 04:41:11 +08:00
|
|
|
bool "/dev/rtcN (character devices)"
|
2012-10-11 06:54:06 +08:00
|
|
|
default RTC_CLASS
|
2006-03-27 17:16:41 +08:00
|
|
|
help
|
2006-10-01 14:28:14 +08:00
|
|
|
Say yes here if you want to use your RTCs using the /dev
|
|
|
|
|
interfaces, which "udev" sets up as /dev/rtc0 through
|
2009-01-07 06:42:17 +08:00
|
|
|
/dev/rtcN.
|
2006-03-27 17:16:41 +08:00
|
|
|
|
2009-01-07 06:42:17 +08:00
|
|
|
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.
|
2006-03-27 17:16:41 +08:00
|
|
|
|
2011-02-12 09:45:40 +08:00
|
|
|
config RTC_INTF_DEV_UIE_EMUL
|
|
|
|
|
bool "RTC UIE emulation on dev interface"
|
|
|
|
|
depends on RTC_INTF_DEV
|
|
|
|
|
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.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_TEST
|
|
|
|
|
tristate "Test driver/device"
|
2006-03-27 17:16:42 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2007-05-08 15:33:48 +08:00
|
|
|
RTC test driver. It's a software RTC which can be
|
|
|
|
|
used to test the RTC subsystem APIs. It gets
|
|
|
|
|
the time from the system clock.
|
|
|
|
|
You want this driver only if you are doing development
|
|
|
|
|
on the RTC subsystem. Please read the source code
|
|
|
|
|
for further details.
|
2006-03-27 17:16:42 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2007-05-08 15:33:48 +08:00
|
|
|
will be called rtc-test.
|
|
|
|
|
|
|
|
|
|
comment "I2C RTC drivers"
|
2007-07-31 15:39:46 +08:00
|
|
|
|
|
|
|
|
if I2C
|
2006-03-27 17:16:42 +08:00
|
|
|
|
2011-05-06 17:21:20 +08:00
|
|
|
config RTC_DRV_88PM860X
|
|
|
|
|
tristate "Marvell 88PM860x"
|
2015-06-09 01:27:37 +08:00
|
|
|
depends on MFD_88PM860X
|
2011-05-06 17:21:20 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for RTC function in Marvell
|
|
|
|
|
88PM860x chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-88pm860x.
|
|
|
|
|
|
2012-07-09 14:37:34 +08:00
|
|
|
config RTC_DRV_88PM80X
|
|
|
|
|
tristate "Marvell 88PM80x"
|
2015-06-09 01:27:37 +08:00
|
|
|
depends on MFD_88PM800
|
2012-07-09 14:37:34 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for RTC function in Marvell
|
|
|
|
|
88PM80x chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-88pm80x.
|
|
|
|
|
|
2015-02-14 06:41:00 +08:00
|
|
|
config RTC_DRV_ABB5ZES3
|
2015-05-10 03:21:54 +08:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
|
|
|
|
|
help
|
2015-02-14 06:41:00 +08:00
|
|
|
If you say yes here you get support for the Abracon
|
|
|
|
|
AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ab-b5ze-s3.
|
|
|
|
|
|
2015-05-06 07:23:44 +08:00
|
|
|
config RTC_DRV_ABX80X
|
|
|
|
|
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.
|
|
|
|
|
|
2016-07-08 22:33:38 +08:00
|
|
|
config RTC_DRV_AC100
|
|
|
|
|
tristate "X-Powers AC100"
|
|
|
|
|
depends on MFD_AC100
|
|
|
|
|
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.
|
|
|
|
|
|
2017-06-27 05:15:03 +08:00
|
|
|
config RTC_DRV_BRCMSTB
|
|
|
|
|
tristate "Broadcom STB wake-timer"
|
|
|
|
|
depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
|
|
|
|
|
default ARCH_BRCMSTB || BMIPS_GENERIC
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the wake-timer found on
|
|
|
|
|
Broadcom STB SoCs (BCM7xxx).
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module will
|
|
|
|
|
be called rtc-brcmstb-waketimer.
|
|
|
|
|
|
2013-11-13 07:11:05 +08:00
|
|
|
config RTC_DRV_AS3722
|
|
|
|
|
tristate "ams AS3722 RTC driver"
|
|
|
|
|
depends on MFD_AS3722
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC of ams AS3722 PMIC
|
|
|
|
|
chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-as3722.
|
|
|
|
|
|
2006-06-25 20:48:17 +08:00
|
|
|
config RTC_DRV_DS1307
|
rtc: ds1307: add basic support for ds1341 chip
This adds support for reading and writing date/time from/to ds1341 chip.
ds1341 chip has other features - alarms, input clock (can be used instead
of intercal oscillator for better accuracy), output clock ("square wave
generation"). However, not all of that is available at the same time.
Same chip pins, CLKIN/nINTA and SQW/nINTB, can be used either for
input/output clocks, or for alarm interrupts. Role of these pins on
particular board depends on hardware wiring.
We can add device tree properties that describe if each of pins is wired
as clock, or as interrupt, or left unconnected, and enable support for
corresponding functionality based on that. But that is cumbersome, requires
hardware for testing, and has to deal with bit enabling/disabling output
clock also affects which pins alarm interrupts are routed to.
Another factor is that there are hardware setups (i.e. ZII RDU2) that
power DS1341 from SuperCap, which makes power saving critical. For such
setups, kernel driver should leave register bits that control mentioned
pins in the state configured by bootloader.
Given all that, it was decided to limit support to "only date/time" for
now. That is enough for common use case. Full (and cumbersome)
implementation can be added later if ever needed.
Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Tested-by: Aleksander Morgado <aleksander@aleksander.es>
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
2017-08-24 14:32:11 +08:00
|
|
|
tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
|
2006-06-25 20:48:17 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for various compatible RTC
|
2009-01-07 06:42:17 +08:00
|
|
|
chips (often with battery backup) connected with I2C. This driver
|
rtc: ds1307: add basic support for ds1341 chip
This adds support for reading and writing date/time from/to ds1341 chip.
ds1341 chip has other features - alarms, input clock (can be used instead
of intercal oscillator for better accuracy), output clock ("square wave
generation"). However, not all of that is available at the same time.
Same chip pins, CLKIN/nINTA and SQW/nINTB, can be used either for
input/output clocks, or for alarm interrupts. Role of these pins on
particular board depends on hardware wiring.
We can add device tree properties that describe if each of pins is wired
as clock, or as interrupt, or left unconnected, and enable support for
corresponding functionality based on that. But that is cumbersome, requires
hardware for testing, and has to deal with bit enabling/disabling output
clock also affects which pins alarm interrupts are routed to.
Another factor is that there are hardware setups (i.e. ZII RDU2) that
power DS1341 from SuperCap, which makes power saving critical. For such
setups, kernel driver should leave register bits that control mentioned
pins in the state configured by bootloader.
Given all that, it was decided to limit support to "only date/time" for
now. That is enough for common use case. Full (and cumbersome)
implementation can be added later if ever needed.
Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Tested-by: Aleksander Morgado <aleksander@aleksander.es>
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
2017-08-24 14:32:11 +08:00
|
|
|
should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
|
|
|
|
|
ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
|
|
|
|
|
In some cases the RTC must already have been initialized (by
|
|
|
|
|
manufacturing or a bootloader).
|
2006-06-25 20:48:17 +08:00
|
|
|
|
|
|
|
|
The first seven registers on these chips hold an RTC, and other
|
|
|
|
|
registers may add features such as NVRAM, a trickle charger for
|
2009-01-07 06:42:17 +08:00
|
|
|
the RTC/NVRAM backup power, and alarms. NVRAM is visible in
|
2007-11-15 08:58:32 +08:00
|
|
|
sysfs, but other chip features may not be available.
|
2006-06-25 20:48:17 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ds1307.
|
|
|
|
|
|
2016-01-24 23:22:16 +08:00
|
|
|
config RTC_DRV_DS1307_HWMON
|
|
|
|
|
bool "HWMON support for rtc-ds1307"
|
|
|
|
|
depends on RTC_DRV_DS1307 && HWMON
|
|
|
|
|
depends on !(RTC_DRV_DS1307=y && HWMON=m)
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to expose temperature sensor data on
|
|
|
|
|
rtc-ds1307 (only DS3231)
|
|
|
|
|
|
2016-07-13 08:26:08 +08:00
|
|
|
config RTC_DRV_DS1307_CENTURY
|
|
|
|
|
bool "Century bit support for rtc-ds1307"
|
|
|
|
|
depends on RTC_DRV_DS1307
|
|
|
|
|
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 RTC date and then boot a kernel with this option set.
|
|
|
|
|
|
2007-10-16 16:28:19 +08:00
|
|
|
config RTC_DRV_DS1374
|
2008-02-06 17:38:40 +08:00
|
|
|
tristate "Dallas/Maxim DS1374"
|
2007-10-16 16:28:19 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for Dallas Semiconductor
|
2009-01-07 06:42:17 +08:00
|
|
|
DS1374 real-time clock chips. If an interrupt is associated
|
2007-10-16 16:28:19 +08:00
|
|
|
with the device, the alarm functionality is supported.
|
|
|
|
|
|
2009-01-07 06:42:17 +08:00
|
|
|
This driver can also be built as a module. If so, the module
|
2007-10-16 16:28:19 +08:00
|
|
|
will be called rtc-ds1374.
|
|
|
|
|
|
2014-12-11 07:53:54 +08:00
|
|
|
config RTC_DRV_DS1374_WDT
|
|
|
|
|
bool "Dallas/Maxim DS1374 watchdog timer"
|
|
|
|
|
depends on RTC_DRV_DS1374
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
|
|
|
|
watchdog timer in the Dallas Semiconductor DS1374
|
|
|
|
|
real-time clock chips.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_DS1672
|
|
|
|
|
tristate "Dallas/Maxim DS1672"
|
2006-06-25 20:48:28 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2007-05-08 15:33:48 +08:00
|
|
|
Dallas/Maxim DS1672 timekeeping chip.
|
2006-06-25 20:48:28 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2007-05-08 15:33:48 +08:00
|
|
|
will be called rtc-ds1672.
|
2006-06-25 20:48:28 +08:00
|
|
|
|
2014-01-24 07:55:10 +08:00
|
|
|
config RTC_DRV_HYM8563
|
|
|
|
|
tristate "Haoyu Microelectronics HYM8563"
|
2015-06-09 01:27:37 +08:00
|
|
|
depends on OF
|
2014-01-24 07:55:10 +08:00
|
|
|
help
|
|
|
|
|
Say Y to enable support for the HYM8563 I2C RTC 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.
|
|
|
|
|
|
2013-02-22 08:44:32 +08:00
|
|
|
config RTC_DRV_LP8788
|
|
|
|
|
tristate "TI LP8788 RTC driver"
|
|
|
|
|
depends on MFD_LP8788
|
|
|
|
|
help
|
|
|
|
|
Say Y to enable support for the LP8788 RTC/ALARM driver.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_MAX6900
|
2008-02-06 17:38:40 +08:00
|
|
|
tristate "Maxim MAX6900"
|
2006-07-14 15:24:11 +08:00
|
|
|
help
|
2007-05-08 15:33:48 +08:00
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
Maxim MAX6900 I2C RTC chip.
|
2006-07-14 15:24:11 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2007-05-08 15:33:48 +08:00
|
|
|
will be called rtc-max6900.
|
2006-07-14 15:24:11 +08:00
|
|
|
|
2012-10-05 08:13:56 +08:00
|
|
|
config RTC_DRV_MAX8907
|
|
|
|
|
tristate "Maxim MAX8907"
|
2016-10-03 04:58:16 +08:00
|
|
|
depends on MFD_MAX8907 || COMPILE_TEST
|
2012-10-05 08:13:56 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
RTC of Maxim MAX8907 PMIC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-max8907.
|
|
|
|
|
|
2010-01-25 19:30:29 +08:00
|
|
|
config RTC_DRV_MAX8925
|
|
|
|
|
tristate "Maxim MAX8925"
|
|
|
|
|
depends on MFD_MAX8925
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
RTC of Maxim MAX8925 PMIC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-max8925.
|
|
|
|
|
|
2010-08-06 10:28:08 +08:00
|
|
|
config RTC_DRV_MAX8998
|
|
|
|
|
tristate "Maxim MAX8998"
|
|
|
|
|
depends on MFD_MAX8998
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
RTC of Maxim MAX8998 PMIC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-max8998.
|
|
|
|
|
|
2013-02-22 08:45:07 +08:00
|
|
|
config RTC_DRV_MAX8997
|
|
|
|
|
tristate "Maxim MAX8997"
|
|
|
|
|
depends on MFD_MAX8997
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
RTC of Maxim MAX8997 PMIC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-max8997.
|
|
|
|
|
|
2013-02-22 08:44:26 +08:00
|
|
|
config RTC_DRV_MAX77686
|
|
|
|
|
tristate "Maxim MAX77686"
|
2016-10-03 04:58:16 +08:00
|
|
|
depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
|
2013-02-22 08:44:26 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
2016-03-02 16:36:24 +08:00
|
|
|
RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
|
2013-02-22 08:44:26 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-max77686.
|
|
|
|
|
|
2014-10-14 06:52:42 +08:00
|
|
|
config RTC_DRV_RK808
|
2017-08-16 10:00:35 +08:00
|
|
|
tristate "Rockchip RK805/RK808/RK818 RTC"
|
2014-10-14 06:52:42 +08:00
|
|
|
depends on MFD_RK808
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
2017-08-16 10:00:35 +08:00
|
|
|
RTC of RK805, RK808 and RK818 PMIC.
|
2014-10-14 06:52:42 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rk808-rtc.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_RS5C372
|
2008-10-21 19:12:59 +08:00
|
|
|
tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
|
2006-03-27 17:16:43 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2008-10-21 19:12:59 +08:00
|
|
|
Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
|
2006-03-27 17:16:43 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2007-05-08 15:33:48 +08:00
|
|
|
will be called rtc-rs5c372.
|
2006-03-27 17:16:43 +08:00
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_ISL1208
|
2008-02-06 17:38:40 +08:00
|
|
|
tristate "Intersil ISL1208"
|
2006-06-25 20:48:29 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2008-02-06 17:38:40 +08:00
|
|
|
Intersil ISL1208 RTC chip.
|
2006-06-25 20:48:29 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2007-05-08 15:33:48 +08:00
|
|
|
will be called rtc-isl1208.
|
2006-06-25 20:48:29 +08:00
|
|
|
|
2010-08-11 09:02:14 +08:00
|
|
|
config RTC_DRV_ISL12022
|
|
|
|
|
tristate "Intersil ISL12022"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Intersil ISL12022 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-isl12022.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_X1205
|
|
|
|
|
tristate "Xicor/Intersil X1205"
|
2006-12-07 12:38:36 +08:00
|
|
|
help
|
2007-05-08 15:33:48 +08:00
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Xicor/Intersil X1205 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-x1205.
|
2006-12-07 12:38:36 +08:00
|
|
|
|
2012-12-18 08:02:44 +08:00
|
|
|
config RTC_DRV_PCF8523
|
|
|
|
|
tristate "NXP PCF8523"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the NXP PCF8523 RTC
|
|
|
|
|
chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-pcf8523.
|
|
|
|
|
|
2015-11-04 15:13:46 +08:00
|
|
|
config RTC_DRV_PCF85063
|
|
|
|
|
tristate "NXP PCF85063"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the PCF85063 RTC chip
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-pcf85063.
|
|
|
|
|
|
2006-03-27 17:16:44 +08:00
|
|
|
config RTC_DRV_PCF8563
|
|
|
|
|
tristate "Philips PCF8563/Epson RTC8564"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Philips PCF8563 RTC 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.
|
|
|
|
|
|
2006-06-25 20:48:18 +08:00
|
|
|
config RTC_DRV_PCF8583
|
|
|
|
|
tristate "Philips PCF8583"
|
|
|
|
|
help
|
2007-03-05 04:33:07 +08:00
|
|
|
If you say yes here you get support for the Philips PCF8583
|
2007-05-08 15:33:48 +08:00
|
|
|
RTC chip found on Acorn RiscPCs. This driver supports the
|
2007-03-05 04:33:07 +08:00
|
|
|
platform specific method of retrieving the current year from
|
2007-05-08 15:33:48 +08:00
|
|
|
the RTC's SRAM. It will work on other platforms with the same
|
|
|
|
|
chip, but the year will probably have to be tweaked.
|
2006-06-25 20:48:18 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-pcf8583.
|
|
|
|
|
|
2007-07-17 19:05:02 +08:00
|
|
|
config RTC_DRV_M41T80
|
2014-06-07 05:35:47 +08:00
|
|
|
tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
|
2007-07-17 19:05:02 +08:00
|
|
|
help
|
2008-10-16 13:03:07 +08:00
|
|
|
If you say Y here you will get support for the ST M41T60
|
|
|
|
|
and M41T80 RTC chips series. Currently, the following chips are
|
2009-04-03 07:57:03 +08:00
|
|
|
supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
|
2014-06-07 05:35:47 +08:00
|
|
|
M41ST85, M41ST87, and MicroCrystal RV4162.
|
2007-07-17 19:05:02 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-m41t80.
|
|
|
|
|
|
2007-07-17 19:05:04 +08:00
|
|
|
config RTC_DRV_M41T80_WDT
|
2008-10-16 13:03:07 +08:00
|
|
|
bool "ST M41T65/M41T80 series RTC watchdog timer"
|
2007-07-17 19:05:04 +08:00
|
|
|
depends on RTC_DRV_M41T80
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
2008-10-16 13:03:07 +08:00
|
|
|
watchdog timer in the ST M41T60 and M41T80 RTC chips series.
|
2007-07-17 19:05:04 +08:00
|
|
|
|
2009-12-16 08:46:12 +08:00
|
|
|
config RTC_DRV_BQ32K
|
|
|
|
|
tristate "TI BQ32000"
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the TI
|
|
|
|
|
BQ32000 I2C RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-bq32k.
|
|
|
|
|
|
2009-02-05 07:12:01 +08:00
|
|
|
config RTC_DRV_DM355EVM
|
|
|
|
|
tristate "TI DaVinci DM355 EVM RTC"
|
|
|
|
|
depends on MFD_DM355EVM_MSP
|
|
|
|
|
help
|
|
|
|
|
Supports the RTC firmware in the MSP430 on the DM355 EVM.
|
|
|
|
|
|
2007-07-17 19:06:09 +08:00
|
|
|
config RTC_DRV_TWL92330
|
2014-12-21 04:41:11 +08:00
|
|
|
bool "TI TWL92330/Menelaus"
|
2007-07-31 15:39:46 +08:00
|
|
|
depends on MENELAUS
|
2007-07-17 19:06:09 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC on the
|
2007-10-20 07:34:40 +08:00
|
|
|
TWL92330 "Menelaus" power management chip, used with OMAP2
|
2009-01-07 06:42:17 +08:00
|
|
|
platforms. The support is integrated with the rest of
|
2007-07-17 19:06:09 +08:00
|
|
|
the Menelaus driver; it's not separate module.
|
|
|
|
|
|
2008-10-21 05:50:05 +08:00
|
|
|
config RTC_DRV_TWL4030
|
2009-12-14 05:16:31 +08:00
|
|
|
tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
|
2012-10-05 08:13:59 +08:00
|
|
|
depends on TWL4030_CORE
|
2016-11-23 16:55:57 +08:00
|
|
|
depends on OF
|
2008-10-21 05:50:05 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC on the
|
2009-12-14 05:16:31 +08:00
|
|
|
TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
|
2008-10-21 05:50:05 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2009-12-14 05:16:31 +08:00
|
|
|
will be called rtc-twl.
|
2008-10-21 05:50:05 +08:00
|
|
|
|
2015-11-04 15:13:46 +08:00
|
|
|
config RTC_DRV_PALMAS
|
|
|
|
|
tristate "TI Palmas RTC driver"
|
|
|
|
|
depends on MFD_PALMAS
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC of TI PALMA series PMIC
|
|
|
|
|
chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-palma.
|
|
|
|
|
|
2013-01-05 07:35:44 +08:00
|
|
|
config RTC_DRV_TPS6586X
|
|
|
|
|
tristate "TI TPS6586X RTC driver"
|
|
|
|
|
depends on MFD_TPS6586X
|
|
|
|
|
help
|
2013-04-09 01:06:50 +08:00
|
|
|
TI Power Management IC TPS6586X supports RTC functionality
|
2013-01-05 07:35:44 +08:00
|
|
|
along with alarm. This driver supports the RTC driver for
|
|
|
|
|
the TPS6586X RTC module.
|
|
|
|
|
|
2012-10-05 08:13:55 +08:00
|
|
|
config RTC_DRV_TPS65910
|
|
|
|
|
tristate "TI TPS65910 RTC driver"
|
|
|
|
|
depends on RTC_CLASS && MFD_TPS65910
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC on the
|
|
|
|
|
TPS65910 chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-tps65910.
|
|
|
|
|
|
2013-02-22 08:44:34 +08:00
|
|
|
config RTC_DRV_TPS80031
|
|
|
|
|
tristate "TI TPS80031/TPS80032 RTC driver"
|
|
|
|
|
depends on MFD_TPS80031
|
|
|
|
|
help
|
2013-04-09 01:06:50 +08:00
|
|
|
TI Power Management IC TPS80031 supports RTC functionality
|
2013-02-22 08:44:34 +08:00
|
|
|
along with alarm. This driver supports the RTC driver for
|
|
|
|
|
the TPS80031 RTC module.
|
|
|
|
|
|
2012-10-05 08:14:04 +08:00
|
|
|
config RTC_DRV_RC5T583
|
|
|
|
|
tristate "RICOH 5T583 RTC driver"
|
|
|
|
|
depends on MFD_RC5T583
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC on the
|
|
|
|
|
RICOH 5T583 chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-rc5t583.
|
|
|
|
|
|
2008-03-05 06:28:25 +08:00
|
|
|
config RTC_DRV_S35390A
|
|
|
|
|
tristate "Seiko Instruments S-35390A"
|
2008-04-11 12:29:18 +08:00
|
|
|
select BITREVERSE
|
2008-03-05 06:28:25 +08:00
|
|
|
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.
|
|
|
|
|
|
2008-06-13 06:21:55 +08:00
|
|
|
config RTC_DRV_FM3130
|
|
|
|
|
tristate "Ramtron FM3130"
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
|
|
|
|
Ramtron FM3130 RTC chips.
|
|
|
|
|
Ramtron FM3130 is a chip with two separate devices inside,
|
|
|
|
|
RTC clock and FRAM. This driver provides only RTC functionality.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so the module
|
|
|
|
|
will be called rtc-fm3130.
|
|
|
|
|
|
2015-12-04 03:41:21 +08:00
|
|
|
config RTC_DRV_RX8010
|
|
|
|
|
tristate "Epson RX8010SJ"
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Epson RX8010SJ RTC
|
|
|
|
|
chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-rx8010.
|
|
|
|
|
|
2008-11-13 05:27:06 +08:00
|
|
|
config RTC_DRV_RX8581
|
|
|
|
|
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.
|
|
|
|
|
|
2009-06-18 07:26:11 +08:00
|
|
|
config RTC_DRV_RX8025
|
|
|
|
|
tristate "Epson RX-8025SA/NB"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Epson
|
|
|
|
|
RX-8025SA/NB RTC chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-rx8025.
|
|
|
|
|
|
2011-05-27 07:25:04 +08:00
|
|
|
config RTC_DRV_EM3027
|
|
|
|
|
tristate "EM Microelectronic EM3027"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the EM
|
|
|
|
|
Microelectronic EM3027 RTC chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-em3027.
|
|
|
|
|
|
2015-11-03 06:48:32 +08:00
|
|
|
config RTC_DRV_RV8803
|
2016-07-21 18:41:27 +08:00
|
|
|
tristate "Micro Crystal RV8803, Epson RX8900"
|
2015-11-03 06:48:32 +08:00
|
|
|
help
|
2016-07-21 18:41:27 +08:00
|
|
|
If you say yes here you get support for the Micro Crystal RV8803 and
|
|
|
|
|
Epson RX8900 RTC chips.
|
2015-11-03 06:48:32 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-rv8803.
|
|
|
|
|
|
2013-11-13 07:11:04 +08:00
|
|
|
config RTC_DRV_S5M
|
2014-06-11 06:18:46 +08:00
|
|
|
tristate "Samsung S2M/S5M series"
|
2016-10-03 04:58:16 +08:00
|
|
|
depends on MFD_SEC_CORE || COMPILE_TEST
|
|
|
|
|
select REGMAP_IRQ
|
2013-11-13 07:11:04 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
2014-06-11 06:18:46 +08:00
|
|
|
RTC of Samsung S2MPS14 and S5M PMIC series.
|
2013-11-13 07:11:04 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-s5m.
|
|
|
|
|
|
2007-07-31 15:39:46 +08:00
|
|
|
endif # I2C
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
comment "SPI RTC drivers"
|
2007-07-31 15:39:46 +08:00
|
|
|
|
|
|
|
|
if SPI_MASTER
|
2007-05-08 15:33:48 +08:00
|
|
|
|
2011-05-27 07:25:07 +08:00
|
|
|
config RTC_DRV_M41T93
|
2015-05-10 03:21:54 +08:00
|
|
|
tristate "ST M41T93"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
ST M41T93 SPI RTC chip.
|
2011-05-27 07:25:07 +08:00
|
|
|
|
2015-05-10 03:21:54 +08:00
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-m41t93.
|
2011-05-27 07:25:07 +08:00
|
|
|
|
2008-07-24 12:30:34 +08:00
|
|
|
config RTC_DRV_M41T94
|
|
|
|
|
tristate "ST M41T94"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
ST M41T94 SPI RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-m41t94.
|
|
|
|
|
|
2016-02-23 18:54:57 +08:00
|
|
|
config RTC_DRV_DS1302
|
|
|
|
|
tristate "Dallas/Maxim DS1302"
|
|
|
|
|
depends on SPI
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Dallas DS1302 RTC chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ds1302.
|
|
|
|
|
|
2008-07-24 12:30:36 +08:00
|
|
|
config RTC_DRV_DS1305
|
|
|
|
|
tristate "Dallas/Maxim DS1305/DS1306"
|
|
|
|
|
help
|
|
|
|
|
Select this driver to get support for the Dallas/Maxim DS1305
|
2009-01-07 06:42:17 +08:00
|
|
|
and DS1306 real time clock chips. These support a trickle
|
2008-07-24 12:30:36 +08:00
|
|
|
charger, alarms, and NVRAM in addition to the clock.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ds1305.
|
|
|
|
|
|
2014-06-07 05:35:59 +08:00
|
|
|
config RTC_DRV_DS1343
|
2014-06-07 05:36:00 +08:00
|
|
|
select REGMAP_SPI
|
2014-06-07 05:35:59 +08:00
|
|
|
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.
|
|
|
|
|
|
2014-04-04 05:50:16 +08:00
|
|
|
config RTC_DRV_DS1347
|
2016-09-01 01:26:41 +08:00
|
|
|
select REGMAP_SPI
|
2014-04-04 05:50:16 +08:00
|
|
|
tristate "Dallas/Maxim DS1347"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Dallas/Maxim DS1347 chips.
|
|
|
|
|
|
|
|
|
|
This driver only supports the RTC 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.
|
|
|
|
|
|
2008-11-13 05:27:07 +08:00
|
|
|
config RTC_DRV_DS1390
|
|
|
|
|
tristate "Dallas/Maxim DS1390/93/94"
|
|
|
|
|
help
|
2009-01-07 06:42:16 +08:00
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Dallas/Maxim DS1390/93/94 chips.
|
2008-11-13 05:27:07 +08:00
|
|
|
|
2015-09-18 23:27:57 +08:00
|
|
|
This driver supports the RTC feature and trickle charging but not
|
|
|
|
|
other chip features such as alarms.
|
2008-11-13 05:27:07 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ds1390.
|
|
|
|
|
|
2016-06-01 14:29:54 +08:00
|
|
|
config RTC_DRV_MAX6916
|
|
|
|
|
tristate "Maxim MAX6916"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
Maxim MAX6916 SPI RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver only supports the RTC 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.
|
|
|
|
|
|
2008-02-06 17:38:53 +08:00
|
|
|
config RTC_DRV_R9701
|
|
|
|
|
tristate "Epson RTC-9701JE"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
Epson RTC-9701JE SPI RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-r9701.
|
|
|
|
|
|
2015-11-04 15:13:46 +08:00
|
|
|
config RTC_DRV_RX4581
|
|
|
|
|
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 RTC_DRV_RX6110
|
|
|
|
|
tristate "Epson RX-6110"
|
|
|
|
|
select REGMAP_SPI
|
|
|
|
|
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.
|
|
|
|
|
|
2006-06-28 19:26:47 +08:00
|
|
|
config RTC_DRV_RS5C348
|
|
|
|
|
tristate "Ricoh RS5C348A/B"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Ricoh RS5C348A and RS5C348B RTC chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-rs5c348.
|
|
|
|
|
|
2015-11-04 15:13:46 +08:00
|
|
|
config RTC_DRV_MAX6902
|
|
|
|
|
tristate "Maxim MAX6902"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
Maxim MAX6902 SPI RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-max6902.
|
|
|
|
|
|
2009-09-23 07:46:20 +08:00
|
|
|
config RTC_DRV_PCF2123
|
|
|
|
|
tristate "NXP PCF2123"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the NXP PCF2123
|
|
|
|
|
RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-pcf2123.
|
|
|
|
|
|
2014-06-07 05:36:02 +08:00
|
|
|
config RTC_DRV_MCP795
|
|
|
|
|
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.
|
|
|
|
|
|
2007-07-31 15:39:46 +08:00
|
|
|
endif # SPI_MASTER
|
|
|
|
|
|
2016-03-06 23:27:48 +08:00
|
|
|
#
|
|
|
|
|
# Helper to resolve issues with configs that have SPI enabled but I2C
|
|
|
|
|
# modular. See SND_SOC_I2C_AND_SPI for more information
|
|
|
|
|
#
|
|
|
|
|
config RTC_I2C_AND_SPI
|
|
|
|
|
tristate
|
|
|
|
|
default m if I2C=m
|
|
|
|
|
default y if I2C=y
|
|
|
|
|
default y if SPI_MASTER=y
|
|
|
|
|
select REGMAP_I2C if I2C
|
|
|
|
|
select REGMAP_SPI if SPI_MASTER
|
|
|
|
|
|
|
|
|
|
comment "SPI and I2C RTC drivers"
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_DS3232
|
|
|
|
|
tristate "Dallas/Maxim DS3232/DS3234"
|
|
|
|
|
depends on RTC_I2C_AND_SPI
|
|
|
|
|
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.
|
|
|
|
|
|
2017-06-28 19:29:09 +08:00
|
|
|
config RTC_DRV_DS3232_HWMON
|
|
|
|
|
bool "HWMON support for Dallas/Maxim DS3232/DS3234"
|
|
|
|
|
depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to expose temperature sensor data on
|
|
|
|
|
rtc-ds3232
|
|
|
|
|
|
2016-03-14 22:45:00 +08:00
|
|
|
config RTC_DRV_PCF2127
|
|
|
|
|
tristate "NXP PCF2127"
|
|
|
|
|
depends on RTC_I2C_AND_SPI
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the NXP PCF2127/29 RTC
|
|
|
|
|
chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-pcf2127.
|
|
|
|
|
|
2016-05-03 17:54:34 +08:00
|
|
|
config RTC_DRV_RV3029C2
|
|
|
|
|
tristate "Micro Crystal RV3029/3049"
|
|
|
|
|
depends on RTC_I2C_AND_SPI
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Micro Crystal
|
|
|
|
|
RV3029 and RV3049 RTC chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-rv3029c2.
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_RV3029_HWMON
|
|
|
|
|
bool "HWMON support for RV3029/3049"
|
|
|
|
|
depends on RTC_DRV_RV3029C2 && HWMON
|
|
|
|
|
depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to expose temperature sensor data on
|
|
|
|
|
rtc-rv3029.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
comment "Platform RTC drivers"
|
|
|
|
|
|
2016-10-12 21:30:53 +08:00
|
|
|
# this 'CMOS' RTC driver is arch dependent because it requires
|
|
|
|
|
# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
|
2007-05-08 15:33:48 +08:00
|
|
|
# global rtc_lock ... it's not yet just another platform_device.
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_CMOS
|
|
|
|
|
tristate "PC-style 'CMOS'"
|
2016-06-01 22:46:22 +08:00
|
|
|
depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
|
2008-04-28 17:11:52 +08:00
|
|
|
default y if X86
|
2016-06-01 22:46:23 +08:00
|
|
|
select RTC_MC146818_LIB
|
2007-05-08 15:33:48 +08:00
|
|
|
help
|
|
|
|
|
Say "yes" here to get direct support for the real time clock
|
|
|
|
|
found in every PC or ACPI-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
|
2009-01-07 06:42:17 +08:00
|
|
|
this driver, otherwise it won't be accessible. This means
|
2007-05-08 15:33:48 +08:00
|
|
|
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.
|
|
|
|
|
|
2013-07-14 06:49:45 +08:00
|
|
|
config RTC_DRV_ALPHA
|
|
|
|
|
bool "Alpha PC-style CMOS"
|
|
|
|
|
depends on ALPHA
|
2016-06-01 22:46:23 +08:00
|
|
|
select RTC_MC146818_LIB
|
2013-07-14 06:49:45 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Direct support for the real-time clock found on every Alpha
|
|
|
|
|
system, specifically MC146818 compatibles. If in doubt, say Y.
|
|
|
|
|
|
2010-11-11 01:29:17 +08:00
|
|
|
config RTC_DRV_VRTC
|
2011-12-18 01:43:40 +08:00
|
|
|
tristate "Virtual RTC for Intel MID platforms"
|
|
|
|
|
depends on X86_INTEL_MID
|
|
|
|
|
default y if X86_INTEL_MID
|
2010-11-11 01:29:17 +08:00
|
|
|
|
|
|
|
|
help
|
|
|
|
|
Say "yes" here to get direct support for the real time clock
|
|
|
|
|
found on Moorestown platforms. The VRTC is a emulated RTC that
|
|
|
|
|
derives its clock source from a real RTC in the PMIC. The MC146818
|
|
|
|
|
style programming interface is mostly conserved, but any
|
|
|
|
|
updates are done via IPC calls to the system controller FW.
|
|
|
|
|
|
2007-07-17 19:05:06 +08:00
|
|
|
config RTC_DRV_DS1216
|
|
|
|
|
tristate "Dallas DS1216"
|
2007-07-31 15:39:46 +08:00
|
|
|
depends on SNI_RM
|
2007-07-17 19:05:06 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Dallas DS1216 RTC chips.
|
|
|
|
|
|
2008-10-14 23:16:59 +08:00
|
|
|
config RTC_DRV_DS1286
|
|
|
|
|
tristate "Dallas DS1286"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2008-10-14 23:16:59 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Dallas DS1286 RTC chips.
|
|
|
|
|
|
2008-02-06 17:38:46 +08:00
|
|
|
config RTC_DRV_DS1511
|
|
|
|
|
tristate "Dallas DS1511"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2008-02-06 17:38:46 +08:00
|
|
|
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.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_DS1553
|
2008-02-06 17:38:40 +08:00
|
|
|
tristate "Maxim/Dallas DS1553"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2006-03-27 17:16:45 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2008-02-06 17:38:40 +08:00
|
|
|
Maxim/Dallas DS1553 timekeeping chip.
|
2006-03-27 17:16:45 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2007-05-08 15:33:48 +08:00
|
|
|
will be called rtc-ds1553.
|
|
|
|
|
|
2015-02-17 08:00:26 +08:00
|
|
|
config RTC_DRV_DS1685_FAMILY
|
|
|
|
|
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 RTC_DRV_DS1685_FAMILY
|
|
|
|
|
default RTC_DRV_DS1685
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_DS1685
|
|
|
|
|
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 RTC_DRV_DS1689
|
|
|
|
|
bool "DS1689/DS1693"
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Dallas/Maxim DS1689/DS1693 real time
|
|
|
|
|
clock chip.
|
|
|
|
|
|
|
|
|
|
This is an older RTC 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 ROM/Serial number.
|
|
|
|
|
|
|
|
|
|
It also works for the even older DS1688/DS1691 RTC chips, which are
|
|
|
|
|
virtually the same and carry the same model number. Both chips
|
|
|
|
|
have 114 bytes of user NVRAM.
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_DS17285
|
|
|
|
|
bool "DS17285/DS17287"
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Dallas/Maxim DS17285/DS17287 real time
|
|
|
|
|
clock chip.
|
|
|
|
|
|
|
|
|
|
This chip features 2kb of extended NV-SRAM. It may possibly be
|
|
|
|
|
found in some SGI O2 systems (rare).
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_DS17485
|
|
|
|
|
bool "DS17485/DS17487"
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Dallas/Maxim DS17485/DS17487 real time
|
|
|
|
|
clock chip.
|
|
|
|
|
|
|
|
|
|
This chip features 4kb of extended NV-SRAM.
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_DS17885
|
|
|
|
|
bool "DS17885/DS17887"
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Dallas/Maxim DS17885/DS17887 real time
|
|
|
|
|
clock chip.
|
|
|
|
|
|
|
|
|
|
This chip features 8kb of extended NV-SRAM.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config RTC_DS1685_PROC_REGS
|
|
|
|
|
bool "Display register values in /proc"
|
|
|
|
|
depends on RTC_DRV_DS1685_FAMILY && PROC_FS
|
|
|
|
|
help
|
|
|
|
|
Enable this to display a readout of all of the RTC registers in
|
|
|
|
|
/proc/drivers/rtc. Keep in mind that this can potentially lead
|
|
|
|
|
to lost interrupts, as reading Control Register C will clear
|
|
|
|
|
all pending IRQ flags.
|
|
|
|
|
|
|
|
|
|
Unless you are debugging this driver, choose N.
|
|
|
|
|
|
|
|
|
|
config RTC_DS1685_SYSFS_REGS
|
|
|
|
|
bool "SysFS access to RTC register bits"
|
|
|
|
|
depends on RTC_DRV_DS1685_FAMILY && SYSFS
|
|
|
|
|
help
|
|
|
|
|
Enable this to provide access to the RTC control register bits
|
|
|
|
|
in /sys. Some of the bits are read-write, others are read-only.
|
|
|
|
|
|
|
|
|
|
Keep in mind that reading Control C'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.
|
|
|
|
|
|
2008-02-06 17:38:40 +08:00
|
|
|
config RTC_DRV_DS1742
|
|
|
|
|
tristate "Maxim/Dallas DS1742/1743"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2007-07-21 19:37:58 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2008-02-06 17:38:40 +08:00
|
|
|
Maxim/Dallas DS1742/1743 timekeeping chip.
|
2007-07-21 19:37:58 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2008-02-06 17:38:40 +08:00
|
|
|
will be called rtc-ds1742.
|
2007-07-21 19:37:58 +08:00
|
|
|
|
2014-08-09 05:20:03 +08:00
|
|
|
config RTC_DRV_DS2404
|
|
|
|
|
tristate "Maxim/Dallas DS2404"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Dallas DS2404 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ds2404.
|
|
|
|
|
|
2012-03-24 06:02:36 +08:00
|
|
|
config RTC_DRV_DA9052
|
|
|
|
|
tristate "Dialog DA9052/DA9053 RTC"
|
|
|
|
|
depends on PMIC_DA9052
|
|
|
|
|
help
|
|
|
|
|
Say y here to support the RTC driver for Dialog Semiconductor
|
|
|
|
|
DA9052-BC and DA9053-AA/Bx PMICs.
|
|
|
|
|
|
2012-12-18 08:02:53 +08:00
|
|
|
config RTC_DRV_DA9055
|
|
|
|
|
tristate "Dialog Semiconductor DA9055 RTC"
|
|
|
|
|
depends on MFD_DA9055
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
RTC of the Dialog DA9055 PMIC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-da9055
|
|
|
|
|
|
2014-06-07 05:36:03 +08:00
|
|
|
config RTC_DRV_DA9063
|
2015-07-21 18:29:07 +08:00
|
|
|
tristate "Dialog Semiconductor DA9063/DA9062 RTC"
|
|
|
|
|
depends on MFD_DA9063 || MFD_DA9062
|
2014-06-07 05:36:03 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the RTC subsystem
|
2015-07-21 18:29:07 +08:00
|
|
|
for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
|
2014-06-07 05:36:03 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called "rtc-da9063".
|
|
|
|
|
|
2009-04-01 06:24:48 +08:00
|
|
|
config RTC_DRV_EFI
|
|
|
|
|
tristate "EFI RTC"
|
2014-10-03 20:06:33 +08:00
|
|
|
depends on EFI && !X86
|
2009-04-01 06:24:48 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the EFI
|
|
|
|
|
Real Time Clock.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-efi.
|
|
|
|
|
|
2008-02-06 17:38:40 +08:00
|
|
|
config RTC_DRV_STK17TA8
|
|
|
|
|
tristate "Simtek STK17TA8"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2007-05-08 15:33:48 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
2008-02-06 17:38:40 +08:00
|
|
|
Simtek STK17TA8 timekeeping chip.
|
2007-05-08 15:33:48 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2008-02-06 17:38:40 +08:00
|
|
|
will be called rtc-stk17ta8.
|
2007-05-08 15:33:48 +08:00
|
|
|
|
|
|
|
|
config RTC_DRV_M48T86
|
|
|
|
|
tristate "ST M48T86/Dallas DS12887"
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
|
|
|
|
ST M48T86 and Dallas DS12887 RTC chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-m48t86.
|
|
|
|
|
|
2008-10-14 23:17:32 +08:00
|
|
|
config RTC_DRV_M48T35
|
|
|
|
|
tristate "ST M48T35"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2008-10-14 23:17:32 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
|
|
|
|
ST M48T35 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-m48t35".
|
|
|
|
|
|
2007-07-17 19:05:05 +08:00
|
|
|
config RTC_DRV_M48T59
|
2008-09-04 06:12:34 +08:00
|
|
|
tristate "ST M48T59/M48T08/M48T02"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2007-07-17 19:05:05 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
2008-09-04 06:12:34 +08:00
|
|
|
ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
|
|
|
|
|
|
|
|
|
|
These chips are usually found in Sun SPARC and UltraSPARC
|
|
|
|
|
workstations.
|
2007-07-17 19:05:05 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-m48t59".
|
|
|
|
|
|
2009-03-19 06:29:27 +08:00
|
|
|
config RTC_DRV_MSM6242
|
|
|
|
|
tristate "Oki MSM6242"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2009-03-19 06:29:27 +08:00
|
|
|
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.
|
|
|
|
|
|
2008-08-29 16:29:53 +08:00
|
|
|
config RTC_DRV_BQ4802
|
|
|
|
|
tristate "TI BQ4802"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2008-08-29 16:29:53 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the TI
|
|
|
|
|
BQ4802 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-bq4802.
|
|
|
|
|
|
2009-03-19 06:29:27 +08:00
|
|
|
config RTC_DRV_RP5C01
|
|
|
|
|
tristate "Ricoh RP5C01"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2009-03-19 06:29:27 +08:00
|
|
|
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.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_V3020
|
|
|
|
|
tristate "EM Microelectronic V3020"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
|
|
|
|
EM Microelectronic v3020 RTC chip.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-v3020.
|
|
|
|
|
|
2009-08-28 01:59:05 +08:00
|
|
|
config RTC_DRV_WM831X
|
|
|
|
|
tristate "Wolfson Microelectronics WM831x RTC"
|
|
|
|
|
depends on MFD_WM831X
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the RTC 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".
|
|
|
|
|
|
2008-11-13 05:27:04 +08:00
|
|
|
config RTC_DRV_WM8350
|
|
|
|
|
tristate "Wolfson Microelectronics WM8350 RTC"
|
|
|
|
|
depends on MFD_WM8350
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the RTC subsystem
|
|
|
|
|
of the Wolfson Microelectronics WM8350.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called "rtc-wm8350".
|
|
|
|
|
|
2011-05-27 07:25:09 +08:00
|
|
|
config RTC_DRV_SPEAR
|
|
|
|
|
tristate "SPEAR ST RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on PLAT_SPEAR || COMPILE_TEST
|
2011-05-27 07:25:09 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the RTC found on
|
|
|
|
|
spear
|
|
|
|
|
|
2009-01-09 08:50:51 +08:00
|
|
|
config RTC_DRV_PCF50633
|
|
|
|
|
depends on MFD_PCF50633
|
|
|
|
|
tristate "NXP PCF50633 RTC"
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC subsystem of the
|
|
|
|
|
NXP PCF50633 used in embedded systems.
|
|
|
|
|
|
2009-08-31 05:49:04 +08:00
|
|
|
config RTC_DRV_AB3100
|
|
|
|
|
tristate "ST-Ericsson AB3100 RTC"
|
|
|
|
|
depends on AB3100_CORE
|
|
|
|
|
default y if AB3100_CORE
|
|
|
|
|
help
|
|
|
|
|
Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
|
|
|
|
|
support. This chip contains a battery- and capacitor-backed RTC.
|
|
|
|
|
|
2010-05-27 05:42:14 +08:00
|
|
|
config RTC_DRV_AB8500
|
|
|
|
|
tristate "ST-Ericsson AB8500 RTC"
|
|
|
|
|
depends on AB8500_CORE
|
2012-10-05 08:14:32 +08:00
|
|
|
select RTC_INTF_DEV
|
2012-07-31 05:41:41 +08:00
|
|
|
select RTC_INTF_DEV_UIE_EMUL
|
2010-05-27 05:42:14 +08:00
|
|
|
help
|
|
|
|
|
Select this to enable the ST-Ericsson AB8500 power management IC RTC
|
|
|
|
|
support. This chip contains a battery- and capacitor-backed RTC.
|
|
|
|
|
|
2009-12-16 08:46:17 +08:00
|
|
|
config RTC_DRV_NUC900
|
|
|
|
|
tristate "NUC910/NUC920 RTC driver"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_W90X900 || COMPILE_TEST
|
2009-12-16 08:46:17 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC subsystem of the
|
|
|
|
|
NUC910/NUC920 used in embedded systems.
|
2009-08-31 05:49:04 +08:00
|
|
|
|
2014-10-14 16:38:36 +08:00
|
|
|
config RTC_DRV_OPAL
|
|
|
|
|
tristate "IBM OPAL RTC driver"
|
|
|
|
|
depends on PPC_POWERNV
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the PowerNV platform RTC
|
|
|
|
|
driver based on OPAL interfaces.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-opal.
|
|
|
|
|
|
2015-08-19 17:53:22 +08:00
|
|
|
config RTC_DRV_ZYNQMP
|
|
|
|
|
tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC controller found on
|
|
|
|
|
Xilinx Zynq Ultrascale+ MPSoC.
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
comment "on-CPU RTC drivers"
|
|
|
|
|
|
2016-02-03 03:56:10 +08:00
|
|
|
config RTC_DRV_ASM9260
|
|
|
|
|
tristate "Alphascale asm9260 RTC"
|
2016-09-01 00:15:27 +08:00
|
|
|
depends on MACH_ASM9260 || COMPILE_TEST
|
2016-02-03 03:56:10 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC on the
|
|
|
|
|
Alphascale asm9260 SoC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-asm9260.
|
|
|
|
|
|
2009-11-05 22:51:34 +08:00
|
|
|
config RTC_DRV_DAVINCI
|
|
|
|
|
tristate "TI DaVinci RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
|
2009-11-05 22:51:34 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC on the
|
|
|
|
|
DaVinci platforms (DM365).
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-davinci.
|
|
|
|
|
|
2015-04-17 03:45:40 +08:00
|
|
|
config RTC_DRV_DIGICOLOR
|
|
|
|
|
tristate "Conexant Digicolor RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_DIGICOLOR || COMPILE_TEST
|
2015-04-17 03:45:40 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the RTC 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.
|
|
|
|
|
|
2012-05-30 06:07:37 +08:00
|
|
|
config RTC_DRV_IMXDI
|
|
|
|
|
tristate "Freescale IMX DryIce Real Time Clock"
|
2012-12-18 08:02:22 +08:00
|
|
|
depends on ARCH_MXC
|
2012-05-30 06:07:37 +08:00
|
|
|
help
|
|
|
|
|
Support for Freescale IMX DryIce RTC
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-imxdi".
|
|
|
|
|
|
2007-05-08 15:33:48 +08:00
|
|
|
config RTC_DRV_OMAP
|
2015-04-17 03:46:03 +08:00
|
|
|
tristate "TI OMAP Real Time Clock"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
|
2016-09-16 17:26:28 +08:00
|
|
|
depends on OF
|
|
|
|
|
depends on PINCTRL
|
|
|
|
|
select GENERIC_PINCONF
|
2007-05-08 15:33:48 +08:00
|
|
|
help
|
2012-12-18 08:02:17 +08:00
|
|
|
Say "yes" here to support the on chip real time clock
|
2015-04-17 03:46:03 +08:00
|
|
|
present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
|
2012-12-18 08:02:17 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, module
|
|
|
|
|
will be called rtc-omap.
|
2006-03-27 17:16:45 +08:00
|
|
|
|
2010-07-20 19:08:49 +08:00
|
|
|
config HAVE_S3C_RTC
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This will include RTC support for Samsung SoCs. If
|
|
|
|
|
you want to include RTC support for any machine, kindly
|
|
|
|
|
select this in the respective mach-XXXX/Kconfig file.
|
|
|
|
|
|
2006-07-01 19:36:26 +08:00
|
|
|
config RTC_DRV_S3C
|
|
|
|
|
tristate "Samsung S3C series SoC RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
|
2006-07-01 19:36:26 +08:00
|
|
|
help
|
|
|
|
|
RTC (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.
|
|
|
|
|
|
2006-03-27 17:16:45 +08:00
|
|
|
config RTC_DRV_EP93XX
|
|
|
|
|
tristate "Cirrus Logic EP93XX"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_EP93XX || COMPILE_TEST
|
2006-03-27 17:16:45 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
RTC 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.
|
|
|
|
|
|
2006-03-27 17:16:46 +08:00
|
|
|
config RTC_DRV_SA1100
|
2012-02-21 11:51:13 +08:00
|
|
|
tristate "SA11x0/PXA2xx/PXA910"
|
|
|
|
|
depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
|
2006-03-27 17:16:46 +08:00
|
|
|
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 M here: the
|
|
|
|
|
module will be called rtc-sa1100.
|
2006-03-27 17:16:45 +08:00
|
|
|
|
2006-09-27 16:13:19 +08:00
|
|
|
config RTC_DRV_SH
|
|
|
|
|
tristate "SuperH On-Chip RTC"
|
2017-03-30 01:30:29 +08:00
|
|
|
depends on SUPERH || ARCH_RENESAS
|
2006-09-27 16:13:19 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to enable support for the on-chip RTC found in
|
2017-03-30 01:30:29 +08:00
|
|
|
most SuperH processors. This RTC is also found in RZ/A SoCs.
|
2006-09-27 16:13:19 +08:00
|
|
|
|
2015-05-10 03:21:54 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
2006-09-27 16:13:19 +08:00
|
|
|
module will be called rtc-sh.
|
|
|
|
|
|
2006-04-11 13:54:47 +08:00
|
|
|
config RTC_DRV_VR41XX
|
2006-04-11 13:54:48 +08:00
|
|
|
tristate "NEC VR41XX"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on CPU_VR41XX || COMPILE_TEST
|
2006-04-11 13:54:48 +08:00
|
|
|
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 M here: the
|
|
|
|
|
module will be called rtc-vr41xx.
|
2006-04-11 13:54:47 +08:00
|
|
|
|
2008-04-20 19:08:36 +08:00
|
|
|
config RTC_DRV_PL030
|
|
|
|
|
tristate "ARM AMBA PL030 RTC"
|
|
|
|
|
depends on ARM_AMBA
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get access to ARM AMBA
|
|
|
|
|
PrimeCell PL030 RTC found on certain ARM SOCs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called rtc-pl030.
|
|
|
|
|
|
2006-06-25 20:47:38 +08:00
|
|
|
config RTC_DRV_PL031
|
|
|
|
|
tristate "ARM AMBA PL031 RTC"
|
2007-07-31 15:39:46 +08:00
|
|
|
depends on ARM_AMBA
|
2006-06-25 20:47:38 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get access to ARM AMBA
|
2007-05-08 15:33:48 +08:00
|
|
|
PrimeCell PL031 RTC found on certain ARM SOCs.
|
2006-06-25 20:47:38 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called rtc-pl031.
|
|
|
|
|
|
2007-07-17 19:05:00 +08:00
|
|
|
config RTC_DRV_AT32AP700X
|
|
|
|
|
tristate "AT32AP700X series RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on PLATFORM_AT32AP || COMPILE_TEST
|
2007-07-17 19:05:00 +08:00
|
|
|
help
|
|
|
|
|
Driver for the internal RTC (Realtime Clock) on Atmel AVR32
|
|
|
|
|
AT32AP700x family processors.
|
|
|
|
|
|
2006-12-10 18:19:03 +08:00
|
|
|
config RTC_DRV_AT91RM9200
|
2010-10-23 01:12:52 +08:00
|
|
|
tristate "AT91RM9200 or some AT91SAM9 RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_AT91 || COMPILE_TEST
|
2008-02-06 17:38:59 +08:00
|
|
|
help
|
|
|
|
|
Driver for the internal RTC (Realtime Clock) module found on
|
2010-10-23 01:12:52 +08:00
|
|
|
Atmel AT91RM9200's and some AT91SAM9 chips. On AT91SAM9 chips
|
2008-02-06 17:38:59 +08:00
|
|
|
this is powered by the backup power supply.
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_AT91SAM9
|
2014-09-23 19:16:05 +08:00
|
|
|
tristate "AT91SAM9 RTT as RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_AT91 || COMPILE_TEST
|
2014-09-23 19:14:44 +08:00
|
|
|
select MFD_SYSCON
|
2008-02-06 17:38:59 +08:00
|
|
|
help
|
2014-09-23 19:16:05 +08:00
|
|
|
Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
|
|
|
|
|
can be used as an RTC 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 RTC block, on those ones you'd
|
|
|
|
|
probably want to use the real RTC block instead of the "RTT as an
|
|
|
|
|
RTC" driver.
|
2008-02-06 17:38:59 +08:00
|
|
|
|
2009-01-07 06:42:18 +08:00
|
|
|
config RTC_DRV_AU1XXX
|
|
|
|
|
tristate "Au1xxx Counter0 RTC support"
|
2010-07-16 03:45:04 +08:00
|
|
|
depends on MIPS_ALCHEMY
|
2009-01-07 06:42:18 +08:00
|
|
|
help
|
|
|
|
|
This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
|
|
|
|
|
counter) to be used as a RTC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-au1xxx.
|
|
|
|
|
|
2007-05-07 05:50:32 +08:00
|
|
|
config RTC_DRV_BFIN
|
|
|
|
|
tristate "Blackfin On-Chip RTC"
|
2008-08-21 05:09:02 +08:00
|
|
|
depends on BLACKFIN && !BF561
|
2007-05-07 05:50:32 +08:00
|
|
|
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.
|
|
|
|
|
|
2007-05-08 15:26:37 +08:00
|
|
|
config RTC_DRV_RS5C313
|
|
|
|
|
tristate "Ricoh RS5C313"
|
2007-07-31 15:39:46 +08:00
|
|
|
depends on SH_LANDISK
|
2007-05-08 15:26:37 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Ricoh RS5C313 RTC chips.
|
|
|
|
|
|
2009-02-19 23:46:49 +08:00
|
|
|
config RTC_DRV_GENERIC
|
|
|
|
|
tristate "Generic RTC support"
|
|
|
|
|
# Please consider writing a new RTC driver instead of using the generic
|
|
|
|
|
# RTC abstraction
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on PARISC || M68K || PPC || SUPERH32 || COMPILE_TEST
|
2008-09-10 22:24:07 +08:00
|
|
|
help
|
2009-02-19 23:46:49 +08:00
|
|
|
Say Y or M here to enable RTC support on systems using the generic
|
|
|
|
|
RTC abstraction. If you do not know what you are doing, you should
|
2008-09-10 22:24:07 +08:00
|
|
|
just say Y.
|
|
|
|
|
|
2009-01-07 06:42:14 +08:00
|
|
|
config RTC_DRV_PXA
|
2016-03-10 12:46:18 +08:00
|
|
|
tristate "PXA27x/PXA3xx"
|
|
|
|
|
depends on ARCH_PXA
|
|
|
|
|
select RTC_DRV_SA1100
|
|
|
|
|
help
|
2015-05-13 22:20:04 +08:00
|
|
|
If you say Y here you will get access to the real time clock
|
|
|
|
|
built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
|
|
|
|
|
consisting of an SA1100 compatible RTC and the extended PXA RTC.
|
2009-01-07 06:42:14 +08:00
|
|
|
|
2015-05-10 03:21:54 +08:00
|
|
|
This RTC driver uses PXA RTC registers available since pxa27x
|
|
|
|
|
series (RDxR, RYxR) instead of legacy RCNR, RTAR.
|
2009-01-07 06:42:14 +08:00
|
|
|
|
2011-05-27 07:25:03 +08:00
|
|
|
config RTC_DRV_VT8500
|
|
|
|
|
tristate "VIA/WonderMedia 85xx SoC RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_VT8500 || COMPILE_TEST
|
2011-05-27 07:25:03 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get access to the real time clock
|
|
|
|
|
built into your VIA VT8500 SoC or its relatives.
|
|
|
|
|
|
2009-01-07 06:42:14 +08:00
|
|
|
|
2008-08-29 16:32:43 +08:00
|
|
|
config RTC_DRV_SUN4V
|
|
|
|
|
bool "SUN4V Hypervisor RTC"
|
|
|
|
|
depends on SPARC64
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the Hypervisor
|
|
|
|
|
based RTC on SUN4V systems.
|
|
|
|
|
|
2014-08-26 11:54:55 +08:00
|
|
|
config RTC_DRV_SUN6I
|
2017-01-23 18:41:46 +08:00
|
|
|
bool "Allwinner A31 RTC"
|
2017-02-01 19:54:13 +08:00
|
|
|
default MACH_SUN6I || MACH_SUN8I
|
|
|
|
|
depends on COMMON_CLK
|
|
|
|
|
depends on ARCH_SUNXI || COMPILE_TEST
|
2014-08-26 11:54:55 +08:00
|
|
|
help
|
2016-02-02 01:39:22 +08:00
|
|
|
If you say Y here you will get support for the RTC found in
|
|
|
|
|
some Allwinner SoCs like the A31 or the A64.
|
2014-08-26 11:54:55 +08:00
|
|
|
|
2013-11-17 01:33:54 +08:00
|
|
|
config RTC_DRV_SUNXI
|
|
|
|
|
tristate "Allwinner sun4i/sun7i RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
|
2013-11-17 01:33:54 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the RTC found on
|
|
|
|
|
Allwinner A10/A20.
|
|
|
|
|
|
2008-08-29 14:02:36 +08:00
|
|
|
config RTC_DRV_STARFIRE
|
|
|
|
|
bool "Starfire RTC"
|
|
|
|
|
depends on SPARC64
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the RTC found on
|
|
|
|
|
Starfire systems.
|
|
|
|
|
|
2009-01-07 06:42:22 +08:00
|
|
|
config RTC_DRV_TX4939
|
|
|
|
|
tristate "TX4939 SoC"
|
|
|
|
|
depends on SOC_TX4939
|
|
|
|
|
help
|
|
|
|
|
Driver for the internal RTC (Realtime Clock) module found on
|
|
|
|
|
Toshiba TX4939 SoC.
|
|
|
|
|
|
2009-01-07 06:42:24 +08:00
|
|
|
config RTC_DRV_MV
|
|
|
|
|
tristate "Marvell SoC RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
|
2009-01-07 06:42:24 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the in-chip RTC
|
|
|
|
|
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.
|
|
|
|
|
|
2015-02-14 06:41:11 +08:00
|
|
|
config RTC_DRV_ARMADA38X
|
|
|
|
|
tristate "Armada 38x Marvell SoC RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_MVEBU || COMPILE_TEST
|
2015-02-14 06:41:11 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the in-chip RTC
|
|
|
|
|
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.
|
|
|
|
|
|
2017-05-30 15:53:32 +08:00
|
|
|
config RTC_DRV_FTRTC010
|
|
|
|
|
tristate "Faraday Technology FTRTC010 RTC"
|
2015-05-20 23:49:31 +08:00
|
|
|
depends on HAS_IOMEM
|
2017-05-30 15:53:32 +08:00
|
|
|
default ARCH_GEMINI
|
2015-05-20 23:49:31 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the
|
2017-05-30 15:53:32 +08:00
|
|
|
Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
|
2015-05-20 23:49:31 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
2017-05-30 15:53:32 +08:00
|
|
|
will be called rtc-ftrtc010.
|
2015-05-20 23:49:31 +08:00
|
|
|
|
2009-02-24 21:04:20 +08:00
|
|
|
config RTC_DRV_PS3
|
|
|
|
|
tristate "PS3 RTC"
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the RTC on PS3.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ps3.
|
|
|
|
|
|
2009-09-23 07:46:24 +08:00
|
|
|
config RTC_DRV_COH901331
|
|
|
|
|
tristate "ST-Ericsson COH 901 331 RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_U300 || COMPILE_TEST
|
2009-09-23 07:46:24 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here you will get access to ST-Ericsson
|
|
|
|
|
COH 901 331 RTC 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".
|
|
|
|
|
|
|
|
|
|
|
2009-09-23 07:46:26 +08:00
|
|
|
config RTC_DRV_STMP
|
2011-05-25 18:56:50 +08:00
|
|
|
tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_MXS || COMPILE_TEST
|
2015-05-03 17:29:44 +08:00
|
|
|
select STMP_DEVICE
|
2009-09-23 07:46:26 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the onboard
|
2011-05-25 18:56:50 +08:00
|
|
|
STMP3xxx/i.MX23/i.MX28 RTC.
|
2009-09-23 07:46:26 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-stmp3xxx.
|
|
|
|
|
|
2009-09-23 07:46:27 +08:00
|
|
|
config RTC_DRV_PCAP
|
|
|
|
|
tristate "PCAP RTC"
|
|
|
|
|
depends on EZX_PCAP
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you will get support for the RTC found on
|
|
|
|
|
the PCAP2 ASIC used on some Motorola phones.
|
|
|
|
|
|
2010-10-28 18:30:53 +08:00
|
|
|
config RTC_DRV_MC13XXX
|
|
|
|
|
depends on MFD_MC13XXX
|
|
|
|
|
tristate "Freescale MC13xxx RTC"
|
2009-12-16 08:46:09 +08:00
|
|
|
help
|
2010-10-28 18:30:53 +08:00
|
|
|
This enables support for the RTCs found on Freescale's PMICs
|
|
|
|
|
MC13783 and MC13892.
|
2009-12-16 08:46:09 +08:00
|
|
|
|
2010-02-17 01:47:35 +08:00
|
|
|
config RTC_DRV_MPC5121
|
|
|
|
|
tristate "Freescale MPC5121 built-in RTC"
|
2011-07-26 08:13:30 +08:00
|
|
|
depends on PPC_MPC512x || PPC_MPC52xx
|
2010-02-17 01:47:35 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the
|
2011-07-26 08:13:30 +08:00
|
|
|
built-in RTC on MPC5121 or on MPC5200.
|
2010-02-17 01:47:35 +08:00
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-mpc5121.
|
|
|
|
|
|
2010-06-20 02:29:50 +08:00
|
|
|
config RTC_DRV_JZ4740
|
2017-01-25 07:44:16 +08:00
|
|
|
tristate "Ingenic JZ4740 SoC"
|
2016-11-01 04:39:45 +08:00
|
|
|
depends on MACH_INGENIC || COMPILE_TEST
|
2010-06-20 02:29:50 +08:00
|
|
|
help
|
2016-11-01 04:39:45 +08:00
|
|
|
If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
|
|
|
|
|
controllers.
|
2010-06-20 02:29:50 +08:00
|
|
|
|
2017-01-25 07:44:16 +08:00
|
|
|
This driver can also be buillt as a module. If so, the module
|
|
|
|
|
will be called rtc-jz4740.
|
|
|
|
|
|
2015-07-12 01:28:49 +08:00
|
|
|
config RTC_DRV_LPC24XX
|
|
|
|
|
tristate "NXP RTC for LPC178x/18xx/408x/43xx"
|
|
|
|
|
depends on ARCH_LPC18XX || COMPILE_TEST
|
|
|
|
|
depends on OF && HAS_IOMEM
|
|
|
|
|
help
|
|
|
|
|
This enables support for the NXP RTC 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
|
2016-11-09 05:51:45 +08:00
|
|
|
the hardware RTC. This driver can also be built as a module. If
|
2015-07-12 01:28:49 +08:00
|
|
|
so, the module will be called rtc-lpc24xx.
|
|
|
|
|
|
2010-10-28 06:33:01 +08:00
|
|
|
config RTC_DRV_LPC32XX
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_LPC32XX || COMPILE_TEST
|
2010-10-28 06:33:01 +08:00
|
|
|
tristate "NXP LPC32XX RTC"
|
|
|
|
|
help
|
|
|
|
|
This enables support for the NXP RTC in the LPC32XX
|
|
|
|
|
|
2016-11-09 05:51:45 +08:00
|
|
|
This driver can also be built as a module. If so, the module
|
2010-10-28 06:33:01 +08:00
|
|
|
will be called rtc-lpc32xx.
|
|
|
|
|
|
2011-07-26 08:13:33 +08:00
|
|
|
config RTC_DRV_PM8XXX
|
|
|
|
|
tristate "Qualcomm PMIC8XXX RTC"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
|
2011-07-26 08:13:33 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Qualcomm PMIC8XXX RTC.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called rtc-pm8xxx.
|
|
|
|
|
|
2011-03-23 07:34:55 +08:00
|
|
|
config RTC_DRV_TEGRA
|
|
|
|
|
tristate "NVIDIA Tegra Internal RTC driver"
|
2015-05-03 17:00:57 +08:00
|
|
|
depends on ARCH_TEGRA || COMPILE_TEST
|
2011-03-23 07:34:55 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
Tegra 200 series internal RTC module.
|
|
|
|
|
|
|
|
|
|
This drive can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-tegra.
|
|
|
|
|
|
2011-05-10 01:28:43 +08:00
|
|
|
config RTC_DRV_TILE
|
|
|
|
|
tristate "Tilera hypervisor RTC support"
|
|
|
|
|
depends on TILE
|
|
|
|
|
help
|
|
|
|
|
Enable support for the Linux driver side of the Tilera
|
|
|
|
|
hypervisor's real-time clock interface.
|
|
|
|
|
|
2011-05-26 16:43:27 +08:00
|
|
|
config RTC_DRV_PUV3
|
|
|
|
|
tristate "PKUnity v3 RTC support"
|
|
|
|
|
depends on ARCH_PUV3
|
|
|
|
|
help
|
|
|
|
|
This enables support for the RTC in the PKUnity-v3 SoCs.
|
|
|
|
|
|
|
|
|
|
This drive can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-puv3.
|
|
|
|
|
|
2012-03-24 06:02:32 +08:00
|
|
|
config RTC_DRV_LOONGSON1
|
|
|
|
|
tristate "loongson1 RTC support"
|
2015-04-21 10:00:35 +08:00
|
|
|
depends on MACH_LOONGSON32
|
2012-03-24 06:02:32 +08:00
|
|
|
help
|
|
|
|
|
This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
|
|
|
|
|
counter) to be used as a RTC.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-ls1x.
|
|
|
|
|
|
2012-05-30 06:07:37 +08:00
|
|
|
config RTC_DRV_MXC
|
2012-05-30 06:07:37 +08:00
|
|
|
tristate "Freescale MXC Real Time Clock"
|
|
|
|
|
depends on ARCH_MXC
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Freescale MXC
|
|
|
|
|
RTC module.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-mxc".
|
|
|
|
|
|
2012-10-05 08:13:49 +08:00
|
|
|
config RTC_DRV_SNVS
|
|
|
|
|
tristate "Freescale SNVS RTC support"
|
2015-07-13 15:58:51 +08:00
|
|
|
select REGMAP_MMIO
|
2012-10-05 08:13:49 +08:00
|
|
|
depends on HAS_IOMEM
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the Freescale SNVS
|
|
|
|
|
Low Power (LP) RTC module.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-snvs".
|
|
|
|
|
|
2013-07-04 06:08:04 +08:00
|
|
|
config RTC_DRV_SIRFSOC
|
|
|
|
|
tristate "SiRFSOC RTC"
|
|
|
|
|
depends on ARCH_SIRF
|
|
|
|
|
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.
|
|
|
|
|
|
2015-04-09 22:47:33 +08:00
|
|
|
config RTC_DRV_ST_LPC
|
|
|
|
|
tristate "STMicroelectronics LPC RTC"
|
|
|
|
|
depends on ARCH_STI
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include STMicroelectronics Low Power Controller
|
|
|
|
|
(LPC) based RTC support.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called rtc-st-lpc.
|
|
|
|
|
|
2013-09-12 05:24:17 +08:00
|
|
|
config RTC_DRV_MOXART
|
|
|
|
|
tristate "MOXA ART RTC"
|
2014-08-09 05:20:05 +08:00
|
|
|
depends on ARCH_MOXART || COMPILE_TEST
|
2013-09-12 05:24:17 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the MOXA ART
|
|
|
|
|
RTC module.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-moxart
|
|
|
|
|
|
2015-05-06 15:23:41 +08:00
|
|
|
config RTC_DRV_MT6397
|
|
|
|
|
tristate "Mediatek Real Time Clock driver"
|
2016-01-26 00:04:46 +08:00
|
|
|
depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
|
2015-05-06 15:23:41 +08:00
|
|
|
help
|
|
|
|
|
This selects the Mediatek(R) RTC driver. RTC is part of Mediatek
|
|
|
|
|
MT6397 PMIC. You should enable MT6397 PMIC MFD before select
|
|
|
|
|
Mediatek(R) RTC driver.
|
|
|
|
|
|
|
|
|
|
If you want to use Mediatek(R) RTC interface, select Y or M here.
|
|
|
|
|
|
2014-06-07 05:35:42 +08:00
|
|
|
config RTC_DRV_XGENE
|
|
|
|
|
tristate "APM X-Gene RTC"
|
2014-10-14 06:53:14 +08:00
|
|
|
depends on HAS_IOMEM
|
2015-05-06 15:24:42 +08:00
|
|
|
depends on ARCH_XGENE || COMPILE_TEST
|
2014-06-07 05:35:42 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the APM X-Gene SoC real time
|
|
|
|
|
clock.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-xgene".
|
|
|
|
|
|
2016-02-26 01:30:44 +08:00
|
|
|
config RTC_DRV_PIC32
|
|
|
|
|
tristate "Microchip PIC32 RTC"
|
|
|
|
|
depends on MACH_PIC32
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the PIC32 RTC module.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-pic32
|
|
|
|
|
|
2016-12-04 22:04:39 +08:00
|
|
|
config RTC_DRV_R7301
|
|
|
|
|
tristate "EPSON TOYOCOM RTC-7301SF/DG"
|
|
|
|
|
select REGMAP_MMIO
|
|
|
|
|
depends on OF && HAS_IOMEM
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the EPSON TOYOCOM
|
|
|
|
|
RTC-7301SF/DG chips.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called rtc-r7301.
|
|
|
|
|
|
2017-01-11 21:46:43 +08:00
|
|
|
config RTC_DRV_STM32
|
|
|
|
|
tristate "STM32 RTC"
|
|
|
|
|
select REGMAP_MMIO
|
|
|
|
|
depends on ARCH_STM32 || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the STM32 On-Chip
|
|
|
|
|
Real Time Clock.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module, if so, the module
|
|
|
|
|
will be called "rtc-stm32".
|
|
|
|
|
|
2017-03-02 08:27:09 +08:00
|
|
|
config RTC_DRV_CPCAP
|
|
|
|
|
depends on MFD_CPCAP
|
|
|
|
|
tristate "Motorola CPCAP RTC"
|
|
|
|
|
help
|
|
|
|
|
Say y here for CPCAP rtc found on some Motorola phones
|
|
|
|
|
and tablets such as Droid 4.
|
|
|
|
|
|
2012-12-15 20:45:00 +08:00
|
|
|
comment "HID Sensor RTC drivers"
|
|
|
|
|
|
|
|
|
|
config RTC_DRV_HID_SENSOR_TIME
|
|
|
|
|
tristate "HID Sensor Time"
|
|
|
|
|
depends on USB_HID
|
|
|
|
|
select IIO
|
|
|
|
|
select HID_SENSOR_HUB
|
|
|
|
|
select HID_SENSOR_IIO_COMMON
|
|
|
|
|
help
|
|
|
|
|
Say yes here to build support for the HID 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.
|
|
|
|
|
|
|
|
|
|
|
2007-07-31 15:39:46 +08:00
|
|
|
endif # RTC_CLASS
|
