2 # RTC class/drivers configuration
9 tristate "Real Time Clock"
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.
18 This driver can also be built as a module. If so, the module
19 will be called rtc-core.
24 bool "Set system time from RTC on startup and resume"
25 depends on RTC_CLASS = y
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.
32 config RTC_HCTOSYS_DEVICE
33 string "RTC used to set the system time"
34 depends on RTC_HCTOSYS = y
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
43 The driver for this RTC device must be loaded before late_initcall
44 functions run, so it must usually be statically linked.
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).
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.
56 bool "RTC debug support"
57 depends on RTC_CLASS = y
59 Say yes here to enable debugging support in the RTC framework
60 and individual RTC drivers.
62 comment "RTC interfaces"
65 boolean "/sys/class/rtc/rtcN (sysfs)"
69 Say yes here if you want to use your RTCs using sysfs interfaces,
70 /sys/class/rtc/rtc0 through /sys/.../rtcN.
75 boolean "/proc/driver/rtc (procfs for rtc0)"
79 Say yes here if you want to use your first RTC through the proc
80 interface, /proc/driver/rtc. Other RTCs will not be available
86 boolean "/dev/rtcN (character devices)"
89 Say yes here if you want to use your RTCs using the /dev
90 interfaces, which "udev" sets up as /dev/rtc0 through
93 You may want to set up a symbolic link so one of these
94 can be accessed as /dev/rtc, which is a name
95 expected by "hwclock" and some other programs. Recent
96 versions of "udev" are known to set up the symlink for you.
100 config RTC_INTF_DEV_UIE_EMUL
101 bool "RTC UIE emulation on dev interface"
102 depends on RTC_INTF_DEV
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.
108 The emulation code will read the time from the hardware
109 clock several times per second, please enable this option
110 only if you know that you really need it.
112 config RTC_INTF_ALARM
113 bool "Android alarm driver"
117 Provides non-wakeup and rtc backed wakeup alarms based on rtc or
118 elapsed realtime, and a non-wakeup alarm on the monotonic clock.
119 Also provides an interface to set the wall time which must be used
120 for elapsed realtime to work.
122 config RTC_INTF_ALARM_DEV
123 bool "Android alarm device"
124 depends on RTC_INTF_ALARM
127 Exports the alarm interface to user-space.
131 tristate "Test driver/device"
133 If you say yes here you get support for the
134 RTC test driver. It's a software RTC which can be
135 used to test the RTC subsystem APIs. It gets
136 the time from the system clock.
137 You want this driver only if you are doing development
138 on the RTC subsystem. Please read the source code
141 This driver can also be built as a module. If so, the module
142 will be called rtc-test.
144 comment "I2C RTC drivers"
150 tristate "RK2818 or RK29 extern HYM8563 RTC"
151 depends on I2C_RK2818 || I2C_RK29
153 If you say yes here you will get support for the
154 HYM8563 I2C RTC chip.
155 This driver can also be built as a module. If so, the module
156 will be called rtc-HYM8563.
158 config RTC_DRV_DS1307
159 tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025"
161 If you say yes here you get support for various compatible RTC
162 chips (often with battery backup) connected with I2C. This driver
163 should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00,
164 EPSON RX-8025 and probably other chips. In some cases the RTC
165 must already have been initialized (by manufacturing or a
168 The first seven registers on these chips hold an RTC, and other
169 registers may add features such as NVRAM, a trickle charger for
170 the RTC/NVRAM backup power, and alarms. NVRAM is visible in
171 sysfs, but other chip features may not be available.
173 This driver can also be built as a module. If so, the module
174 will be called rtc-ds1307.
176 config RTC_DRV_DS1374
177 tristate "Dallas/Maxim DS1374"
178 depends on RTC_CLASS && I2C
180 If you say yes here you get support for Dallas Semiconductor
181 DS1374 real-time clock chips. If an interrupt is associated
182 with the device, the alarm functionality is supported.
184 This driver can also be built as a module. If so, the module
185 will be called rtc-ds1374.
187 config RTC_DRV_DS1672
188 tristate "Dallas/Maxim DS1672"
190 If you say yes here you get support for the
191 Dallas/Maxim DS1672 timekeeping chip.
193 This driver can also be built as a module. If so, the module
194 will be called rtc-ds1672.
196 config RTC_DRV_MAX6900
197 tristate "Maxim MAX6900"
199 If you say yes here you will get support for the
200 Maxim MAX6900 I2C RTC chip.
202 This driver can also be built as a module. If so, the module
203 will be called rtc-max6900.
205 config RTC_DRV_RS5C372
206 tristate "Ricoh R2025S/D, RS5C372A/B, RV5C386, RV5C387A"
208 If you say yes here you get support for the
209 Ricoh R2025S/D, RS5C372A, RS5C372B, RV5C386, and RV5C387A RTC chips.
211 This driver can also be built as a module. If so, the module
212 will be called rtc-rs5c372.
214 config RTC_DRV_ISL1208
215 tristate "Intersil ISL1208"
217 If you say yes here you get support for the
218 Intersil ISL1208 RTC chip.
220 This driver can also be built as a module. If so, the module
221 will be called rtc-isl1208.
224 tristate "Xicor/Intersil X1205"
226 If you say yes here you get support for the
227 Xicor/Intersil X1205 RTC chip.
229 This driver can also be built as a module. If so, the module
230 will be called rtc-x1205.
232 config RTC_DRV_PCF8563
233 tristate "Philips PCF8563/Epson RTC8564"
235 If you say yes here you get support for the
236 Philips PCF8563 RTC chip. The Epson RTC8564
239 This driver can also be built as a module. If so, the module
240 will be called rtc-pcf8563.
242 config RTC_DRV_PCF8583
243 tristate "Philips PCF8583"
245 If you say yes here you get support for the Philips PCF8583
246 RTC chip found on Acorn RiscPCs. This driver supports the
247 platform specific method of retrieving the current year from
248 the RTC's SRAM. It will work on other platforms with the same
249 chip, but the year will probably have to be tweaked.
251 This driver can also be built as a module. If so, the module
252 will be called rtc-pcf8583.
254 config RTC_DRV_M41T80
255 tristate "ST M41T62/65/M41T80/81/82/83/84/85/87"
257 If you say Y here you will get support for the ST M41T60
258 and M41T80 RTC chips series. Currently, the following chips are
259 supported: M41T62, M41T65, M41T80, M41T81, M41T82, M41T83, M41ST84,
260 M41ST85, and M41ST87.
262 This driver can also be built as a module. If so, the module
263 will be called rtc-m41t80.
265 config RTC_DRV_M41T80_WDT
266 bool "ST M41T65/M41T80 series RTC watchdog timer"
267 depends on RTC_DRV_M41T80
269 If you say Y here you will get support for the
270 watchdog timer in the ST M41T60 and M41T80 RTC chips series.
272 config RTC_DRV_DM355EVM
273 tristate "TI DaVinci DM355 EVM RTC"
274 depends on MFD_DM355EVM_MSP
276 Supports the RTC firmware in the MSP430 on the DM355 EVM.
278 config RTC_DRV_TWL92330
279 boolean "TI TWL92330/Menelaus"
282 If you say yes here you get support for the RTC on the
283 TWL92330 "Menelaus" power management chip, used with OMAP2
284 platforms. The support is integrated with the rest of
285 the Menelaus driver; it's not separate module.
287 config RTC_DRV_TWL4030
288 tristate "TI TWL4030/TWL5030/TPS659x0"
289 depends on RTC_CLASS && TWL4030_CORE
291 If you say yes here you get support for the RTC on the
292 TWL4030 family chips, used mostly with OMAP3 platforms.
294 This driver can also be built as a module. If so, the module
295 will be called rtc-twl4030.
297 config RTC_DRV_S35390A
298 tristate "Seiko Instruments S-35390A"
301 If you say yes here you will get support for the Seiko
302 Instruments S-35390A.
304 This driver can also be built as a module. If so the module
305 will be called rtc-s35390a.
307 config RTC_DRV_S35392A
308 tristate "Seiko Instruments S-35392A"
311 If you say yes here you will get support for the Seiko
312 Instruments S-35392A.
314 This driver can also be built as a module. If so the module
315 will be called rtc-s35392a.
317 config RTC_DRV_FM3130
318 tristate "Ramtron FM3130"
320 If you say Y here you will get support for the
321 Ramtron FM3130 RTC chips.
322 Ramtron FM3130 is a chip with two separate devices inside,
323 RTC clock and FRAM. This driver provides only RTC functionality.
325 This driver can also be built as a module. If so the module
326 will be called rtc-fm3130.
328 config RTC_DRV_RX8581
329 tristate "Epson RX-8581"
331 If you say yes here you will get support for the Epson RX-8581.
333 This driver can also be built as a module. If so the module
334 will be called rtc-rx8581.
336 config RTC_DRV_RX8025
337 tristate "Epson RX-8025SA/NB"
339 If you say yes here you get support for the Epson
340 RX-8025SA/NB RTC chips.
342 This driver can also be built as a module. If so, the module
343 will be called rtc-rx8025.
347 comment "SPI RTC drivers"
351 config RTC_DRV_M41T94
354 If you say yes here you will get support for the
355 ST M41T94 SPI RTC chip.
357 This driver can also be built as a module. If so, the module
358 will be called rtc-m41t94.
360 config RTC_DRV_DS1305
361 tristate "Dallas/Maxim DS1305/DS1306"
363 Select this driver to get support for the Dallas/Maxim DS1305
364 and DS1306 real time clock chips. These support a trickle
365 charger, alarms, and NVRAM in addition to the clock.
367 This driver can also be built as a module. If so, the module
368 will be called rtc-ds1305.
370 config RTC_DRV_DS1390
371 tristate "Dallas/Maxim DS1390/93/94"
373 If you say yes here you get support for the
374 Dallas/Maxim DS1390/93/94 chips.
376 This driver only supports the RTC feature, and not other chip
377 features such as alarms and trickle charging.
379 This driver can also be built as a module. If so, the module
380 will be called rtc-ds1390.
382 config RTC_DRV_MAX6902
383 tristate "Maxim MAX6902"
385 If you say yes here you will get support for the
386 Maxim MAX6902 SPI RTC chip.
388 This driver can also be built as a module. If so, the module
389 will be called rtc-max6902.
392 tristate "Epson RTC-9701JE"
394 If you say yes here you will get support for the
395 Epson RTC-9701JE SPI RTC chip.
397 This driver can also be built as a module. If so, the module
398 will be called rtc-r9701.
400 config RTC_DRV_RS5C348
401 tristate "Ricoh RS5C348A/B"
403 If you say yes here you get support for the
404 Ricoh RS5C348A and RS5C348B RTC chips.
406 This driver can also be built as a module. If so, the module
407 will be called rtc-rs5c348.
409 config RTC_DRV_DS3234
410 tristate "Maxim/Dallas DS3234"
412 If you say yes here you get support for the
413 Maxim/Dallas DS3234 SPI RTC chip.
415 This driver can also be built as a module. If so, the module
416 will be called rtc-ds3234.
418 config RTC_DRV_PCF2123
419 tristate "NXP PCF2123"
421 If you say yes here you get support for the NXP PCF2123
424 This driver can also be built as a module. If so, the module
425 will be called rtc-pcf2123.
429 comment "Platform RTC drivers"
431 # this 'CMOS' RTC driver is arch dependent because <asm-generic/rtc.h>
432 # requires <asm/mc146818rtc.h> defining CMOS_READ/CMOS_WRITE, and a
433 # global rtc_lock ... it's not yet just another platform_device.
436 tristate "PC-style 'CMOS'"
437 depends on X86 || ALPHA || ARM || M32R || ATARI || PPC || MIPS || SPARC64
440 Say "yes" here to get direct support for the real time clock
441 found in every PC or ACPI-based system, and some other boards.
442 Specifically the original MC146818, compatibles like those in
443 PC south bridges, the DS12887 or M48T86, some multifunction
444 or LPC bus chips, and so on.
446 Your system will need to define the platform device used by
447 this driver, otherwise it won't be accessible. This means
448 you can safely enable this driver if you don't know whether
449 or not your board has this kind of hardware.
451 This driver can also be built as a module. If so, the module
452 will be called rtc-cmos.
454 config RTC_DRV_DS1216
455 tristate "Dallas DS1216"
458 If you say yes here you get support for the Dallas DS1216 RTC chips.
460 config RTC_DRV_DS1286
461 tristate "Dallas DS1286"
463 If you say yes here you get support for the Dallas DS1286 RTC chips.
465 config RTC_DRV_DS1302
466 tristate "Dallas DS1302"
467 depends on SH_SECUREEDGE5410
469 If you say yes here you get support for the Dallas DS1302 RTC chips.
471 config RTC_DRV_DS1511
472 tristate "Dallas DS1511"
475 If you say yes here you get support for the
476 Dallas DS1511 timekeeping/watchdog chip.
478 This driver can also be built as a module. If so, the module
479 will be called rtc-ds1511.
481 config RTC_DRV_DS1553
482 tristate "Maxim/Dallas DS1553"
484 If you say yes here you get support for the
485 Maxim/Dallas DS1553 timekeeping chip.
487 This driver can also be built as a module. If so, the module
488 will be called rtc-ds1553.
490 config RTC_DRV_DS1742
491 tristate "Maxim/Dallas DS1742/1743"
493 If you say yes here you get support for the
494 Maxim/Dallas DS1742/1743 timekeeping chip.
496 This driver can also be built as a module. If so, the module
497 will be called rtc-ds1742.
503 If you say yes here you will get support for the EFI
506 This driver can also be built as a module. If so, the module
507 will be called rtc-efi.
509 config RTC_DRV_STK17TA8
510 tristate "Simtek STK17TA8"
513 If you say yes here you get support for the
514 Simtek STK17TA8 timekeeping chip.
516 This driver can also be built as a module. If so, the module
517 will be called rtc-stk17ta8.
519 config RTC_DRV_M48T86
520 tristate "ST M48T86/Dallas DS12887"
522 If you say Y here you will get support for the
523 ST M48T86 and Dallas DS12887 RTC chips.
525 This driver can also be built as a module. If so, the module
526 will be called rtc-m48t86.
528 config RTC_DRV_M48T35
531 If you say Y here you will get support for the
534 This driver can also be built as a module, if so, the module
535 will be called "rtc-m48t35".
537 config RTC_DRV_M48T59
538 tristate "ST M48T59/M48T08/M48T02"
540 If you say Y here you will get support for the
541 ST M48T59 RTC chip and compatible ST M48T08 and M48T02.
543 These chips are usually found in Sun SPARC and UltraSPARC
546 This driver can also be built as a module, if so, the module
547 will be called "rtc-m48t59".
550 tristate "Freescale MXC Real Time Clock"
554 If you say yes here you get support for the Freescale MXC
557 This driver can also be built as a module, if so, the module
558 will be called "rtc-mxc".
560 config RTC_DRV_BQ4802
563 If you say Y here you will get support for the TI
566 This driver can also be built as a module. If so, the module
567 will be called rtc-bq4802.
570 tristate "EM Microelectronic V3020"
572 If you say yes here you will get support for the
573 EM Microelectronic v3020 RTC chip.
575 This driver can also be built as a module. If so, the module
576 will be called rtc-v3020.
578 config RTC_DRV_WM831X
579 tristate "Wolfson Microelectronics WM831x RTC"
580 depends on MFD_WM831X
582 If you say yes here you will get support for the RTC subsystem
583 of the Wolfson Microelectronics WM831X series PMICs.
585 This driver can also be built as a module. If so, the module
586 will be called "rtc-wm831x".
588 config RTC_DRV_WM8350
589 tristate "Wolfson Microelectronics WM8350 RTC"
590 depends on MFD_WM8350
592 If you say yes here you will get support for the RTC subsystem
593 of the Wolfson Microelectronics WM8350.
595 This driver can also be built as a module. If so, the module
596 will be called "rtc-wm8350".
598 config RTC_DRV_PCF50633
599 depends on MFD_PCF50633
600 tristate "NXP PCF50633 RTC"
602 If you say yes here you get support for the RTC subsystem of the
603 NXP PCF50633 used in embedded systems.
605 config RTC_DRV_AB3100
606 tristate "ST-Ericsson AB3100 RTC"
607 depends on AB3100_CORE
608 default y if AB3100_CORE
610 Select this to enable the ST-Ericsson AB3100 Mixed Signal IC RTC
611 support. This chip contains a battery- and capacitor-backed RTC.
614 comment "on-CPU RTC drivers"
618 depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730
620 Say "yes" here to support the real time clock on TI OMAP1 chips.
621 This driver can also be built as a module called rtc-omap.
624 tristate "Samsung S3C series SoC RTC"
625 depends on ARCH_S3C2410
627 RTC (Realtime Clock) driver for the clock inbuilt into the
628 Samsung S3C24XX series of SoCs. This can provide periodic
629 interrupt rates from 1Hz to 64Hz for user programs, and
632 The driver currently supports the common features on all the
633 S3C24XX range, such as the S3C2410, S3C2412, S3C2413, S3C2440
636 This driver can also be build as a module. If so, the module
637 will be called rtc-s3c.
639 config RTC_DRV_EP93XX
640 tristate "Cirrus Logic EP93XX"
641 depends on ARCH_EP93XX
643 If you say yes here you get support for the
644 RTC embedded in the Cirrus Logic EP93XX processors.
646 This driver can also be built as a module. If so, the module
647 will be called rtc-ep93xx.
649 config RTC_DRV_SA1100
650 tristate "SA11x0/PXA2xx"
651 depends on ARCH_SA1100 || ARCH_PXA
653 If you say Y here you will get access to the real time clock
654 built into your SA11x0 or PXA2xx CPU.
656 To compile this driver as a module, choose M here: the
657 module will be called rtc-sa1100.
660 tristate "SuperH On-Chip RTC"
661 depends on RTC_CLASS && SUPERH && HAVE_CLK
663 Say Y here to enable support for the on-chip RTC found in
664 most SuperH processors.
666 To compile this driver as a module, choose M here: the
667 module will be called rtc-sh.
669 config RTC_DRV_VR41XX
670 tristate "NEC VR41XX"
671 depends on CPU_VR41XX
673 If you say Y here you will get access to the real time clock
674 built into your NEC VR41XX CPU.
676 To compile this driver as a module, choose M here: the
677 module will be called rtc-vr41xx.
680 tristate "ARM AMBA PL030 RTC"
683 If you say Y here you will get access to ARM AMBA
684 PrimeCell PL030 RTC found on certain ARM SOCs.
686 To compile this driver as a module, choose M here: the
687 module will be called rtc-pl030.
690 tristate "ARM AMBA PL031 RTC"
693 If you say Y here you will get access to ARM AMBA
694 PrimeCell PL031 RTC found on certain ARM SOCs.
696 To compile this driver as a module, choose M here: the
697 module will be called rtc-pl031.
699 config RTC_DRV_AT32AP700X
700 tristate "AT32AP700X series RTC"
701 depends on PLATFORM_AT32AP
703 Driver for the internal RTC (Realtime Clock) on Atmel AVR32
704 AT32AP700x family processors.
706 config RTC_DRV_AT91RM9200
707 tristate "AT91RM9200 or AT91SAM9RL"
708 depends on ARCH_AT91RM9200 || ARCH_AT91SAM9RL
710 Driver for the internal RTC (Realtime Clock) module found on
711 Atmel AT91RM9200's and AT91SAM9RL chips. On SAM9RL chips
712 this is powered by the backup power supply.
714 config RTC_DRV_AT91SAM9
715 tristate "AT91SAM9x/AT91CAP9"
716 depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
718 RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
719 (Real Time Timer). These timers are powered by the backup power
720 supply (such as a small coin cell battery), but do not need to
723 (On AT91SAM9rl chips you probably want to use the dedicated RTC
724 module and leave the RTT available for other uses.)
726 config RTC_DRV_AT91SAM9_RTT
730 prompt "RTT module Number" if ARCH_AT91SAM9263
731 depends on RTC_DRV_AT91SAM9
733 More than one RTT module is available. You can choose which
734 one will be used as an RTC. The default of zero is normally
735 OK to use, though some systems use that for non-RTC purposes.
737 config RTC_DRV_AT91SAM9_GPBR
739 range 0 3 if !ARCH_AT91SAM9263
740 range 0 15 if ARCH_AT91SAM9263
742 prompt "Backup Register Number"
743 depends on RTC_DRV_AT91SAM9
745 The RTC driver needs to use one of the General Purpose Backup
746 Registers (GPBRs) as well as the RTT. You can choose which one
747 will be used. The default of zero is normally OK to use, but
748 on some systems other software needs to use that register.
750 config RTC_DRV_AU1XXX
751 tristate "Au1xxx Counter0 RTC support"
752 depends on SOC_AU1X00
754 This is a driver for the Au1xxx on-chip Counter0 (Time-Of-Year
755 counter) to be used as a RTC.
757 This driver can also be built as a module. If so, the module
758 will be called rtc-au1xxx.
761 tristate "Blackfin On-Chip RTC"
762 depends on BLACKFIN && !BF561
764 If you say yes here you will get support for the
765 Blackfin On-Chip Real Time Clock.
767 This driver can also be built as a module. If so, the module
768 will be called rtc-bfin.
770 config RTC_DRV_RS5C313
771 tristate "Ricoh RS5C313"
772 depends on SH_LANDISK
774 If you say yes here you get support for the Ricoh RS5C313 RTC chips.
776 config RTC_DRV_GENERIC
777 tristate "Generic RTC support"
778 # Please consider writing a new RTC driver instead of using the generic
780 depends on PARISC || M68K || PPC || SUPERH32
782 Say Y or M here to enable RTC support on systems using the generic
783 RTC abstraction. If you do not know what you are doing, you should
787 tristate "PXA27x/PXA3xx"
790 If you say Y here you will get access to the real time clock
791 built into your PXA27x or PXA3xx CPU.
793 This RTC driver uses PXA RTC registers available since pxa27x
794 series (RDxR, RYxR) instead of legacy RCNR, RTAR.
798 bool "SUN4V Hypervisor RTC"
801 If you say Y here you will get support for the Hypervisor
802 based RTC on SUN4V systems.
804 config RTC_DRV_STARFIRE
808 If you say Y here you will get support for the RTC found on
811 config RTC_DRV_TX4939
812 tristate "TX4939 SoC"
813 depends on SOC_TX4939
815 Driver for the internal RTC (Realtime Clock) module found on
819 tristate "Marvell SoC RTC"
820 depends on ARCH_KIRKWOOD
822 If you say yes here you will get support for the in-chip RTC
823 that can be found in some of Marvell's SoC devices, such as
824 the Kirkwood 88F6281 and 88F6192.
826 This driver can also be built as a module. If so, the module
827 will be called rtc-mv.
833 If you say yes here you will get support for the RTC on PS3.
835 This driver can also be built as a module. If so, the module
836 will be called rtc-ps3.
838 config RTC_DRV_COH901331
839 tristate "ST-Ericsson COH 901 331 RTC"
842 If you say Y here you will get access to ST-Ericsson
843 COH 901 331 RTC clock found in some ST-Ericsson Mobile
846 This driver can also be built as a module. If so, the module
847 will be called "rtc-coh901331".
851 tristate "Freescale STMP3xxx RTC"
852 depends on ARCH_STMP3XXX
854 If you say yes here you will get support for the onboard
857 This driver can also be built as a module. If so, the module
858 will be called rtc-stmp3xxx.
864 If you say Y here you will get support for the RTC found on
865 the PCAP2 ASIC used on some Motorola phones.