drivers/rtc/Kconfig

   1 #
   2 # RTC class/drivers configuration
   3 #
   4
   5 config RTC_LIB
   6         tristate
   7
   8 menuconfig RTC_CLASS
   9         tristate "Real Time Clock"
  10         default n
  11         depends on !S390
  12         select RTC_LIB
  13         help
  14           Generic RTC class support. If you say yes here, you will
  15           be allowed to plug one or more RTCs to your system. You will
  16           probably want to enable one or more of the interfaces below.
  17
  18           This driver can also be built as a module. If so, the module
  19           will be called rtc-core.
  20
  21 if RTC_CLASS
  22
  23 config RTC_HCTOSYS
  24         bool "Set system time from RTC on startup and resume"
  25         depends on RTC_CLASS = y
  26         default y
  27         help
  28           If you say yes here, the system time (wall clock) will be set using
  29           the value read from a specified RTC device. This is useful to avoid
  30           unnecessary fsck runs at boot time, and to network better.
  31
  32 config RTC_HCTOSYS_DEVICE
  33         string "RTC used to set the system time"
  34         depends on RTC_HCTOSYS = y
  35         default "rtc0"
  36         help
  37           The RTC device that will be used to (re)initialize the system
  38           clock, usually rtc0.  Initialization is done when the system
  39           starts up, and when it resumes from a low power state.  This
  40           device should record time in UTC, since the kernel won't do
  41           timezone correction.
  42
  43           The driver for this RTC device must be loaded before late_initcall
  44           functions run, so it must usually be statically linked.
  45
  46           This clock should be battery-backed, so that it reads the correct
  47           time when the system boots from a power-off state.  Otherwise, your
  48           system will need an external clock source (like an NTP server).
  49
  50           If the clock you specify here is not battery backed, it may still
  51           be useful to reinitialize system time when resuming from system
  52           sleep states. Do not specify an RTC here unless it stays powered
  53           during all this system's supported sleep states.
  54
  55 config RTC_DEBUG
  56         bool "RTC debug support"
  57         depends on RTC_CLASS = y
  58         help
  59           Say yes here to enable debugging support in the RTC framework
  60           and individual RTC drivers.
  61
  62 comment "RTC interfaces"
  63
  64 config RTC_INTF_SYSFS
  65         boolean "/sys/class/rtc/rtcN (sysfs)"
  66         depends on SYSFS
  67         default RTC_CLASS
  68         help
  69           Say yes here if you want to use your RTCs using sysfs interfaces,
  70           /sys/class/rtc/rtc0 through /sys/.../rtcN.
  71
  72           This driver can also be built as a module. If so, the module
  73           will be called rtc-sysfs.
  74
  75 config RTC_INTF_PROC
  76         boolean "/proc/driver/rtc (procfs for rtc0)"
  77         depends on PROC_FS
  78         default RTC_CLASS
  79         help
  80           Say yes here if you want to use your first RTC through the proc
  81           interface, /proc/driver/rtc.  Other RTCs will not be available
  82           through that API.
  83
  84           This driver can also be built as a module. If so, the module
  85           will be called rtc-proc.
  86
  87 config RTC_INTF_DEV
  88         boolean "/dev/rtcN (character devices)"
  89         default RTC_CLASS
  90         help
  91           Say yes here if you want to use your RTCs using the /dev
  92           interfaces, which "udev" sets up as /dev/rtc0 through
  93           /dev/rtcN.  You may want to set up a symbolic link so one
  94           of these can be accessed as /dev/rtc, which is a name
  95           expected by "hwclock" and some other programs.
  96
  97           This driver can also be built as a module. If so, the module
  98           will be called rtc-dev.
  99
 100 config RTC_INTF_DEV_UIE_EMUL
 101         bool "RTC UIE emulation on dev interface"
 102         depends on RTC_INTF_DEV
 103         help
 104           Provides an emulation for RTC_UIE if the underlying rtc chip
 105           driver does not expose RTC_UIE ioctls.  Those requests generate
 106           once-per-second update interrupts, used for synchronization.
 107
 108 config RTC_DRV_TEST
 109         tristate "Test driver/device"
 110         help
 111           If you say yes here you get support for the
 112           RTC test driver. It's a software RTC which can be
 113           used to test the RTC subsystem APIs. It gets
 114           the time from the system clock.
 115           You want this driver only if you are doing development
 116           on the RTC subsystem. Please read the source code
 117           for further details.
 118
 119           This driver can also be built as a module. If so, the module
 120           will be called rtc-test.
 121
 122 comment "I2C RTC drivers"
 123         depends on I2C
 124
 125 if I2C
 126
 127 config RTC_DRV_DS1307
 128         tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00"
 129         help
 130           If you say yes here you get support for various compatible RTC
 131           chips (often with battery backup) connected with I2C.  This driver
 132           should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
 133           and probably other chips.  In some cases the RTC must already
 134           have been initialized (by manufacturing or a bootloader).
 135
 136           The first seven registers on these chips hold an RTC, and other
 137           registers may add features such as NVRAM, a trickle charger for
 138           the RTC/NVRAM backup power, and alarms.  NVRAM is visible in
 139           sysfs, but other chip features may not be available.
 140
 141           This driver can also be built as a module. If so, the module
 142           will be called rtc-ds1307.
 143
 144 config RTC_DRV_DS1374
 145         tristate "Dallas/Maxim DS1374"
 146         depends on RTC_CLASS && I2C
 147         help
 148           If you say yes here you get support for Dallas Semiconductor
 149           DS1374 real-time clock chips.  If an interrupt is associated
 150           with the device, the alarm functionality is supported.
 151
 152           This driver can also be built as a module.  If so, the module
 153           will be called rtc-ds1374.
 154
 155 config RTC_DRV_DS1672
 156         tristate "Dallas/Maxim DS1672"
 157         help
 158           If you say yes here you get support for the
 159           Dallas/Maxim DS1672 timekeeping chip.
 160
 161           This driver can also be built as a module. If so, the module
 162           will be called rtc-ds1672.
 163
 164 config RTC_DRV_MAX6900
 165         tristate "Maxim MAX6900"
 166         help
 167           If you say yes here you will get support for the
 168           Maxim MAX6900 I2C RTC chip.
 169
 170           This driver can also be built as a module. If so, the module
 171           will be called rtc-max6900.
 172
 173 config RTC_DRV_RS5C372
 174         tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
 175         help
 176           If you say yes here you get support for the
 177           Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
 178
 179           This driver can also be built as a module. If so, the module
 180           will be called rtc-rs5c372.
 181
 182 config RTC_DRV_ISL1208
 183         tristate "Intersil ISL1208"
 184         help
 185           If you say yes here you get support for the
 186           Intersil ISL1208 RTC chip.
 187
 188           This driver can also be built as a module. If so, the module
 189           will be called rtc-isl1208.
 190
 191 config RTC_DRV_X1205
 192         tristate "Xicor/Intersil X1205"
 193         help
 194           If you say yes here you get support for the
 195           Xicor/Intersil X1205 RTC chip.
 196
 197           This driver can also be built as a module. If so, the module
 198           will be called rtc-x1205.
 199
 200 config RTC_DRV_PCF8563
 201         tristate "Philips PCF8563/Epson RTC8564"
 202         help
 203           If you say yes here you get support for the
 204           Philips PCF8563 RTC chip. The Epson RTC8564
 205           should work as well.
 206
 207           This driver can also be built as a module. If so, the module
 208           will be called rtc-pcf8563.
 209
 210 config RTC_DRV_PCF8583
 211         tristate "Philips PCF8583"
 212         help
 213           If you say yes here you get support for the Philips PCF8583
 214           RTC chip found on Acorn RiscPCs. This driver supports the
 215           platform specific method of retrieving the current year from
 216           the RTC's SRAM. It will work on other platforms with the same
 217           chip, but the year will probably have to be tweaked.
 218
 219           This driver can also be built as a module. If so, the module
 220           will be called rtc-pcf8583.
 221
 222 config RTC_DRV_M41T80
 223         tristate "ST M41T65/M41T80/81/82/83/84/85/87"
 224         help
 225           If you say Y here you will get support for the ST M41T60
 226           and M41T80 RTC chips series. Currently, the following chips are
 227           supported: M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
 228           M41ST85, and M41ST87.
 229
 230           This driver can also be built as a module. If so, the module
 231           will be called rtc-m41t80.
 232
 233 config RTC_DRV_M41T80_WDT
 234         bool "ST M41T65/M41T80 series RTC watchdog timer"
 235         depends on RTC_DRV_M41T80
 236         help
 237           If you say Y here you will get support for the
 238           watchdog timer in the ST M41T60 and M41T80 RTC chips series.
 239
 240 config RTC_DRV_TWL92330
 241         boolean "TI TWL92330/Menelaus"
 242         depends on MENELAUS
 243         help
 244           If you say yes here you get support for the RTC on the
 245           TWL92330 "Menelaus" power management chip, used with OMAP2
 246           platforms.  The support is integrated with the rest of
 247           the Menelaus driver; it's not separate module.
 248
 249 config RTC_DRV_TWL4030
 250         tristate "TI TWL4030/TWL5030/TPS659x0"
 251         depends on RTC_CLASS && TWL4030_CORE
 252         help
 253           If you say yes here you get support for the RTC on the
 254           TWL4030 family chips, used mostly with OMAP3 platforms.
 255
 256           This driver can also be built as a module. If so, the module
 257           will be called rtc-twl4030.
 258
 259 config RTC_DRV_S35390A
 260         tristate "Seiko Instruments S-35390A"
 261         select BITREVERSE
 262         help
 263           If you say yes here you will get support for the Seiko
 264           Instruments S-35390A.
 265
 266           This driver can also be built as a module. If so the module
 267           will be called rtc-s35390a.
 268
 269 config RTC_DRV_FM3130
 270         tristate "Ramtron FM3130"
 271         help
 272           If you say Y here you will get support for the
 273           Ramtron FM3130 RTC chips.
 274           Ramtron FM3130 is a chip with two separate devices inside,
 275           RTC clock and FRAM. This driver provides only RTC functionality.
 276
 277           This driver can also be built as a module. If so the module
 278           will be called rtc-fm3130.
 279
 280 config RTC_DRV_RX8581
 281         tristate "Epson RX-8581"
 282         help
 283           If you say yes here you will get support for the Epson RX-8581.
 284
 285           This driver can also be built as a module. If so the module
 286           will be called rtc-rx8581.
 287
 288 endif # I2C
 289
 290 comment "SPI RTC drivers"
 291
 292 if SPI_MASTER
 293
 294 config RTC_DRV_M41T94
 295         tristate "ST M41T94"
 296         help
 297           If you say yes here you will get support for the
 298           ST M41T94 SPI RTC chip.
 299
 300           This driver can also be built as a module. If so, the module
 301           will be called rtc-m41t94.
 302
 303 config RTC_DRV_DS1305
 304         tristate "Dallas/Maxim DS1305/DS1306"
 305         help
 306           Select this driver to get support for the Dallas/Maxim DS1305
 307           and DS1306 real time clock chips.  These support a trickle
 308           charger, alarms, and NVRAM in addition to the clock.
 309
 310           This driver can also be built as a module. If so, the module
 311           will be called rtc-ds1305.
 312
 313 config RTC_DRV_DS1390
 314         tristate "Dallas/Maxim DS1390/93/94"
 315         help
 316           If you say yes here you get support for the DS1390/93/94 chips.
 317
 318           This driver only supports the RTC feature, and not other chip
 319           features such as alarms and trickle charging.
 320
 321           This driver can also be built as a module. If so, the module
 322           will be called rtc-ds1390.
 323
 324 config RTC_DRV_MAX6902
 325         tristate "Maxim MAX6902"
 326         help
 327           If you say yes here you will get support for the
 328           Maxim MAX6902 SPI RTC chip.
 329
 330           This driver can also be built as a module. If so, the module
 331           will be called rtc-max6902.
 332
 333 config RTC_DRV_R9701
 334         tristate "Epson RTC-9701JE"
 335         help
 336           If you say yes here you will get support for the
 337           Epson RTC-9701JE SPI RTC chip.
 338
 339           This driver can also be built as a module. If so, the module
 340           will be called rtc-r9701.
 341
 342 config RTC_DRV_RS5C348
 343         tristate "Ricoh RS5C348A/B"
 344         help
 345           If you say yes here you get support for the
 346           Ricoh RS5C348A and RS5C348B RTC chips.
 347
 348           This driver can also be built as a module. If so, the module
 349           will be called rtc-rs5c348.
 350
 351 config RTC_DRV_DS3234
 352         tristate "Maxim/Dallas DS3234"
 353         help
 354           If you say yes here you get support for the
 355           Maxim/Dallas DS3234 SPI RTC chip.
 356
 357           This driver can also be built as a module. If so, the module
 358           will be called rtc-ds3234.
 359
 360 endif # SPI_MASTER
 361
 362 comment "Platform RTC drivers"
 363
 364 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
 365 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
 366 # global rtc_lock ... it's not yet just another platform_device.
 367
 368 config RTC_DRV_CMOS
 369         tristate "PC-style 'CMOS'"
 370         depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
 371         default y if X86
 372         help
 373           Say "yes" here to get direct support for the real time clock
 374           found in every PC or ACPI-based system, and some other boards.
 375           Specifically the original MC146818, compatibles like those in
 376           PC south bridges, the DS12887 or M48T86, some multifunction
 377           or LPC bus chips, and so on.
 378
 379           Your system will need to define the platform device used by
 380           this driver, otherwise it won't be accessible.  This means
 381           you can safely enable this driver if you don't know whether
 382           or not your board has this kind of hardware.
 383
 384           This driver can also be built as a module. If so, the module
 385           will be called rtc-cmos.
 386
 387 config RTC_DRV_DS1216
 388         tristate "Dallas DS1216"
 389         depends on SNI_RM
 390         help
 391           If you say yes here you get support for the Dallas DS1216 RTC chips.
 392
 393 config RTC_DRV_DS1286
 394         tristate "Dallas DS1286"
 395         help
 396           If you say yes here you get support for the Dallas DS1286 RTC chips.
 397
 398 config RTC_DRV_DS1302
 399         tristate "Dallas DS1302"
 400         depends on SH_SECUREEDGE5410
 401         help
 402           If you say yes here you get support for the Dallas DS1302 RTC chips.
 403
 404 config RTC_DRV_DS1511
 405         tristate "Dallas DS1511"
 406         depends on RTC_CLASS
 407         help
 408           If you say yes here you get support for the
 409           Dallas DS1511 timekeeping/watchdog chip.
 410
 411           This driver can also be built as a module. If so, the module
 412           will be called rtc-ds1511.
 413
 414 config RTC_DRV_DS1553
 415         tristate "Maxim/Dallas DS1553"
 416         help
 417           If you say yes here you get support for the
 418           Maxim/Dallas DS1553 timekeeping chip.
 419
 420           This driver can also be built as a module. If so, the module
 421           will be called rtc-ds1553.
 422
 423 config RTC_DRV_DS1742
 424         tristate "Maxim/Dallas DS1742/1743"
 425         help
 426           If you say yes here you get support for the
 427           Maxim/Dallas DS1742/1743 timekeeping chip.
 428
 429           This driver can also be built as a module. If so, the module
 430           will be called rtc-ds1742.
 431
 432 config RTC_DRV_STK17TA8
 433         tristate "Simtek STK17TA8"
 434         depends on RTC_CLASS
 435         help
 436           If you say yes here you get support for the
 437           Simtek STK17TA8 timekeeping chip.
 438
 439           This driver can also be built as a module. If so, the module
 440           will be called rtc-stk17ta8.
 441
 442 config RTC_DRV_M48T86
 443         tristate "ST M48T86/Dallas DS12887"
 444         help
 445           If you say Y here you will get support for the
 446           ST M48T86 and Dallas DS12887 RTC chips.
 447
 448           This driver can also be built as a module. If so, the module
 449           will be called rtc-m48t86.
 450
 451 config RTC_DRV_M48T35
 452         tristate "ST M48T35"
 453         help
 454           If you say Y here you will get support for the
 455           ST M48T35 RTC chip.
 456
 457           This driver can also be built as a module, if so, the module
 458           will be called "rtc-m48t35".
 459
 460 config RTC_DRV_M48T59
 461         tristate "ST M48T59/M48T08/M48T02"
 462         help
 463           If you say Y here you will get support for the
 464           ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
 465
 466           These chips are usually found in Sun SPARC and UltraSPARC
 467           workstations.
 468
 469           This driver can also be built as a module, if so, the module
 470           will be called "rtc-m48t59".
 471
 472 config RTC_DRV_BQ4802
 473         tristate "TI BQ4802"
 474         help
 475           If you say Y here you will get support for the TI
 476           BQ4802 RTC chip.
 477
 478           This driver can also be built as a module. If so, the module
 479           will be called rtc-bq4802.
 480
 481 config RTC_DRV_V3020
 482         tristate "EM Microelectronic V3020"
 483         help
 484           If you say yes here you will get support for the
 485           EM Microelectronic v3020 RTC chip.
 486
 487           This driver can also be built as a module. If so, the module
 488           will be called rtc-v3020.
 489
 490 config RTC_DRV_WM8350
 491         tristate "Wolfson Microelectronics WM8350 RTC"
 492         depends on MFD_WM8350
 493         help
 494           If you say yes here you will get support for the RTC subsystem
 495           of the Wolfson Microelectronics WM8350.
 496
 497           This driver can also be built as a module. If so, the module
 498           will be called "rtc-wm8350".
 499
 500 comment "on-CPU RTC drivers"
 501
 502 config RTC_DRV_OMAP
 503         tristate "TI OMAP1"
 504         depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
 505         help
 506           Say "yes" here to support the real time clock on TI OMAP1 chips.
 507           This driver can also be built as a module called rtc-omap.
 508
 509 config RTC_DRV_S3C
 510         tristate "Samsung S3C series SoC RTC"
 511         depends on ARCH_S3C2410
 512         help
 513           RTC (Realtime Clock) driver for the clock inbuilt into the
 514           Samsung S3C24XX series of SoCs. This can provide periodic
 515           interrupt rates from 1Hz to 64Hz for user programs, and
 516           wakeup from Alarm.
 517
 518           The driver currently supports the common features on all the
 519           S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
 520           and S3C2442.
 521
 522           This driver can also be build as a module. If so, the module
 523           will be called rtc-s3c.
 524
 525 config RTC_DRV_EP93XX
 526         tristate "Cirrus Logic EP93XX"
 527         depends on ARCH_EP93XX
 528         help
 529           If you say yes here you get support for the
 530           RTC embedded in the Cirrus Logic EP93XX processors.
 531
 532           This driver can also be built as a module. If so, the module
 533           will be called rtc-ep93xx.
 534
 535 config RTC_DRV_SA1100
 536         tristate "SA11x0/PXA2xx"
 537         depends on ARCH_SA1100 || ARCH_PXA
 538         help
 539           If you say Y here you will get access to the real time clock
 540           built into your SA11x0 or PXA2xx CPU.
 541
 542           To compile this driver as a module, choose M here: the
 543           module will be called rtc-sa1100.
 544
 545 config RTC_DRV_SH
 546         tristate "SuperH On-Chip RTC"
 547         depends on RTC_CLASS && SUPERH
 548         help
 549           Say Y here to enable support for the on-chip RTC found in
 550           most SuperH processors.
 551
 552           To compile this driver as a module, choose M here: the
 553           module will be called rtc-sh.
 554
 555 config RTC_DRV_VR41XX
 556         tristate "NEC VR41XX"
 557         depends on CPU_VR41XX
 558         help
 559           If you say Y here you will get access to the real time clock
 560           built into your NEC VR41XX CPU.
 561
 562           To compile this driver as a module, choose M here: the
 563           module will be called rtc-vr41xx.
 564
 565 config RTC_DRV_PL030
 566         tristate "ARM AMBA PL030 RTC"
 567         depends on ARM_AMBA
 568         help
 569           If you say Y here you will get access to ARM AMBA
 570           PrimeCell PL030 RTC found on certain ARM SOCs.
 571
 572           To compile this driver as a module, choose M here: the
 573           module will be called rtc-pl030.
 574
 575 config RTC_DRV_PL031
 576         tristate "ARM AMBA PL031 RTC"
 577         depends on ARM_AMBA
 578         help
 579           If you say Y here you will get access to ARM AMBA
 580           PrimeCell PL031 RTC found on certain ARM SOCs.
 581
 582           To compile this driver as a module, choose M here: the
 583           module will be called rtc-pl031.
 584
 585 config RTC_DRV_AT32AP700X
 586         tristate "AT32AP700X series RTC"
 587         depends on PLATFORM_AT32AP
 588         help
 589           Driver for the internal RTC (Realtime Clock) on Atmel AVR32
 590           AT32AP700x family processors.
 591
 592 config RTC_DRV_AT91RM9200
 593         tristate "AT91RM9200 or AT91SAM9RL"
 594         depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
 595         help
 596           Driver for the internal RTC (Realtime Clock) module found on
 597           Atmel AT91RM9200's and AT91SAM9RL chips.  On SAM9RL chips
 598           this is powered by the backup power supply.
 599
 600 config RTC_DRV_AT91SAM9
 601         tristate "AT91SAM9x/AT91CAP9"
 602         depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
 603         help
 604           RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
 605           (Real Time Timer). These timers are powered by the backup power
 606           supply (such as a small coin cell battery), but do not need to
 607           be used as RTCs.
 608
 609           (On AT91SAM9rl chips you probably want to use the dedicated RTC
 610           module and leave the RTT available for other uses.)
 611
 612 config RTC_DRV_AT91SAM9_RTT
 613         int
 614         range 0 1
 615         default 0
 616         prompt "RTT module Number" if ARCH_AT91SAM9263
 617         depends on RTC_DRV_AT91SAM9
 618         help
 619           More than one RTT module is available.  You can choose which
 620           one will be used as an RTC.  The default of zero is normally
 621           OK to use, though some systems use that for non-RTC purposes.
 622
 623 config RTC_DRV_AT91SAM9_GPBR
 624         int
 625         range 0 3 if !ARCH_AT91SAM9263
 626         range 0 15 if ARCH_AT91SAM9263
 627         default 0
 628         prompt "Backup Register Number"
 629         depends on RTC_DRV_AT91SAM9
 630         help
 631           The RTC driver needs to use one of the General Purpose Backup
 632           Registers (GPBRs) as well as the RTT.  You can choose which one
 633           will be used.  The default of zero is normally OK to use, but
 634           on some systems other software needs to use that register.
 635
 636 config RTC_DRV_BFIN
 637         tristate "Blackfin On-Chip RTC"
 638         depends on BLACKFIN && !BF561
 639         help
 640           If you say yes here you will get support for the
 641           Blackfin On-Chip Real Time Clock.
 642
 643           This driver can also be built as a module. If so, the module
 644           will be called rtc-bfin.
 645
 646 config RTC_DRV_RS5C313
 647         tristate "Ricoh RS5C313"
 648         depends on SH_LANDISK
 649         help
 650           If you say yes here you get support for the Ricoh RS5C313 RTC chips.
 651
 652 config RTC_DRV_PARISC
 653         tristate "PA-RISC firmware RTC support"
 654         depends on PARISC
 655         help
 656           Say Y or M here to enable RTC support on PA-RISC systems using
 657           firmware calls. If you do not know what you are doing, you should
 658           just say Y.
 659
 660 config RTC_DRV_PPC
 661        tristate "PowerPC machine dependent RTC support"
 662        depends on PPC
 663        help
 664          The PowerPC kernel has machine-specific functions for accessing
 665          the RTC. This exposes that functionality through the generic RTC
 666          class.
 667
 668 config RTC_DRV_SUN4V
 669         bool "SUN4V Hypervisor RTC"
 670         depends on SPARC64
 671         help
 672           If you say Y here you will get support for the Hypervisor
 673           based RTC on SUN4V systems.
 674
 675 config RTC_DRV_STARFIRE
 676         bool "Starfire RTC"
 677         depends on SPARC64
 678         help
 679           If you say Y here you will get support for the RTC found on
 680           Starfire systems.
 681
 682 endif # RTC_CLASS