1# SPDX-License-Identifier: GPL-2.0-only
   2#
   3# RTC class/drivers configuration
   4#
   5
   6config RTC_LIB
   7	bool
   8
   9config RTC_MC146818_LIB
  10	bool
  11	select RTC_LIB
  12
  13menuconfig RTC_CLASS
  14	bool "Real Time Clock"
  15	default n
  16	depends on !S390
  17	select RTC_LIB
  18	help
  19	  Generic RTC class support. If you say yes here, you will
  20	  be allowed to plug one or more RTCs to your system. You will
  21	  probably want to enable one or more of the interfaces below.
  22
  23if RTC_CLASS
  24
  25config RTC_HCTOSYS
  26	bool "Set system time from RTC on startup and resume"
  27	default y
  28	help
  29	  If you say yes here, the system time (wall clock) will be set using
  30	  the value read from a specified RTC device. This is useful to avoid
  31	  unnecessary fsck runs at boot time, and to network better.
  32
  33config RTC_HCTOSYS_DEVICE
  34	string "RTC used to set the system time"
  35	depends on RTC_HCTOSYS
  36	default "rtc0"
  37	help
  38	  The RTC device that will be used to (re)initialize the system
  39	  clock, usually rtc0. Initialization is done when the system
  40	  starts up, and when it resumes from a low power state. This
  41	  device should record time in UTC, since the kernel won't do
  42	  timezone correction.
  43
  44	  This clock should be battery-backed, so that it reads the correct
  45	  time when the system boots from a power-off state. Otherwise, your
  46	  system will need an external clock source (like an NTP server).
  47
  48	  If the clock you specify here is not battery backed, it may still
  49	  be useful to reinitialize system time when resuming from system
  50	  sleep states. Do not specify an RTC here unless it stays powered
  51	  during all this system's supported sleep states.
  52
  53config RTC_SYSTOHC
  54	bool "Set the RTC time based on NTP synchronization"
  55	default y
  56	help
  57	  If you say yes here, the system time (wall clock) will be stored
  58	  in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
  59	  minutes if userspace reports synchronized NTP status.
  60
  61config RTC_SYSTOHC_DEVICE
  62	string "RTC used to synchronize NTP adjustment"
  63	depends on RTC_SYSTOHC
  64	default RTC_HCTOSYS_DEVICE if RTC_HCTOSYS
  65	default "rtc0"
  66	help
  67	  The RTC device used for NTP synchronization. The main difference
  68	  between RTC_HCTOSYS_DEVICE and RTC_SYSTOHC_DEVICE is that this
  69	  one can sleep when setting time, because it runs in the workqueue
  70	  context.
  71
  72config RTC_DEBUG
  73	bool "RTC debug support"
  74	help
  75	  Say yes here to enable debugging support in the RTC framework
  76	  and individual RTC drivers.
  77
 
 
 
 
 
 
 
 
 
  78config RTC_NVMEM
  79	bool "RTC non volatile storage support"
  80	select NVMEM
  81	default RTC_CLASS
  82	help
  83	  Say yes here to add support for the non volatile (often battery
  84	  backed) storage present on RTCs.
  85
  86comment "RTC interfaces"
  87
  88config RTC_INTF_SYSFS
  89	bool "/sys/class/rtc/rtcN (sysfs)"
  90	depends on SYSFS
  91	default RTC_CLASS
  92	help
  93	  Say yes here if you want to use your RTCs using sysfs interfaces,
  94	  /sys/class/rtc/rtc0 through /sys/.../rtcN.
  95
  96	  If unsure, say Y.
  97
  98config RTC_INTF_PROC
  99	bool "/proc/driver/rtc (procfs for rtcN)"
 100	depends on PROC_FS
 101	default RTC_CLASS
 102	help
 103	  Say yes here if you want to use your system clock RTC through
 104	  the proc interface, /proc/driver/rtc.
 105	  Other RTCs will not be available through that API.
 106	  If there is no RTC for the system clock, then the first RTC(rtc0)
 107	  is used by default.
 108
 109	  If unsure, say Y.
 110
 111config RTC_INTF_DEV
 112	bool "/dev/rtcN (character devices)"
 113	default RTC_CLASS
 114	help
 115	  Say yes here if you want to use your RTCs using the /dev
 116	  interfaces, which "udev" sets up as /dev/rtc0 through
 117	  /dev/rtcN.
 118
 119	  You may want to set up a symbolic link so one of these
 120	  can be accessed as /dev/rtc, which is a name
 121	  expected by "hwclock" and some other programs. Recent
 122	  versions of "udev" are known to set up the symlink for you.
 123
 124	  If unsure, say Y.
 125
 126config RTC_INTF_DEV_UIE_EMUL
 127	bool "RTC UIE emulation on dev interface"
 128	depends on RTC_INTF_DEV
 129	help
 130	  Provides an emulation for RTC_UIE if the underlying rtc chip
 131	  driver does not expose RTC_UIE ioctls. Those requests generate
 132	  once-per-second update interrupts, used for synchronization.
 133
 134	  The emulation code will read the time from the hardware
 135	  clock several times per second, please enable this option
 136	  only if you know that you really need it.
 137
 138config RTC_DRV_TEST
 139	tristate "Test driver/device"
 140	help
 141	  If you say yes here you get support for the
 142	  RTC test driver. It's a software RTC which can be
 143	  used to test the RTC subsystem APIs. It gets
 144	  the time from the system clock.
 145	  You want this driver only if you are doing development
 146	  on the RTC subsystem. Please read the source code
 147	  for further details.
 148
 149	  This driver can also be built as a module. If so, the module
 150	  will be called rtc-test.
 151
 152comment "I2C RTC drivers"
 153
 154if I2C
 155
 156config RTC_DRV_88PM860X
 157	tristate "Marvell 88PM860x"
 158	depends on MFD_88PM860X
 159	help
 160	  If you say yes here you get support for RTC function in Marvell
 161	  88PM860x chips.
 162
 163	  This driver can also be built as a module. If so, the module
 164	  will be called rtc-88pm860x.
 165
 166config RTC_DRV_88PM80X
 167	tristate "Marvell 88PM80x"
 168	depends on MFD_88PM800
 169	help
 170	  If you say yes here you get support for RTC function in Marvell
 171	  88PM80x chips.
 172
 173	  This driver can also be built as a module. If so, the module
 174	  will be called rtc-88pm80x.
 175
 176config RTC_DRV_ABB5ZES3
 177	select REGMAP_I2C
 178	tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
 179	help
 180	  If you say yes here you get support for the Abracon
 181	  AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
 182
 183	  This driver can also be built as a module. If so, the module
 184	  will be called rtc-ab-b5ze-s3.
 185
 186config RTC_DRV_ABEOZ9
 187	select REGMAP_I2C
 188	tristate "Abracon AB-RTCMC-32.768kHz-EOZ9"
 189	help
 190	  If you say yes here you get support for the Abracon
 191	  AB-RTCMC-32.768kHz-EOA9 I2C RTC chip.
 192
 193	  This driver can also be built as a module. If so, the module
 194	  will be called rtc-ab-e0z9.
 195
 196config RTC_DRV_ABX80X
 197	tristate "Abracon ABx80x"
 198	select WATCHDOG_CORE if WATCHDOG
 199	help
 200	  If you say yes here you get support for Abracon AB080X and AB180X
 201	  families of ultra-low-power  battery- and capacitor-backed real-time
 202	  clock chips.
 203
 204	  This driver can also be built as a module. If so, the module
 205	  will be called rtc-abx80x.
 206
 207config RTC_DRV_AC100
 208	tristate "X-Powers AC100"
 209	depends on MFD_AC100
 210	help
 211	  If you say yes here you get support for the real-time clock found
 212	  in X-Powers AC100 family peripheral ICs.
 213
 214	  This driver can also be built as a module. If so, the module
 215	  will be called rtc-ac100.
 216
 217config RTC_DRV_BRCMSTB
 218	tristate "Broadcom STB wake-timer"
 219	depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
 220	default ARCH_BRCMSTB || BMIPS_GENERIC
 221	help
 222	  If you say yes here you get support for the wake-timer found on
 223	  Broadcom STB SoCs (BCM7xxx).
 224
 225	  This driver can also be built as a module. If so, the module will
 226	  be called rtc-brcmstb-waketimer.
 227
 228config RTC_DRV_AS3722
 229	tristate "ams AS3722 RTC driver"
 230	depends on MFD_AS3722
 231	help
 232	  If you say yes here you get support for the RTC of ams AS3722 PMIC
 233	  chips.
 234
 235	  This driver can also be built as a module. If so, the module
 236	  will be called rtc-as3722.
 237
 238config RTC_DRV_DS1307
 239	tristate "Dallas/Maxim DS1307/37/38/39/40/41, ST M41T00, EPSON RX-8025, ISL12057"
 240	select REGMAP_I2C
 241	select WATCHDOG_CORE if WATCHDOG
 242	help
 243	  If you say yes here you get support for various compatible RTC
 244	  chips (often with battery backup) connected with I2C. This driver
 245	  should handle DS1307, DS1337, DS1338, DS1339, DS1340, DS1341,
 246	  ST M41T00, EPSON RX-8025, Intersil ISL12057 and probably other chips.
 247	  In some cases the RTC must already have been initialized (by
 248	  manufacturing or a bootloader).
 249
 250	  The first seven registers on these chips hold an RTC, and other
 251	  registers may add features such as NVRAM, a trickle charger for
 252	  the RTC/NVRAM backup power, and alarms. NVRAM is visible in
 253	  sysfs, but other chip features may not be available.
 254
 255	  This driver can also be built as a module. If so, the module
 256	  will be called rtc-ds1307.
 257
 258config RTC_DRV_DS1307_CENTURY
 259	bool "Century bit support for rtc-ds1307"
 260	depends on RTC_DRV_DS1307
 261	default n
 262	help
 263	  The DS1307 driver suffered from a bug where it was enabling the
 264	  century bit inconditionnally but never used it when reading the time.
 265	  It made the driver unable to support dates beyond 2099.
 266	  Setting this option will add proper support for the century bit but if
 267	  the time was previously set using a kernel predating this option,
 268	  reading the date will return a date in the next century.
 269	  To solve that, you could boot a kernel without this option set, set
 270	  the RTC date and then boot a kernel with this option set.
 271
 272config RTC_DRV_DS1374
 273	tristate "Dallas/Maxim DS1374"
 274	help
 275	  If you say yes here you get support for Dallas Semiconductor
 276	  DS1374 real-time clock chips. If an interrupt is associated
 277	  with the device, the alarm functionality is supported.
 278
 279	  This driver can also be built as a module. If so, the module
 280	  will be called rtc-ds1374.
 281
 282config RTC_DRV_DS1374_WDT
 283	bool "Dallas/Maxim DS1374 watchdog timer"
 284	depends on RTC_DRV_DS1374 && WATCHDOG
 285	select WATCHDOG_CORE
 286	help
 287	  If you say Y here you will get support for the
 288	  watchdog timer in the Dallas Semiconductor DS1374
 289	  real-time clock chips.
 290
 291config RTC_DRV_DS1672
 292	tristate "Dallas/Maxim DS1672"
 293	help
 294	  If you say yes here you get support for the
 295	  Dallas/Maxim DS1672 timekeeping chip.
 296
 297	  This driver can also be built as a module. If so, the module
 298	  will be called rtc-ds1672.
 299
 300config RTC_DRV_HYM8563
 301	tristate "Haoyu Microelectronics HYM8563"
 302	depends on OF
 303	help
 304	  Say Y to enable support for the HYM8563 I2C RTC chip. Apart
 305	  from the usual rtc functions it provides a clock output of
 306	  up to 32kHz.
 307
 308	  This driver can also be built as a module. If so, the module
 309	  will be called rtc-hym8563.
 310
 311config RTC_DRV_LP8788
 312	tristate "TI LP8788 RTC driver"
 313	depends on MFD_LP8788
 314	help
 315	  Say Y to enable support for the LP8788 RTC/ALARM driver.
 316
 317config RTC_DRV_MAX6900
 318	tristate "Maxim MAX6900"
 319	help
 320	  If you say yes here you will get support for the
 321	  Maxim MAX6900 I2C RTC chip.
 322
 323	  This driver can also be built as a module. If so, the module
 324	  will be called rtc-max6900.
 325
 326config RTC_DRV_MAX8907
 327	tristate "Maxim MAX8907"
 328	depends on MFD_MAX8907 || COMPILE_TEST
 329	select REGMAP_IRQ
 330	help
 331	  If you say yes here you will get support for the
 332	  RTC of Maxim MAX8907 PMIC.
 333
 334	  This driver can also be built as a module. If so, the module
 335	  will be called rtc-max8907.
 336
 337config RTC_DRV_MAX8925
 338	tristate "Maxim MAX8925"
 339	depends on MFD_MAX8925
 340	help
 341	  If you say yes here you will get support for the
 342	  RTC of Maxim MAX8925 PMIC.
 343
 344	  This driver can also be built as a module. If so, the module
 345	  will be called rtc-max8925.
 346
 347config RTC_DRV_MAX8998
 348	tristate "Maxim MAX8998"
 349	depends on MFD_MAX8998
 350	help
 351	  If you say yes here you will get support for the
 352	  RTC of Maxim MAX8998 PMIC.
 353
 354	  This driver can also be built as a module. If so, the module
 355	  will be called rtc-max8998.
 356
 357config RTC_DRV_MAX8997
 358	tristate "Maxim MAX8997"
 359	depends on MFD_MAX8997
 360	help
 361	  If you say yes here you will get support for the
 362	  RTC of Maxim MAX8997 PMIC.
 363
 364	  This driver can also be built as a module. If so, the module
 365	  will be called rtc-max8997.
 366
 367config RTC_DRV_MAX77686
 368	tristate "Maxim MAX77686"
 369	depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
 370	help
 371	  If you say yes here you will get support for the
 372	  RTC of Maxim MAX77686/MAX77620/MAX77802 PMIC.
 373
 374	  This driver can also be built as a module. If so, the module
 375	  will be called rtc-max77686.
 376
 
 
 
 
 
 
 
 
 
 
 377config RTC_DRV_RK808
 378	tristate "Rockchip RK805/RK808/RK809/RK817/RK818 RTC"
 379	depends on MFD_RK808
 380	help
 381	  If you say yes here you will get support for the
 382	  RTC of RK805, RK809 and RK817, RK808 and RK818 PMIC.
 383
 384	  This driver can also be built as a module. If so, the module
 385	  will be called rk808-rtc.
 386
 387config RTC_DRV_RS5C372
 388	tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
 389	help
 390	  If you say yes here you get support for the
 391	  Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
 392
 393	  This driver can also be built as a module. If so, the module
 394	  will be called rtc-rs5c372.
 395
 396config RTC_DRV_ISL1208
 397	tristate "Intersil ISL1208"
 398	help
 399	  If you say yes here you get support for the
 400	  Intersil ISL1208 RTC chip.
 401
 402	  This driver can also be built as a module. If so, the module
 403	  will be called rtc-isl1208.
 404
 405config RTC_DRV_ISL12022
 406	tristate "Intersil ISL12022"
 
 407	help
 408	  If you say yes here you get support for the
 409	  Intersil ISL12022 RTC chip.
 410
 411	  This driver can also be built as a module. If so, the module
 412	  will be called rtc-isl12022.
 413
 414config RTC_DRV_ISL12026
 415	tristate "Intersil ISL12026"
 416	depends on OF || COMPILE_TEST
 417	help
 418	  If you say yes here you get support for the
 419	  Intersil ISL12026 RTC chip.
 420
 421	  This driver can also be built as a module. If so, the module
 422	  will be called rtc-isl12026.
 423
 424config RTC_DRV_X1205
 425	tristate "Xicor/Intersil X1205"
 426	help
 427	  If you say yes here you get support for the
 428	  Xicor/Intersil X1205 RTC chip.
 429
 430	  This driver can also be built as a module. If so, the module
 431	  will be called rtc-x1205.
 432
 433config RTC_DRV_PCF8523
 434	tristate "NXP PCF8523"
 
 435	help
 436	  If you say yes here you get support for the NXP PCF8523 RTC
 437	  chips.
 438
 439	  This driver can also be built as a module. If so, the module
 440	  will be called rtc-pcf8523.
 441
 442config RTC_DRV_PCF85063
 443	tristate "NXP PCF85063"
 444	select REGMAP_I2C
 445	help
 446	  If you say yes here you get support for the PCF85063 RTC chip
 447
 448	  This driver can also be built as a module. If so, the module
 449	  will be called rtc-pcf85063.
 450
 451config RTC_DRV_PCF85363
 452	tristate "NXP PCF85363"
 453	select REGMAP_I2C
 454	help
 455	  If you say yes here you get support for the PCF85363 RTC chip.
 456
 457	  This driver can also be built as a module. If so, the module
 458	  will be called rtc-pcf85363.
 459
 460	  The nvmem interface will be named pcf85363-#, where # is the
 461	  zero-based instance number.
 462
 463config RTC_DRV_PCF8563
 464	tristate "Philips PCF8563/Epson RTC8564"
 465	help
 466	  If you say yes here you get support for the
 467	  Philips PCF8563 RTC chip. The Epson RTC8564
 468	  should work as well.
 469
 470	  This driver can also be built as a module. If so, the module
 471	  will be called rtc-pcf8563.
 472
 473config RTC_DRV_PCF8583
 474	tristate "Philips PCF8583"
 475	help
 476	  If you say yes here you get support for the Philips PCF8583
 477	  RTC chip found on Acorn RiscPCs. This driver supports the
 478	  platform specific method of retrieving the current year from
 479	  the RTC's SRAM. It will work on other platforms with the same
 480	  chip, but the year will probably have to be tweaked.
 481
 482	  This driver can also be built as a module. If so, the module
 483	  will be called rtc-pcf8583.
 484
 485config RTC_DRV_M41T80
 486	tristate "ST M41T62/65/M41T80/81/82/83/84/85/87 and compatible"
 487	help
 488	  If you say Y here you will get support for the ST M41T60
 489	  and M41T80 RTC chips series. Currently, the following chips are
 490	  supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
 491	  M41ST85, M41ST87, and MicroCrystal RV4162.
 492
 493	  This driver can also be built as a module. If so, the module
 494	  will be called rtc-m41t80.
 495
 496config RTC_DRV_M41T80_WDT
 497	bool "ST M41T65/M41T80 series RTC watchdog timer"
 498	depends on RTC_DRV_M41T80
 499	help
 500	  If you say Y here you will get support for the
 501	  watchdog timer in the ST M41T60 and M41T80 RTC chips series.
 502
 503config RTC_DRV_BD70528
 504	tristate "ROHM BD71815 and BD71828 PMIC RTC"
 505	depends on MFD_ROHM_BD71828
 506	help
 507	  If you say Y here you will get support for the RTC
 508	  block on ROHM BD71815 and BD71828 Power Management IC.
 509
 510	  This driver can also be built as a module. If so, the module
 511	  will be called rtc-bd70528.
 512
 513config RTC_DRV_BQ32K
 514	tristate "TI BQ32000"
 515	help
 516	  If you say Y here you will get support for the TI
 517	  BQ32000 I2C RTC chip.
 518
 519	  This driver can also be built as a module. If so, the module
 520	  will be called rtc-bq32k.
 521
 522config RTC_DRV_DM355EVM
 523	tristate "TI DaVinci DM355 EVM RTC"
 524	depends on MFD_DM355EVM_MSP
 525	help
 526	  Supports the RTC firmware in the MSP430 on the DM355 EVM.
 527
 528config RTC_DRV_TWL92330
 529	bool "TI TWL92330/Menelaus"
 530	depends on MENELAUS
 531	help
 532	  If you say yes here you get support for the RTC on the
 533	  TWL92330 "Menelaus" power management chip, used with OMAP2
 534	  platforms. The support is integrated with the rest of
 535	  the Menelaus driver; it's not separate module.
 536
 537config RTC_DRV_TWL4030
 538	tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
 539	depends on TWL4030_CORE
 540	depends on OF
 541	help
 542	  If you say yes here you get support for the RTC on the
 543	  TWL4030/TWL5030/TWL6030 family chips, used mostly with OMAP3 platforms.
 544
 545	  This driver can also be built as a module. If so, the module
 546	  will be called rtc-twl.
 547
 548config RTC_DRV_PALMAS
 549	tristate "TI Palmas RTC driver"
 550	depends on MFD_PALMAS
 551	help
 552	  If you say yes here you get support for the RTC of TI PALMA series PMIC
 553	  chips.
 554
 555	  This driver can also be built as a module. If so, the module
 556	  will be called rtc-palma.
 557
 558config RTC_DRV_TPS6586X
 559	tristate "TI TPS6586X RTC driver"
 560	depends on MFD_TPS6586X
 561	help
 562	  TI Power Management IC TPS6586X supports RTC functionality
 563	  along with alarm. This driver supports the RTC driver for
 564	  the TPS6586X RTC module.
 565
 566config RTC_DRV_TPS65910
 567	tristate "TI TPS65910 RTC driver"
 568	depends on MFD_TPS65910
 569	help
 570	  If you say yes here you get support for the RTC on the
 571	  TPS65910 chips.
 572
 573	  This driver can also be built as a module. If so, the module
 574	  will be called rtc-tps65910.
 575
 576config RTC_DRV_TPS80031
 577	tristate "TI TPS80031/TPS80032 RTC driver"
 578	depends on MFD_TPS80031
 579	help
 580	  TI Power Management IC TPS80031 supports RTC functionality
 581	  along with alarm. This driver supports the RTC driver for
 582	  the TPS80031 RTC module.
 583
 584config RTC_DRV_RC5T583
 585	tristate "RICOH 5T583 RTC driver"
 586	depends on MFD_RC5T583
 587	help
 588	  If you say yes here you get support for the RTC on the
 589	  RICOH 5T583 chips.
 590
 591	  This driver can also be built as a module. If so, the module
 592	  will be called rtc-rc5t583.
 593
 594config RTC_DRV_RC5T619
 595	tristate "RICOH RC5T619 RTC driver"
 596	depends on MFD_RN5T618
 597	help
 598	  If you say yes here you get support for the RTC on the
 599	  RICOH RC5T619 chips.
 600
 601	  This driver can also be built as a module. If so, the module
 602	  will be called rtc-rc5t619.
 603
 604config RTC_DRV_S35390A
 605	tristate "Seiko Instruments S-35390A"
 606	select BITREVERSE
 607	help
 608	  If you say yes here you will get support for the Seiko
 609	  Instruments S-35390A.
 610
 611	  This driver can also be built as a module. If so the module
 612	  will be called rtc-s35390a.
 613
 614config RTC_DRV_FM3130
 615	tristate "Ramtron FM3130"
 616	help
 617	  If you say Y here you will get support for the
 618	  Ramtron FM3130 RTC chips.
 619	  Ramtron FM3130 is a chip with two separate devices inside,
 620	  RTC clock and FRAM. This driver provides only RTC functionality.
 621
 622	  This driver can also be built as a module. If so the module
 623	  will be called rtc-fm3130.
 624
 625config RTC_DRV_RX8010
 626	tristate "Epson RX8010SJ"
 627	select REGMAP_I2C
 628	help
 629	  If you say yes here you get support for the Epson RX8010SJ RTC
 630	  chip.
 631
 632	  This driver can also be built as a module. If so, the module
 633	  will be called rtc-rx8010.
 634
 635config RTC_DRV_RX8581
 636	tristate "Epson RX-8571/RX-8581"
 637	select REGMAP_I2C
 638	help
 639	  If you say yes here you will get support for the Epson RX-8571/
 640	  RX-8581.
 641
 642	  This driver can also be built as a module. If so the module
 643	  will be called rtc-rx8581.
 644
 645config RTC_DRV_RX8025
 646	tristate "Epson RX-8025SA/NB"
 647	help
 648	  If you say yes here you get support for the Epson
 649	  RX-8025SA/NB RTC chips.
 650
 651	  This driver can also be built as a module. If so, the module
 652	  will be called rtc-rx8025.
 653
 654config RTC_DRV_EM3027
 655	tristate "EM Microelectronic EM3027"
 656	help
 657	  If you say yes here you get support for the EM
 658	  Microelectronic EM3027 RTC chips.
 659
 660	  This driver can also be built as a module. If so, the module
 661	  will be called rtc-em3027.
 662
 663config RTC_DRV_RV3028
 664	tristate "Micro Crystal RV3028"
 665	select REGMAP_I2C
 666	help
 667	  If you say yes here you get support for the Micro Crystal
 668	  RV3028.
 669
 670	  This driver can also be built as a module. If so, the module
 671	  will be called rtc-rv3028.
 672
 673config RTC_DRV_RV3032
 674	tristate "Micro Crystal RV3032"
 675	select REGMAP_I2C
 676	help
 677	  If you say yes here you get support for the Micro Crystal
 678	  RV3032.
 679
 680	  This driver can also be built as a module. If so, the module
 681	  will be called rtc-rv3032.
 682
 683config RTC_DRV_RV8803
 684	tristate "Micro Crystal RV8803, Epson RX8900"
 685	help
 686	  If you say yes here you get support for the Micro Crystal RV8803 and
 687	  Epson RX8900 RTC chips.
 688
 689	  This driver can also be built as a module. If so, the module
 690	  will be called rtc-rv8803.
 691
 692config RTC_DRV_S5M
 693	tristate "Samsung S2M/S5M series"
 694	depends on MFD_SEC_CORE || COMPILE_TEST
 695	select REGMAP_IRQ
 696	select REGMAP_I2C
 697	help
 698	  If you say yes here you will get support for the
 699	  RTC of Samsung S2MPS14 and S5M PMIC series.
 700
 701	  This driver can also be built as a module. If so, the module
 702	  will be called rtc-s5m.
 703
 704config RTC_DRV_SD3078
 705	tristate "ZXW Shenzhen whwave SD3078"
 706	select REGMAP_I2C
 707	help
 708	  If you say yes here you get support for the ZXW Shenzhen whwave
 709	  SD3078 RTC chips.
 710
 711	  This driver can also be built as a module. If so, the module
 712	  will be called rtc-sd3078
 713
 714endif # I2C
 715
 716comment "SPI RTC drivers"
 717
 718if SPI_MASTER
 719
 720config RTC_DRV_M41T93
 721	tristate "ST M41T93"
 722	help
 723	  If you say yes here you will get support for the
 724	  ST M41T93 SPI RTC chip.
 725
 726	  This driver can also be built as a module. If so, the module
 727	  will be called rtc-m41t93.
 728
 729config RTC_DRV_M41T94
 730	tristate "ST M41T94"
 731	help
 732	  If you say yes here you will get support for the
 733	  ST M41T94 SPI RTC chip.
 734
 735	  This driver can also be built as a module. If so, the module
 736	  will be called rtc-m41t94.
 737
 738config RTC_DRV_DS1302
 739	tristate "Dallas/Maxim DS1302"
 740	depends on SPI
 741	help
 742	  If you say yes here you get support for the Dallas DS1302 RTC chips.
 743
 744	  This driver can also be built as a module. If so, the module
 745	  will be called rtc-ds1302.
 746
 747config RTC_DRV_DS1305
 748	tristate "Dallas/Maxim DS1305/DS1306"
 749	help
 750	  Select this driver to get support for the Dallas/Maxim DS1305
 751	  and DS1306 real time clock chips. These support a trickle
 752	  charger, alarms, and NVRAM in addition to the clock.
 753
 754	  This driver can also be built as a module. If so, the module
 755	  will be called rtc-ds1305.
 756
 757config RTC_DRV_DS1343
 758	select REGMAP_SPI
 759	tristate "Dallas/Maxim DS1343/DS1344"
 760	help
 761	  If you say yes here you get support for the
 762	  Dallas/Maxim DS1343 and DS1344 real time clock chips.
 763	  Support for trickle charger, alarm is provided.
 764
 765	  This driver can also be built as a module. If so, the module
 766	  will be called rtc-ds1343.
 767
 768config RTC_DRV_DS1347
 769	select REGMAP_SPI
 770	tristate "Dallas/Maxim DS1347"
 771	help
 772	  If you say yes here you get support for the
 773	  Dallas/Maxim DS1347 chips.
 774
 775	  This driver only supports the RTC feature, and not other chip
 776	  features such as alarms.
 777
 778	  This driver can also be built as a module. If so, the module
 779	  will be called rtc-ds1347.
 780
 781config RTC_DRV_DS1390
 782	tristate "Dallas/Maxim DS1390/93/94"
 783	help
 784	  If you say yes here you get support for the
 785	  Dallas/Maxim DS1390/93/94 chips.
 786
 787	  This driver supports the RTC feature and trickle charging but not
 788	  other chip features such as alarms.
 789
 790	  This driver can also be built as a module. If so, the module
 791	  will be called rtc-ds1390.
 792
 793config RTC_DRV_MAX6916
 794	tristate "Maxim MAX6916"
 795	help
 796	  If you say yes here you will get support for the
 797	  Maxim MAX6916 SPI RTC chip.
 798
 799	  This driver only supports the RTC feature, and not other chip
 800	  features such as alarms.
 801
 802	  This driver can also be built as a module. If so, the module
 803	  will be called rtc-max6916.
 804
 805config RTC_DRV_R9701
 806	tristate "Epson RTC-9701JE"
 807	help
 808	  If you say yes here you will get support for the
 809	  Epson RTC-9701JE SPI RTC chip.
 810
 811	  This driver can also be built as a module. If so, the module
 812	  will be called rtc-r9701.
 813
 814config RTC_DRV_RX4581
 815	tristate "Epson RX-4581"
 816	help
 817	  If you say yes here you will get support for the Epson RX-4581.
 818
 819	  This driver can also be built as a module. If so the module
 820	  will be called rtc-rx4581.
 821
 822config RTC_DRV_RS5C348
 823	tristate "Ricoh RS5C348A/B"
 824	help
 825	  If you say yes here you get support for the
 826	  Ricoh RS5C348A and RS5C348B RTC chips.
 827
 828	  This driver can also be built as a module. If so, the module
 829	  will be called rtc-rs5c348.
 830
 831config RTC_DRV_MAX6902
 832	tristate "Maxim MAX6902"
 833	help
 834	  If you say yes here you will get support for the
 835	  Maxim MAX6902 SPI RTC chip.
 836
 837	  This driver can also be built as a module. If so, the module
 838	  will be called rtc-max6902.
 839
 840config RTC_DRV_PCF2123
 841	tristate "NXP PCF2123"
 842	select REGMAP_SPI
 843	help
 844	  If you say yes here you get support for the NXP PCF2123
 845	  RTC chip.
 846
 847	  This driver can also be built as a module. If so, the module
 848	  will be called rtc-pcf2123.
 849
 850config RTC_DRV_MCP795
 851	tristate "Microchip MCP795"
 852	help
 853	  If you say yes here you will get support for the Microchip MCP795.
 854
 855	  This driver can also be built as a module. If so the module
 856	  will be called rtc-mcp795.
 857
 858endif # SPI_MASTER
 859
 860#
 861# Helper to resolve issues with configs that have SPI enabled but I2C
 862# modular.  See SND_SOC_I2C_AND_SPI for more information
 863#
 864config RTC_I2C_AND_SPI
 865	tristate
 866	default m if I2C=m
 867	default y if I2C=y
 868	default y if SPI_MASTER=y
 869
 870comment "SPI and I2C RTC drivers"
 871
 872config RTC_DRV_DS3232
 873	tristate "Dallas/Maxim DS3232/DS3234"
 874	depends on RTC_I2C_AND_SPI
 875	select REGMAP_I2C if I2C
 876	select REGMAP_SPI if SPI_MASTER
 877	help
 878	  If you say yes here you get support for Dallas Semiconductor
 879	  DS3232 and DS3234 real-time clock chips. If an interrupt is associated
 880	  with the device, the alarm functionality is supported.
 881
 882	  This driver can also be built as a module.  If so, the module
 883	  will be called rtc-ds3232.
 884
 885config RTC_DRV_DS3232_HWMON
 886	bool "HWMON support for Dallas/Maxim DS3232/DS3234"
 887	depends on RTC_DRV_DS3232 && HWMON && !(RTC_DRV_DS3232=y && HWMON=m)
 888	default y
 889	help
 890	  Say Y here if you want to expose temperature sensor data on
 891	  rtc-ds3232
 892
 893config RTC_DRV_PCF2127
 894	tristate "NXP PCF2127"
 895	depends on RTC_I2C_AND_SPI
 896	select REGMAP_I2C if I2C
 897	select REGMAP_SPI if SPI_MASTER
 898	select WATCHDOG_CORE if WATCHDOG
 899	help
 900	  If you say yes here you get support for the NXP PCF2127/29 RTC
 901	  chips with integrated quartz crystal for industrial applications.
 902	  Both chips also have watchdog timer and tamper switch detection
 903	  features.
 904
 905	  PCF2127 has an additional feature of 512 bytes battery backed
 906	  memory that's accessible using nvmem interface.
 907
 908	  This driver can also be built as a module. If so, the module
 909	  will be called rtc-pcf2127.
 910
 911config RTC_DRV_RV3029C2
 912	tristate "Micro Crystal RV3029/3049"
 913	depends on RTC_I2C_AND_SPI
 914	select REGMAP_I2C if I2C
 915	select REGMAP_SPI if SPI_MASTER
 916	help
 917	  If you say yes here you get support for the Micro Crystal
 918	  RV3029 and RV3049 RTC chips.
 919
 920	  This driver can also be built as a module. If so, the module
 921	  will be called rtc-rv3029c2.
 922
 923config RTC_DRV_RV3029_HWMON
 924	bool "HWMON support for RV3029/3049"
 925	depends on RTC_DRV_RV3029C2 && HWMON
 926	depends on !(RTC_DRV_RV3029C2=y && HWMON=m)
 927	default y
 928	help
 929	  Say Y here if you want to expose temperature sensor data on
 930	  rtc-rv3029.
 931
 932config RTC_DRV_RX6110
 933	tristate "Epson RX-6110"
 934	depends on RTC_I2C_AND_SPI
 935	select REGMAP_SPI if SPI_MASTER
 936	select REGMAP_I2C if I2C
 937	help
 938	  If you say yes here you will get support for the Epson RX-6110.
 939
 940	  This driver can also be built as a module. If so the module
 941	  will be called rtc-rx6110.
 942
 943comment "Platform RTC drivers"
 944
 945# this 'CMOS' RTC driver is arch dependent because it requires
 946# <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 947# global rtc_lock ... it's not yet just another platform_device.
 948
 949config RTC_DRV_CMOS
 950	tristate "PC-style 'CMOS'"
 951	depends on X86 || ARM || PPC || MIPS || SPARC64
 952	default y if X86
 953	select RTC_MC146818_LIB
 954	help
 955	  Say "yes" here to get direct support for the real time clock
 956	  found in every PC or ACPI-based system, and some other boards.
 957	  Specifically the original MC146818, compatibles like those in
 958	  PC south bridges, the DS12887 or M48T86, some multifunction
 959	  or LPC bus chips, and so on.
 960
 961	  Your system will need to define the platform device used by
 962	  this driver, otherwise it won't be accessible. This means
 963	  you can safely enable this driver if you don't know whether
 964	  or not your board has this kind of hardware.
 965
 966	  This driver can also be built as a module. If so, the module
 967	  will be called rtc-cmos.
 968
 969config RTC_DRV_ALPHA
 970	bool "Alpha PC-style CMOS"
 971	depends on ALPHA
 972	select RTC_MC146818_LIB
 973	default y
 974	help
 975	  Direct support for the real-time clock found on every Alpha
 976	  system, specifically MC146818 compatibles.  If in doubt, say Y.
 977
 978config RTC_DRV_DS1216
 979	tristate "Dallas DS1216"
 980	depends on SNI_RM
 981	help
 982	  If you say yes here you get support for the Dallas DS1216 RTC chips.
 983
 984config RTC_DRV_DS1286
 985	tristate "Dallas DS1286"
 986	depends on HAS_IOMEM
 987	help
 988	  If you say yes here you get support for the Dallas DS1286 RTC chips.
 989
 990config RTC_DRV_DS1511
 991	tristate "Dallas DS1511"
 992	depends on HAS_IOMEM
 993	help
 994	  If you say yes here you get support for the
 995	  Dallas DS1511 timekeeping/watchdog chip.
 996
 997	  This driver can also be built as a module. If so, the module
 998	  will be called rtc-ds1511.
 999
1000config RTC_DRV_DS1553
1001	tristate "Maxim/Dallas DS1553"
1002	depends on HAS_IOMEM
1003	help
1004	  If you say yes here you get support for the
1005	  Maxim/Dallas DS1553 timekeeping chip.
1006
1007	  This driver can also be built as a module. If so, the module
1008	  will be called rtc-ds1553.
1009
1010config RTC_DRV_DS1685_FAMILY
1011	tristate "Dallas/Maxim DS1685 Family"
1012	depends on HAS_IOMEM
1013	help
1014	  If you say yes here you get support for the Dallas/Maxim DS1685
1015	  family of real time chips.  This family includes the DS1685/DS1687,
1016	  DS1689/DS1693, DS17285/DS17287, DS17485/DS17487, and
1017	  DS17885/DS17887 chips.
1018
1019	  This driver can also be built as a module. If so, the module
1020	  will be called rtc-ds1685.
1021
1022choice
1023	prompt "Subtype"
1024	depends on RTC_DRV_DS1685_FAMILY
1025	default RTC_DRV_DS1685
1026
1027config RTC_DRV_DS1685
1028	bool "DS1685/DS1687"
1029	help
1030	  This enables support for the Dallas/Maxim DS1685/DS1687 real time
1031	  clock chip.
1032
1033	  This chip is commonly found in SGI O2 (IP32) and SGI Octane (IP30)
1034	  systems, as well as EPPC-405-UC modules by electronic system design
1035	  GmbH.
1036
1037config RTC_DRV_DS1689
1038	bool "DS1689/DS1693"
1039	help
1040	  This enables support for the Dallas/Maxim DS1689/DS1693 real time
1041	  clock chip.
1042
1043	  This is an older RTC chip, supplanted by the DS1685/DS1687 above,
1044	  which supports a few minor features such as Vcc, Vbat, and Power
1045	  Cycle counters, plus a customer-specific, 8-byte ROM/Serial number.
1046
1047	  It also works for the even older DS1688/DS1691 RTC chips, which are
1048	  virtually the same and carry the same model number.  Both chips
1049	  have 114 bytes of user NVRAM.
1050
1051config RTC_DRV_DS17285
1052	bool "DS17285/DS17287"
1053	help
1054	  This enables support for the Dallas/Maxim DS17285/DS17287 real time
1055	  clock chip.
1056
1057	  This chip features 2kb of extended NV-SRAM.  It may possibly be
1058	  found in some SGI O2 systems (rare).
1059
1060config RTC_DRV_DS17485
1061	bool "DS17485/DS17487"
1062	help
1063	  This enables support for the Dallas/Maxim DS17485/DS17487 real time
1064	  clock chip.
1065
1066	  This chip features 4kb of extended NV-SRAM.
1067
1068config RTC_DRV_DS17885
1069	bool "DS17885/DS17887"
1070	help
1071	  This enables support for the Dallas/Maxim DS17885/DS17887 real time
1072	  clock chip.
1073
1074	  This chip features 8kb of extended NV-SRAM.
1075
1076endchoice
1077
1078config RTC_DRV_DS1742
1079	tristate "Maxim/Dallas DS1742/1743"
1080	depends on HAS_IOMEM
1081	help
1082	  If you say yes here you get support for the
1083	  Maxim/Dallas DS1742/1743 timekeeping chip.
1084
1085	  This driver can also be built as a module. If so, the module
1086	  will be called rtc-ds1742.
1087
1088config RTC_DRV_DS2404
1089	tristate "Maxim/Dallas DS2404"
1090	help
1091	  If you say yes here you get support for the
1092	  Dallas DS2404 RTC chip.
1093
1094	  This driver can also be built as a module. If so, the module
1095	  will be called rtc-ds2404.
1096
1097config RTC_DRV_DA9052
1098	tristate "Dialog DA9052/DA9053 RTC"
1099	depends on PMIC_DA9052
1100	help
1101	  Say y here to support the RTC driver for Dialog Semiconductor
1102	  DA9052-BC and DA9053-AA/Bx PMICs.
1103
1104config RTC_DRV_DA9055
1105	tristate "Dialog Semiconductor DA9055 RTC"
1106	depends on MFD_DA9055
1107	help
1108	  If you say yes here you will get support for the
1109	  RTC of the Dialog DA9055 PMIC.
1110
1111	  This driver can also be built as a module. If so, the module
1112	  will be called rtc-da9055
1113
1114config RTC_DRV_DA9063
1115	tristate "Dialog Semiconductor DA9063/DA9062 RTC"
1116	depends on MFD_DA9063 || MFD_DA9062
1117	help
1118	  If you say yes here you will get support for the RTC subsystem
1119	  for the Dialog Semiconductor PMIC chips DA9063 and DA9062.
1120
1121	  This driver can also be built as a module. If so, the module
1122	  will be called "rtc-da9063".
1123
1124config RTC_DRV_EFI
1125	tristate "EFI RTC"
1126	depends on EFI && !X86
1127	help
1128	  If you say yes here you will get support for the EFI
1129	  Real Time Clock.
1130
1131	  This driver can also be built as a module. If so, the module
1132	  will be called rtc-efi.
1133
1134config RTC_DRV_STK17TA8
1135	tristate "Simtek STK17TA8"
1136	depends on HAS_IOMEM
1137	help
1138	  If you say yes here you get support for the
1139	  Simtek STK17TA8 timekeeping chip.
1140
1141	  This driver can also be built as a module. If so, the module
1142	  will be called rtc-stk17ta8.
1143
1144config RTC_DRV_M48T86
1145	tristate "ST M48T86/Dallas DS12887"
1146	depends on HAS_IOMEM
1147	help
1148	  If you say Y here you will get support for the
1149	  ST M48T86 and Dallas DS12887 RTC chips.
1150
1151	  This driver can also be built as a module. If so, the module
1152	  will be called rtc-m48t86.
1153
1154config RTC_DRV_M48T35
1155	tristate "ST M48T35"
1156	depends on HAS_IOMEM
1157	help
1158	  If you say Y here you will get support for the
1159	  ST M48T35 RTC chip.
1160
1161	  This driver can also be built as a module, if so, the module
1162	  will be called "rtc-m48t35".
1163
1164config RTC_DRV_M48T59
1165	tristate "ST M48T59/M48T08/M48T02"
1166	depends on HAS_IOMEM
1167	help
1168	  If you say Y here you will get support for the
1169	  ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
1170
1171	  These chips are usually found in Sun SPARC and UltraSPARC
1172	  workstations.
1173
1174	  This driver can also be built as a module, if so, the module
1175	  will be called "rtc-m48t59".
1176
1177config RTC_DRV_MSM6242
1178	tristate "Oki MSM6242"
1179	depends on HAS_IOMEM
1180	help
1181	  If you say yes here you get support for the Oki MSM6242
1182	  timekeeping chip. It is used in some Amiga models (e.g. A2000).
1183
1184	  This driver can also be built as a module. If so, the module
1185	  will be called rtc-msm6242.
1186
1187config RTC_DRV_BQ4802
1188	tristate "TI BQ4802"
1189	depends on HAS_IOMEM
1190	help
1191	  If you say Y here you will get support for the TI
1192	  BQ4802 RTC chip.
1193
1194	  This driver can also be built as a module. If so, the module
1195	  will be called rtc-bq4802.
1196
1197config RTC_DRV_RP5C01
1198	tristate "Ricoh RP5C01"
1199	depends on HAS_IOMEM
1200	help
1201	  If you say yes here you get support for the Ricoh RP5C01
1202	  timekeeping chip. It is used in some Amiga models (e.g. A3000
1203	  and A4000).
1204
1205	  This driver can also be built as a module. If so, the module
1206	  will be called rtc-rp5c01.
1207
1208config RTC_DRV_V3020
1209	tristate "EM Microelectronic V3020"
1210	help
1211	  If you say yes here you will get support for the
1212	  EM Microelectronic v3020 RTC chip.
1213
1214	  This driver can also be built as a module. If so, the module
1215	  will be called rtc-v3020.
1216
 
 
 
 
 
 
 
 
 
 
 
1217config RTC_DRV_WM831X
1218	tristate "Wolfson Microelectronics WM831x RTC"
1219	depends on MFD_WM831X
1220	help
1221	  If you say yes here you will get support for the RTC subsystem
1222	  of the Wolfson Microelectronics WM831X series PMICs.
1223
1224	  This driver can also be built as a module. If so, the module
1225	  will be called "rtc-wm831x".
1226
1227config RTC_DRV_WM8350
1228	tristate "Wolfson Microelectronics WM8350 RTC"
1229	depends on MFD_WM8350
1230	help
1231	  If you say yes here you will get support for the RTC subsystem
1232	  of the Wolfson Microelectronics WM8350.
1233
1234	  This driver can also be built as a module. If so, the module
1235	  will be called "rtc-wm8350".
1236
1237config RTC_DRV_SC27XX
1238	tristate "Spreadtrum SC27xx RTC"
1239	depends on MFD_SC27XX_PMIC || COMPILE_TEST
1240	help
1241	  If you say Y here you will get support for the RTC subsystem
1242	  of the Spreadtrum SC27xx series PMICs. The SC27xx series PMICs
1243	  includes the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
1244
1245	  This driver can also be built as a module. If so, the module
1246	  will be called rtc-sc27xx.
1247
1248config RTC_DRV_SPEAR
1249	tristate "SPEAR ST RTC"
1250	depends on PLAT_SPEAR || COMPILE_TEST
1251	default y
1252	help
1253	 If you say Y here you will get support for the RTC found on
1254	 spear
1255
1256config RTC_DRV_PCF50633
1257	depends on MFD_PCF50633
1258	tristate "NXP PCF50633 RTC"
1259	help
1260	  If you say yes here you get support for the RTC subsystem of the
1261	  NXP PCF50633 used in embedded systems.
1262
1263config RTC_DRV_AB8500
1264	tristate "ST-Ericsson AB8500 RTC"
1265	depends on AB8500_CORE
1266	select RTC_INTF_DEV
1267	select RTC_INTF_DEV_UIE_EMUL
1268	help
1269	  Select this to enable the ST-Ericsson AB8500 power management IC RTC
1270	  support. This chip contains a battery- and capacitor-backed RTC.
1271
1272config RTC_DRV_OPAL
1273	tristate "IBM OPAL RTC driver"
1274	depends on PPC_POWERNV
1275	default y
1276	help
1277	  If you say yes here you get support for the PowerNV platform RTC
1278	  driver based on OPAL interfaces.
1279
1280	  This driver can also be built as a module. If so, the module
1281	  will be called rtc-opal.
1282
 
 
 
 
 
 
 
 
 
 
1283config RTC_DRV_ZYNQMP
1284	tristate "Xilinx Zynq Ultrascale+ MPSoC RTC"
1285	depends on OF && HAS_IOMEM
1286	help
1287	  If you say yes here you get support for the RTC controller found on
1288	  Xilinx Zynq Ultrascale+ MPSoC.
1289
1290config RTC_DRV_CROS_EC
1291	tristate "Chrome OS EC RTC driver"
1292	depends on CROS_EC
1293	help
1294	  If you say yes here you will get support for the
1295	  Chrome OS Embedded Controller's RTC.
1296
1297	  This driver can also be built as a module. If so, the module
1298	  will be called rtc-cros-ec.
1299
1300config RTC_DRV_NTXEC
1301	tristate "Netronix embedded controller RTC"
1302	depends on MFD_NTXEC
1303	help
1304	  Say yes here if you want to support the RTC functionality of the
1305	  embedded controller found in certain e-book readers designed by the
1306	  original design manufacturer Netronix.
1307
1308comment "on-CPU RTC drivers"
1309
1310config RTC_DRV_ASM9260
1311	tristate "Alphascale asm9260 RTC"
1312	depends on MACH_ASM9260 || COMPILE_TEST
1313	help
1314	  If you say yes here you get support for the RTC on the
1315	  Alphascale asm9260 SoC.
1316
1317	  This driver can also be built as a module. If so, the module
1318	  will be called rtc-asm9260.
1319
1320config RTC_DRV_DAVINCI
1321	tristate "TI DaVinci RTC"
1322	depends on ARCH_DAVINCI_DM365 || COMPILE_TEST
1323	help
1324	  If you say yes here you get support for the RTC on the
1325	  DaVinci platforms (DM365).
1326
1327	  This driver can also be built as a module. If so, the module
1328	  will be called rtc-davinci.
1329
1330config RTC_DRV_DIGICOLOR
1331	tristate "Conexant Digicolor RTC"
1332	depends on ARCH_DIGICOLOR || COMPILE_TEST
1333	help
1334	  If you say yes here you get support for the RTC on Conexant
1335	  Digicolor platforms. This currently includes the CX92755 SoC.
1336
1337	  This driver can also be built as a module. If so, the module
1338	  will be called rtc-digicolor.
1339
1340config RTC_DRV_IMXDI
1341	tristate "Freescale IMX DryIce Real Time Clock"
1342	depends on ARCH_MXC
1343	depends on OF
1344	help
1345	   Support for Freescale IMX DryIce RTC
1346
1347	   This driver can also be built as a module, if so, the module
1348	   will be called "rtc-imxdi".
1349
1350config RTC_DRV_FSL_FTM_ALARM
1351	tristate "Freescale FlexTimer alarm timer"
1352	depends on ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
1353	help
1354	   For the FlexTimer in LS1012A, LS1021A, LS1028A, LS1043A, LS1046A,
1355	   LS1088A, LS208xA, we can use FTM as the wakeup source.
1356
1357	   Say y here to enable FTM alarm support. The FTM alarm provides
1358	   alarm functions for wakeup system from deep sleep.
1359
1360	   This driver can also be built as a module, if so, the module
1361	   will be called "rtc-fsl-ftm-alarm".
1362
1363config RTC_DRV_MESON
1364	tristate "Amlogic Meson RTC"
1365	depends on (ARM && ARCH_MESON) || COMPILE_TEST
1366	select REGMAP_MMIO
1367	help
1368	   Support for the RTC block on the Amlogic Meson6, Meson8, Meson8b
1369	   and Meson8m2 SoCs.
1370
1371	   This driver can also be built as a module, if so, the module
1372	   will be called "rtc-meson".
1373
1374config RTC_DRV_MESON_VRTC
1375	tristate "Amlogic Meson Virtual RTC"
1376	depends on ARCH_MESON || COMPILE_TEST
1377	default m if ARCH_MESON
1378	help
1379	  If you say yes here you will get support for the
1380	  Virtual RTC of Amlogic SoCs.
1381
1382	  This driver can also be built as a module. If so, the module
1383	  will be called rtc-meson-vrtc.
1384
1385config RTC_DRV_OMAP
1386	tristate "TI OMAP Real Time Clock"
1387	depends on ARCH_OMAP || ARCH_DAVINCI || COMPILE_TEST
1388	depends on OF
1389	depends on PINCTRL
1390	select GENERIC_PINCONF
1391	help
1392	  Say "yes" here to support the on chip real time clock
1393	  present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx.
1394
1395	  This driver can also be built as a module, if so, module
1396	  will be called rtc-omap.
1397
1398config HAVE_S3C_RTC
1399	bool
1400	help
1401	  This will include RTC support for Samsung SoCs. If
1402	  you want to include RTC support for any machine, kindly
1403	  select this in the respective mach-XXXX/Kconfig file.
1404
1405config RTC_DRV_S3C
1406	tristate "Samsung S3C series SoC RTC"
1407	depends on ARCH_S3C64XX || HAVE_S3C_RTC || COMPILE_TEST
 
1408	help
1409	  RTC (Realtime Clock) driver for the clock inbuilt into the
1410	  Samsung S3C24XX series of SoCs. This can provide periodic
1411	  interrupt rates from 1Hz to 64Hz for user programs, and
1412	  wakeup from Alarm.
1413
1414	  The driver currently supports the common features on all the
1415	  S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
1416	  and S3C2442.
1417
1418	  This driver can also be build as a module. If so, the module
1419	  will be called rtc-s3c.
1420
1421config RTC_DRV_EP93XX
1422	tristate "Cirrus Logic EP93XX"
1423	depends on ARCH_EP93XX || COMPILE_TEST
1424	help
1425	  If you say yes here you get support for the
1426	  RTC embedded in the Cirrus Logic EP93XX processors.
1427
1428	  This driver can also be built as a module. If so, the module
1429	  will be called rtc-ep93xx.
1430
1431config RTC_DRV_SA1100
1432	tristate "SA11x0/PXA2xx/PXA910"
1433	depends on ARCH_SA1100 || ARCH_PXA || ARCH_MMP
1434	help
1435	  If you say Y here you will get access to the real time clock
1436	  built into your SA11x0 or PXA2xx CPU.
1437
1438	  To compile this driver as a module, choose M here: the
1439	  module will be called rtc-sa1100.
1440
1441config RTC_DRV_SH
1442	tristate "SuperH On-Chip RTC"
1443	depends on SUPERH || ARCH_RENESAS
1444	help
1445	  Say Y here to enable support for the on-chip RTC found in
1446	  most SuperH processors. This RTC is also found in RZ/A SoCs.
1447
1448	  To compile this driver as a module, choose M here: the
1449	  module will be called rtc-sh.
1450
1451config RTC_DRV_VR41XX
1452	tristate "NEC VR41XX"
1453	depends on CPU_VR41XX || COMPILE_TEST
1454	help
1455	  If you say Y here you will get access to the real time clock
1456	  built into your NEC VR41XX CPU.
 
 
 
1457
1458	  To compile this driver as a module, choose M here: the
1459	  module will be called rtc-vr41xx.
1460
1461config RTC_DRV_PL030
1462	tristate "ARM AMBA PL030 RTC"
1463	depends on ARM_AMBA
1464	help
1465	  If you say Y here you will get access to ARM AMBA
1466	  PrimeCell PL030 RTC found on certain ARM SOCs.
1467
1468	  To compile this driver as a module, choose M here: the
1469	  module will be called rtc-pl030.
1470
1471config RTC_DRV_PL031
1472	tristate "ARM AMBA PL031 RTC"
1473	depends on ARM_AMBA
1474	help
1475	  If you say Y here you will get access to ARM AMBA
1476	  PrimeCell PL031 RTC found on certain ARM SOCs.
1477
1478	  To compile this driver as a module, choose M here: the
1479	  module will be called rtc-pl031.
1480
1481config RTC_DRV_AT91RM9200
1482	tristate "AT91RM9200 or some AT91SAM9 RTC"
1483	depends on ARCH_AT91 || COMPILE_TEST
1484	depends on OF
1485	help
1486	  Driver for the internal RTC (Realtime Clock) module found on
1487	  Atmel AT91RM9200's and some  AT91SAM9 chips. On AT91SAM9 chips
1488	  this is powered by the backup power supply.
1489
1490config RTC_DRV_AT91SAM9
1491	tristate "AT91SAM9 RTT as RTC"
1492	depends on ARCH_AT91 || COMPILE_TEST
1493	depends on OF && HAS_IOMEM
1494	select MFD_SYSCON
1495	help
1496	  Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
1497	  can be used as an RTC thanks to the backup power supply (e.g. a
1498	  small coin cell battery) which keeps this block and the GPBR
1499	  (General Purpose Backup Registers) block powered when the device
1500	  is shutdown.
1501	  Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
1502	  probably want to use the real RTC block instead of the "RTT as an
1503	  RTC" driver.
1504
1505config RTC_DRV_AU1XXX
1506	tristate "Au1xxx Counter0 RTC support"
1507	depends on MIPS_ALCHEMY
1508	help
1509	  This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
1510	  counter) to be used as a RTC.
1511
1512	  This driver can also be built as a module. If so, the module
1513	  will be called rtc-au1xxx.
1514
1515config RTC_DRV_RS5C313
1516	tristate "Ricoh RS5C313"
1517	depends on SH_LANDISK
1518	help
1519	  If you say yes here you get support for the Ricoh RS5C313 RTC chips.
1520
 
 
 
 
 
 
 
1521config RTC_DRV_GENERIC
1522	tristate "Generic RTC support"
1523	# Please consider writing a new RTC driver instead of using the generic
1524	# RTC abstraction
1525	depends on PARISC || M68K || PPC || SUPERH || COMPILE_TEST
1526	help
1527	  Say Y or M here to enable RTC support on systems using the generic
1528	  RTC abstraction. If you do not know what you are doing, you should
1529	  just say Y.
1530
1531config RTC_DRV_PXA
1532	tristate "PXA27x/PXA3xx"
1533	depends on ARCH_PXA
1534	select RTC_DRV_SA1100
1535	help
1536	 If you say Y here you will get access to the real time clock
1537	 built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs
1538	 consisting of an SA1100 compatible RTC and the extended PXA RTC.
1539
1540	 This RTC driver uses PXA RTC registers available since pxa27x
1541	 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
1542
1543config RTC_DRV_VT8500
1544	tristate "VIA/WonderMedia 85xx SoC RTC"
1545	depends on ARCH_VT8500 || COMPILE_TEST
1546	help
1547	  If you say Y here you will get access to the real time clock
1548	  built into your VIA VT8500 SoC or its relatives.
1549
1550
1551config RTC_DRV_SUN4V
1552	bool "SUN4V Hypervisor RTC"
1553	depends on SPARC64
1554	help
1555	  If you say Y here you will get support for the Hypervisor
1556	  based RTC on SUN4V systems.
1557
1558config RTC_DRV_SUN6I
1559	bool "Allwinner A31 RTC"
1560	default MACH_SUN6I || MACH_SUN8I
1561	depends on COMMON_CLK
1562	depends on ARCH_SUNXI || COMPILE_TEST
1563	help
1564	  If you say Y here you will get support for the RTC found in
1565	  some Allwinner SoCs like the A31 or the A64.
1566
1567config RTC_DRV_SUNXI
1568	tristate "Allwinner sun4i/sun7i RTC"
1569	depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
1570	help
1571	  If you say Y here you will get support for the RTC found on
1572	  Allwinner A10/A20.
1573
1574config RTC_DRV_STARFIRE
1575	bool "Starfire RTC"
1576	depends on SPARC64
1577	help
1578	  If you say Y here you will get support for the RTC found on
1579	  Starfire systems.
1580
1581config RTC_DRV_MV
1582	tristate "Marvell SoC RTC"
1583	depends on ARCH_DOVE || ARCH_MVEBU || COMPILE_TEST
1584	help
1585	  If you say yes here you will get support for the in-chip RTC
1586	  that can be found in some of Marvell's SoC devices, such as
1587	  the Kirkwood 88F6281 and 88F6192.
1588
1589	  This driver can also be built as a module. If so, the module
1590	  will be called rtc-mv.
1591
1592config RTC_DRV_ARMADA38X
1593	tristate "Armada 38x Marvell SoC RTC"
1594	depends on ARCH_MVEBU || COMPILE_TEST
1595	depends on OF
1596	help
1597	  If you say yes here you will get support for the in-chip RTC
1598	  that can be found in the Armada 38x Marvell's SoC device
1599
1600	  This driver can also be built as a module. If so, the module
1601	  will be called armada38x-rtc.
1602
1603config RTC_DRV_CADENCE
1604	tristate "Cadence RTC driver"
1605	depends on OF && HAS_IOMEM
1606	help
1607	  If you say Y here you will get access to Cadence RTC IP
1608	  found on certain SOCs.
1609
1610	  To compile this driver as a module, choose M here: the
1611	  module will be called rtc-cadence.
1612
1613config RTC_DRV_FTRTC010
1614	tristate "Faraday Technology FTRTC010 RTC"
1615	depends on HAS_IOMEM
1616	default ARCH_GEMINI
1617	help
1618	  If you say Y here you will get support for the
1619	  Faraday Technolog FTRTC010 found on e.g. Gemini SoC's.
1620
1621	  This driver can also be built as a module. If so, the module
1622	  will be called rtc-ftrtc010.
1623
1624config RTC_DRV_PS3
1625	tristate "PS3 RTC"
1626	depends on PPC_PS3
1627	help
1628	  If you say yes here you will get support for the RTC on PS3.
1629
1630	  This driver can also be built as a module. If so, the module
1631	  will be called rtc-ps3.
1632
1633config RTC_DRV_STMP
1634	tristate "Freescale STMP3xxx/i.MX23/i.MX28 RTC"
1635	depends on ARCH_MXS || COMPILE_TEST
1636	select STMP_DEVICE
1637	help
1638	  If you say yes here you will get support for the onboard
1639	  STMP3xxx/i.MX23/i.MX28 RTC.
1640
1641	  This driver can also be built as a module. If so, the module
1642	  will be called rtc-stmp3xxx.
1643
1644config RTC_DRV_PCAP
1645	tristate "PCAP RTC"
1646	depends on EZX_PCAP
1647	help
1648	  If you say Y here you will get support for the RTC found on
1649	  the PCAP2 ASIC used on some Motorola phones.
1650
1651config RTC_DRV_MC13XXX
1652	depends on MFD_MC13XXX
1653	tristate "Freescale MC13xxx RTC"
1654	help
1655	  This enables support for the RTCs found on Freescale's PMICs
1656	  MC13783 and MC13892.
1657
1658config RTC_DRV_MPC5121
1659	tristate "Freescale MPC5121 built-in RTC"
1660	depends on PPC_MPC512x || PPC_MPC52xx
1661	help
1662	  If you say yes here you will get support for the
1663	  built-in RTC on MPC5121 or on MPC5200.
1664
1665	  This driver can also be built as a module. If so, the module
1666	  will be called rtc-mpc5121.
1667
1668config RTC_DRV_JZ4740
1669	tristate "Ingenic JZ4740 SoC"
1670	depends on MIPS || COMPILE_TEST
1671	depends on OF
1672	help
1673	  If you say yes here you get support for the Ingenic JZ47xx SoCs RTC
1674	  controllers.
1675
1676	  This driver can also be built as a module. If so, the module
1677	  will be called rtc-jz4740.
1678
1679config RTC_DRV_LPC24XX
1680	tristate "NXP RTC for LPC178x/18xx/408x/43xx"
1681	depends on ARCH_LPC18XX || COMPILE_TEST
1682	depends on OF && HAS_IOMEM
1683	help
1684	  This enables support for the NXP RTC found which can be found on
1685	  NXP LPC178x/18xx/408x/43xx devices.
1686
1687	  If you have one of the devices above enable this driver to use
1688	  the hardware RTC. This driver can also be built as a module. If
1689	  so, the module will be called rtc-lpc24xx.
1690
1691config RTC_DRV_LPC32XX
1692	depends on ARCH_LPC32XX || COMPILE_TEST
1693	tristate "NXP LPC32XX RTC"
1694	help
1695	  This enables support for the NXP RTC in the LPC32XX
1696
1697	  This driver can also be built as a module. If so, the module
1698	  will be called rtc-lpc32xx.
1699
1700config RTC_DRV_PM8XXX
1701	tristate "Qualcomm PMIC8XXX RTC"
1702	depends on MFD_PM8XXX || MFD_SPMI_PMIC || COMPILE_TEST
1703	help
1704	  If you say yes here you get support for the
1705	  Qualcomm PMIC8XXX RTC.
1706
1707	  To compile this driver as a module, choose M here: the
1708	  module will be called rtc-pm8xxx.
1709
1710config RTC_DRV_TEGRA
1711	tristate "NVIDIA Tegra Internal RTC driver"
1712	depends on ARCH_TEGRA || COMPILE_TEST
1713	help
1714	  If you say yes here you get support for the
1715	  Tegra 200 series internal RTC module.
1716
1717	  This drive can also be built as a module. If so, the module
1718	  will be called rtc-tegra.
1719
1720config RTC_DRV_LOONGSON1
1721	tristate "loongson1 RTC support"
1722	depends on MACH_LOONGSON32
1723	help
1724	  This is a driver for the loongson1 on-chip Counter0 (Time-Of-Year
1725	  counter) to be used as a RTC.
1726
1727	  This driver can also be built as a module. If so, the module
1728	  will be called rtc-ls1x.
1729
1730config RTC_DRV_MXC
1731	tristate "Freescale MXC Real Time Clock"
1732	depends on ARCH_MXC || COMPILE_TEST
1733	depends on HAS_IOMEM
1734	depends on OF
1735	help
1736	   If you say yes here you get support for the Freescale MXC
1737	   RTC module.
1738
1739	   This driver can also be built as a module, if so, the module
1740	   will be called "rtc-mxc".
1741
1742config RTC_DRV_MXC_V2
1743	tristate "Freescale MXC Real Time Clock for i.MX53"
1744	depends on ARCH_MXC || COMPILE_TEST
1745	depends on HAS_IOMEM
1746	depends on OF
1747	help
1748	   If you say yes here you get support for the Freescale MXC
1749	   SRTC module in i.MX53 processor.
1750
1751	   This driver can also be built as a module, if so, the module
1752	   will be called "rtc-mxc_v2".
1753
1754config RTC_DRV_SNVS
1755	tristate "Freescale SNVS RTC support"
1756	select REGMAP_MMIO
1757	depends on ARCH_MXC || COMPILE_TEST
1758	depends on HAS_IOMEM
1759	depends on OF
1760	help
1761	   If you say yes here you get support for the Freescale SNVS
1762	   Low Power (LP) RTC module.
1763
1764	   This driver can also be built as a module, if so, the module
1765	   will be called "rtc-snvs".
1766
1767config RTC_DRV_IMX_SC
1768	depends on IMX_SCU
1769	depends on HAVE_ARM_SMCCC
1770	tristate "NXP i.MX System Controller RTC support"
1771	help
1772	   If you say yes here you get support for the NXP i.MX System
1773	   Controller RTC module.
1774
1775config RTC_DRV_ST_LPC
1776	tristate "STMicroelectronics LPC RTC"
1777	depends on ARCH_STI
1778	depends on OF
1779	help
1780	  Say Y here to include STMicroelectronics Low Power Controller
1781	  (LPC) based RTC support.
1782
1783	  To compile this driver as a module, choose M here: the
1784	  module will be called rtc-st-lpc.
1785
1786config RTC_DRV_MOXART
1787	tristate "MOXA ART RTC"
1788	depends on ARCH_MOXART || COMPILE_TEST
1789	help
1790	   If you say yes here you get support for the MOXA ART
1791	   RTC module.
1792
1793	   This driver can also be built as a module. If so, the module
1794	   will be called rtc-moxart
1795
1796config RTC_DRV_MT2712
1797	tristate "MediaTek MT2712 SoC based RTC"
1798	depends on ARCH_MEDIATEK || COMPILE_TEST
1799	help
1800	  This enables support for the real time clock built in the MediaTek
1801	  SoCs for MT2712.
1802
1803	  This drive can also be built as a module. If so, the module
1804	  will be called rtc-mt2712.
1805
1806config RTC_DRV_MT6397
1807	tristate "MediaTek PMIC based RTC"
1808	depends on MFD_MT6397 || (COMPILE_TEST && IRQ_DOMAIN)
1809	help
1810	  This selects the MediaTek(R) RTC driver. RTC is part of MediaTek
1811	  MT6397 PMIC. You should enable MT6397 PMIC MFD before select
1812	  MediaTek(R) RTC driver.
1813
1814	  If you want to use MediaTek(R) RTC interface, select Y or M here.
1815
1816config RTC_DRV_MT7622
1817	tristate "MediaTek SoC based RTC"
1818	depends on ARCH_MEDIATEK || COMPILE_TEST
1819	help
1820	  This enables support for the real time clock built in the MediaTek
1821	  SoCs.
1822
1823	  This drive can also be built as a module. If so, the module
1824	  will be called rtc-mt7622.
1825
1826config RTC_DRV_XGENE
1827	tristate "APM X-Gene RTC"
1828	depends on HAS_IOMEM
1829	depends on ARCH_XGENE || COMPILE_TEST
1830	help
1831	  If you say yes here you get support for the APM X-Gene SoC real time
1832	  clock.
1833
1834	  This driver can also be built as a module, if so, the module
1835	  will be called "rtc-xgene".
1836
1837config RTC_DRV_PIC32
1838	tristate "Microchip PIC32 RTC"
1839	depends on MACH_PIC32
1840	default y
1841	help
1842	   If you say yes here you get support for the PIC32 RTC module.
1843
1844	   This driver can also be built as a module. If so, the module
1845	   will be called rtc-pic32
1846
1847config RTC_DRV_R7301
1848	tristate "EPSON TOYOCOM RTC-7301SF/DG"
1849	select REGMAP_MMIO
1850	depends on OF && HAS_IOMEM
1851	help
1852	   If you say yes here you get support for the EPSON TOYOCOM
1853	   RTC-7301SF/DG chips.
1854
1855	   This driver can also be built as a module. If so, the module
1856	   will be called rtc-r7301.
1857
1858config RTC_DRV_STM32
1859	tristate "STM32 RTC"
1860	select REGMAP_MMIO
1861	depends on ARCH_STM32 || COMPILE_TEST
1862	help
1863	   If you say yes here you get support for the STM32 On-Chip
1864	   Real Time Clock.
1865
1866	   This driver can also be built as a module, if so, the module
1867	   will be called "rtc-stm32".
1868
1869config RTC_DRV_CPCAP
1870	depends on MFD_CPCAP
1871	tristate "Motorola CPCAP RTC"
1872	help
1873	   Say y here for CPCAP rtc found on some Motorola phones
1874	   and tablets such as Droid 4.
1875
1876config RTC_DRV_RTD119X
1877	bool "Realtek RTD129x RTC"
1878	depends on ARCH_REALTEK || COMPILE_TEST
1879	default ARCH_REALTEK
1880	help
1881	  If you say yes here, you get support for the RTD1295 SoC
1882	  Real Time Clock.
1883
1884config RTC_DRV_ASPEED
1885	tristate "ASPEED RTC"
1886	depends on OF
1887	depends on ARCH_ASPEED || COMPILE_TEST
1888	help
1889	  If you say yes here you get support for the ASPEED BMC SoC real time
1890	  clocks.
1891
1892	  This driver can also be built as a module, if so, the module
1893	  will be called "rtc-aspeed".
1894
 
 
 
 
 
 
 
 
 
 
 
1895comment "HID Sensor RTC drivers"
1896
1897config RTC_DRV_HID_SENSOR_TIME
1898	tristate "HID Sensor Time"
1899	depends on USB_HID
1900	depends on HID_SENSOR_HUB && IIO
1901	select HID_SENSOR_IIO_COMMON
1902	help
1903	  Say yes here to build support for the HID Sensors of type Time.
1904	  This drivers makes such sensors available as RTCs.
1905
1906	  If this driver is compiled as a module, it will be named
1907	  rtc-hid-sensor-time.
1908
1909config RTC_DRV_GOLDFISH
1910	tristate "Goldfish Real Time Clock"
1911	depends on HAS_IOMEM
1912	help
1913	  Say yes to enable RTC driver for the Goldfish based virtual platform.
1914
1915	  Goldfish is a code name for the virtual platform developed by Google
1916	  for Android emulation.
1917
1918config RTC_DRV_WILCO_EC
1919	tristate "Wilco EC RTC"
1920	depends on WILCO_EC
1921	default m
1922	help
1923	  If you say yes here, you get read/write support for the Real Time
1924	  Clock on the Wilco Embedded Controller (Wilco is a kind of Chromebook)
1925
1926	  This can also be built as a module. If so, the module will
1927	  be named "rtc_wilco_ec".
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1928
1929endif # RTC_CLASS