Home
last modified time | relevance | path

Searched refs:RTC (Results 1 – 125 of 125) sorted by relevance

/linux-4.1.27/drivers/rtc/
DKconfig2 # RTC class/drivers configuration
14 Generic RTC class support. If you say yes here, you will
21 bool "Set system time from RTC on startup and resume"
25 the value read from a specified RTC device. This is useful to avoid
29 bool "Set the RTC time based on NTP synchronization"
33 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
37 string "RTC used to set the system time"
41 The RTC device that will be used to (re)initialize the system
47 The driver for this RTC device must be loaded before late_initcall
56 sleep states. Do not specify an RTC here unless it stays powered
[all …]
Drtc-cmos.c694 #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes. in cmos_do_probe()
/linux-4.1.27/Documentation/
Drtc.txt2 Real Time Clock (RTC) Drivers for Linux
16 Linux has two largely-compatible userspace RTC API families you may
19 * /dev/rtc ... is the RTC provided by PC compatible systems,
23 supported by a wide variety of RTC chips on all systems.
27 RTCs use the same API to make requests in both RTC frameworks (using
29 same functionality. For example, not every RTC is hooked up to an
91 the process of doing this, the kernel briefly turns off RTC periodic
94 whatever) then the kernel will keep its hands off the RTC, allowing you
97 The alarm and/or interrupt frequency are programmed into the RTC via
108 New portable "RTC Class" drivers: /dev/rtcN
[all …]
Dkernel-parameters.txt3563 wakeup-capable RTC alarm.
/linux-4.1.27/arch/sh/kernel/cpu/sh4/
Dsetup-sh4-202.c92 HUDI, TMU0, TMU1, TMU2, RTC, SCIF, WDT, enumerator
99 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
100 INTC_VECT(RTC, 0x4c0),
107 { 0xffd00004, 0, 16, 4, /* IPRA */ { TMU0, TMU1, TMU2, RTC } },
Dsetup-sh7750.c192 TMU3, TMU4, TMU0, TMU1, TMU2, RTC, SCI1, SCIF, WDT, REF, enumerator
202 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
203 INTC_VECT(RTC, 0x4c0),
213 { 0xffd00004, 0, 16, 4, /* IPRA */ { TMU0, TMU1, TMU2, RTC } },
/linux-4.1.27/Documentation/devicetree/bindings/rtc/
Dmoxa,moxart-rtc.txt6 - gpio-rtc-sclk : RTC sclk gpio, with zero flags
7 - gpio-rtc-data : RTC data gpio, with zero flags
8 - gpio-rtc-reset : RTC reset gpio, with zero flags
Drtc-palmas.txt1 Palmas RTC controller bindings
5 - "ti,palmas-rtc" for palma series of the RTC controller
7 - interrupts: Interrupt number of RTC submodule on device.
12 TPS80036 supports the backup battery for powering the RTC when main
Darmada-380-rtc.txt3 RTC controller for the Armada 38x SoCs
10 * "rtc" for the RTC registers
13 - interrupts: IRQ line for the RTC.
Drtc-omap.txt5 - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family.
6 - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family.
7 This RTC IP has special WAKE-EN Register to enable
Dtwl-rtc.txt1 * TI twl RTC
3 The TWL family (twl4030/6030) contains a RTC.
Dpxa-rtc.txt1 * PXA RTC
3 PXA specific RTC driver.
Dorion-rtc.txt3 RTC controller for the Kirkwood, the Dove, the Armada 370 and the
10 - interrupts: IRQ line for the RTC.
Dsunxi-rtc.txt3 RTC controller for the Allwinner A10/A20
9 - interrupts: IRQ line for the RTC.
Dsun6i-rtc.txt3 RTC controller for the Allwinner A31
9 - interrupts : IRQ lines for the RTC alarm 0 and alarm 1, in that order.
Dxgene-rtc.txt3 RTC controller for the APM X-Gene Real Time Clock
9 - interrupts: IRQ line for the RTC.
Disil,isl12057.txt1 Intersil ISL12057 I2C RTC/Alarm chip
13 RTC alarm rings. In order to mark the device has a wakeup source and
30 of the SoC connected to IRQ#2 of the RTC chip.
Dolpc-xo1-rtc.txt1 OLPC XO-1 RTC
Dmaxim,ds1742.txt5 - reg: Physical base address of the RTC and length of memory
Dlpc32xx-rtc.txt7 - interrupts: The RTC interrupt
Dspear-rtc.txt1 * SPEAr RTC
Drtc-cmos.txt1 Motorola mc146818 compatible RTC
Dnvidia,tegra20-rtc.txt3 The Tegra RTC maintains seconds and milliseconds counters, and five alarm
Datmel,at91sam9-rtc.txt9 the time base when the RTT is used as an RTC.
Dabracon,abx80x.txt1 Abracon ABX80X I2C ultra low power RTC/Alarm chip
/linux-4.1.27/arch/sh/kernel/cpu/sh3/
Dsetup-sh7710.c30 RTC, WDT, REF, enumerator
53 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
54 INTC_VECT(RTC, 0x4c0),
60 { 0xfffffee2, 0, 16, 4, /* IPRA */ { TMU0, TMU1, TMU2, RTC } },
Dsetup-sh7705.c33 RTC, WDT, REF_RCMI, enumerator
51 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
52 INTC_VECT(RTC, 0x4c0),
58 { 0xfffffee2, 0, 16, 4, /* IPRA */ { TMU0, TMU1, TMU2, RTC } },
Dsetup-sh770x.c34 RTC, WDT, REF, enumerator
40 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
41 INTC_VECT(RTC, 0x4c0),
70 { 0xfffffee2, 0, 16, 4, /* IPRA */ { TMU0, TMU1, TMU2, RTC } },
Dsetup-sh7720.c229 TMU0, TMU1, TMU2, RTC, enumerator
245 INTC_VECT(TMU2, 0x440), INTC_VECT(RTC, 0x480),
246 INTC_VECT(RTC, 0x4a0), INTC_VECT(RTC, 0x4c0),
273 { 0xA414FEE2UL, 0, 16, 4, /* IPRA */ { TMU0, TMU1, TMU2, RTC } },
/linux-4.1.27/arch/sh/boards/mach-highlander/
Dirq-r7780mp.c26 RTC, /* RTC Alarm */ enumerator
40 INTC_IRQ(RTC, IRQ_RTC),
51 { SCIF0, SCIF1, RTC, 0, CF, 0, TP, SMBUS,
Dirq-r7785rp.c24 RTC, /* RTC Alarm */ enumerator
36 INTC_IRQ(RTC, IRQ_RTC),
51 RTC, 0, TH_ALERT, 0, 0, 0, 0, 0 } },
/linux-4.1.27/arch/arm/boot/dts/
Dkirkwood-nas2big.dts43 /* The on-chip RTC is not powered (no supercap). */
104 * An external I2C RTC (Dallas DS1337S+) is used. This allows
105 * to power-up the board on an RTC alarm. The external RTC can
Dam335x-bone-common.dtsi227 * Configure pmic to enter OFF-state instead of SLEEP-state ("RTC-only
228 * mode") at poweroff. Most BeagleBone versions do not support RTC-only
239 * if you want to use RTC-only mode and made sure you are not affected
Dimx28-eukrea-mbmx287lc.dts16 * Module contains : i.MX287 + 128MB DDR2 + NAND + 2 x Ethernet PHY + RTC
Dimx28-eukrea-mbmx283lc.dts16 * Module contains : i.MX282 + 64MB DDR2 + NAND + Ethernet PHY + RTC
Darmada-370-synology-ds213j.dts84 /* RTC provided by Seiko S-35390A I2C RTC chip below */
152 /* Main device RTC chip */
Dtegra30-colibri-eval-v3.dts49 * GEN1_I2C: I2C_SDA/SCL on SODIMM pin 194/196 (e.g. RTC on carrier
Dtegra30-apalis-eval.dts72 * GEN1_I2C: I2C1_SDA/SCL on MXM3 pin 209/211 (e.g. RTC on carrier
Dkirkwood-dir665.dts274 /* There is no battery on the boards, so the RTC does not keep time
Darmada-xp-openblocks-ax3-4.dts109 /* No crystal connected to the internal RTC */
Darmada-xp-linksys-mamba.dts99 /* No crystal connected to the internal RTC */
Darmada-xp-synology-ds414.dts106 /* RTC is provided by Seiko S-35390A below */
/linux-4.1.27/arch/avr32/boards/atngw100/
DKconfig_mrmt62 bool "Use External RTC on I2C Bus"
64 RMT1 has an optional RTC device on the I2C bus.
66 matching RTC driver.
/linux-4.1.27/sound/core/
DKconfig125 tristate "RTC Timer support"
126 depends on RTC
129 Say Y here to enable RTC timer support for ALSA. ALSA uses
130 the RTC timer as a precise timing source and maps the RTC
137 Note that this option is exclusive with the new RTC drivers
141 bool "Use RTC as default sequencer timer"
146 Say Y here to use the RTC timer as the default sequencer
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Dtrivial-devices.txt42 dallas,ds1338 I2C RTC with 56-Byte NV RAM
43 dallas,ds1340 I2C RTC with Trickle Charger
44 dallas,ds1374 I2C, 32-Bit Binary Counter Watchdog RTC with Trickle Charger and Reset Input/Output
48 dallas,ds3232 Extremely Accurate I²C RTC with Integrated Crystal and SRAM
64 isil,isl12057 Intersil ISL12057 I2C RTC Chip
96 stm,m41t62 Serial real-time clock (RTC) with alarm
97 stm,m41t80 M41T80 - SERIAL ACCESS RTC WITH ALARMS
/linux-4.1.27/arch/sh/kernel/cpu/sh2a/
Dsetup-sh7203.c39 ROMDEC, FLCTL, SDHI, RTC, RCAN0, RCAN1, enumerator
109 INTC_IRQ(RTC, 231), INTC_IRQ(RTC, 232),
110 INTC_IRQ(RTC, 233),
157 { 0xfffe0c14, 0, 16, 4, /* IPR16 */ { FLCTL, 0, RTC, RCAN0 } },
162 { 0xfffe0c14, 0, 16, 4, /* IPR16 */ { FLCTL, SDHI, RTC, RCAN0 } },
Dsetup-sh7201.c30 RTC, WDT, enumerator
90 INTC_IRQ(RTC, 152), INTC_IRQ(RTC, 153),
91 INTC_IRQ(RTC, 154),
161 { 0xfffe9806, 0, 16, 4, /* IPR09 */ { RTC, WDT, IIC30, 0 } },
Dsetup-sh7264.c44 NFMC, SDHI, RTC, enumerator
165 INTC_IRQ(RTC, 296), INTC_IRQ(RTC, 297),
166 INTC_IRQ(RTC, 298),
215 { 0xfffe0c1e, 0, 16, 4, /* IPR21 */ { NFMC, SDHI, RTC, 0 } },
Dsetup-sh7269.c48 RTC, enumerator
182 INTC_IRQ(RTC, 338), INTC_IRQ(RTC, 339),
183 INTC_IRQ(RTC, 340),
237 { 0xfffe0c26, 0, 16, 4, /* IPR25 */ { SDHI0, SDHI1, RTC, 0 } },
/linux-4.1.27/arch/sh/kernel/cpu/sh4a/
Dsetup-sh7780.c308 RTC, WDT, TMU0, TMU1, TMU2, TMU2_TICPI, enumerator
319 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
320 INTC_VECT(RTC, 0x4c0),
364 HUDI, 0, WDT, SCIF1, SCIF0, RTC, TMU345, TMU012 } },
370 { 0xffd40004, 0, 32, 8, /* INT2PRI1 */ { TMU3, TMU4, TMU5, RTC } },
Dsetup-sh7763.c245 RTC, WDT, TMU0, TMU1, TMU2, TMU2_TICPI, enumerator
259 INTC_VECT(RTC, 0x480), INTC_VECT(RTC, 0x4a0),
260 INTC_VECT(RTC, 0x4c0),
311 HUDI, 0, WDT, SCIF1, SCIF0, RTC, TMU345, TMU012 } },
322 { 0xffd40004, 0, 32, 8, /* INT2PRI1 */ { TMU3, TMU4, TMU5, RTC } },
Dsetup-sh7734.c332 RTC, enumerator
421 INTC_VECT(RTC, 0xC00),
500 RTC,
511 { TMU30, TMU60, RTC, SDHI } },
Dsetup-sh7723.c484 SDHI1, RTC, DMAC1B, SDHI0, enumerator
585 INTC_GROUP(RTC, RTC_ATI,RTC_PRI,RTC_CUI),
634 { 0xa4080028, 0, 16, 4, /* IPRK */ { RTC,DMAC1B,0,SDHI0 } },
Dsetup-sh7722.c549 SIM, RTC, DMAC0123, VIOVOU, USB, DMAC45, FLCTL, I2C, SDHI, enumerator
587 INTC_GROUP(RTC, RTC_ATI, RTC_PRI, RTC_CUI),
636 { 0xa4080020, 0, 16, 4, /* IPRI */ { SIO, 0, TSIF, RTC } },
Dsetup-sh7724.c910 DMAC1A, _2DG, DMAC0A, VIO, USB, RTC, enumerator
1023 INTC_GROUP(RTC, RTC_ATI, RTC_PRI, RTC_CUI),
1088 { 0xa4080028, 0, 16, 4, /* IPRK */ { RTC, DMAC1B, 0, SDHI0 } },
/linux-4.1.27/Documentation/ia64/
Defirtc.txt28 used today with the legacy RTC driver (driver/char/rtc.c). However, because
47 To allow for a uniform interface between the legacy RTC and EFI time service,
49 "public" API of the two drivers. The specifics of the legacy RTC are still
56 Two ioctl()s, compatible with the legacy RTC calls:
95 RTC which is some kind of interval timer alarm. For this reason we don't use
97 introduced 2 news ioctl()s to the interface of an RTC.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dqcom-pm8xxx.txt69 Definition: single entry specifying the base address of the RTC registers
74 Definition: single entry specifying the RTC's alarm interrupt
79 Definition: indicates that the setting of RTC time is allowed by
Dmax77686.txt3 MAX77686 is a Mulitifunction device with PMIC, RTC and Charger on chip. It is
5 are addressed using same i2c slave address whereas RTC submodule uses
Dmax8925.txt21 max8925-rtc : : RTC
Dmt6397.txt5 - RTC
D88pm860x.txt22 88pm860x-rtc : : RTC
Dda9055.txt10 da9055-rtc : : RTC
Das3711.txt2 supplies, a battery charger and an RTC. So far only bindings for the two stepup
Ds2mpa01.txt6 and an RTC. It is interfaced to the host controller using an I2C interface.
Ds2mps11.txt5 current regulators, RTC, charger controller and other sub-blocks. It is
Dmc13xxx.txt9 - fsl,mc13xxx-uses-rtc : Indicate the RTC is being used
Das3722.txt8 interrupt request from internal sub-blocks like RTC, regulators, GPIOs as well
/linux-4.1.27/Documentation/arm/
DNetwinder16 0x0070 - 0x007f RTC
57 8 ISA RTC alarm
/linux-4.1.27/Documentation/timers/
Dhpet.txt20 and from the RTC.
29 RTC driver framework. An example user space program is provided in
Dtimekeeping.txt47 the user-visible time to RTC clocks in the system or against networked time
/linux-4.1.27/arch/mips/lasat/
DKconfig10 bool "DS1603 RTC driver"
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt73 RTC
76 The RTC hardware is similar to the S3C2410, and is supported by the
DOverview.txt161 RTC
164 Support for the onboard RTC unit, including alarm function.
166 This has recently been upgraded to use the new RTC core,
/linux-4.1.27/Documentation/power/
Ds2ram.txt67 pm_trace uses the system's Real Time Clock (RTC) to save the magic number.
68 Reason for this is that the RTC is the only reliably available piece of
84 or the low order bits of the minutes of the RTC, but a too long delay will
Dinterface.txt63 the RTC across reboots, so that you can debug a machine that just hangs
64 during suspend (or more commonly, during resume). Namely, the RTC is only
/linux-4.1.27/drivers/char/
DKconfig255 memory in the real time clock (RTC), which is contained in every PC
257 nvram in the system, but is usually 114 (128-14 for the RTC).
275 # These legacy RTC drivers just cause too many conflicts with the generic
276 # RTC framework ... let's not even try to coexist any more.
280 config RTC config
281 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
298 and set the RTC in an SMP compatible fashion.
331 …depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR…
340 "extended RTC operation" below it will also provide an emulation
348 bool "Extended RTC operation"
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/timer/
Dmediatek,mtk-timer.txt8 clocks. The order is system clock and as second clock the RTC clock.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-iio-trigger-sysfs10 are not applicable. For example no RTC or spare GPIOs.
Dsysfs-class-rtc-rtc0-device-rtc_calibration7 Every 60 seconds the AB8500 will correct the RTC's value
Dsysfs-power102 last PM event point in the RTC across reboots, so that you can
104 commonly, during resume). Namely, the RTC is only used to save
128 device associated with the last PM event point saved in the RTC
132 the device hash in the RTC at boot, with a newline after each
139 Due to the small hash size necessary to fit in the RTC, it is
142 device is causing the problem. Note that genuine RTC clock
/linux-4.1.27/drivers/cpuidle/
Dcpuidle-ux500.c115 prcmu_enable_wakeups(PRCMU_WAKEUP(ARM) | PRCMU_WAKEUP(RTC) | in dbx500_cpuidle_probe()
/linux-4.1.27/Documentation/devicetree/bindings/metag/
Dpdc-intc.txt74 <30 4 /* level */>, /* Peripheral 0 (RTC) */
89 interrupts = <0 /* Peripheral 0 (RTC) */
/linux-4.1.27/drivers/staging/iio/trigger/
DKconfig9 tristate "Periodic RTC triggers"
/linux-4.1.27/arch/arm/mach-mmp/
Dclock-pxa910.c43 static APBC_CLK(rtc, RTC, 8, 32768);
Dclock-pxa168.c56 static APBC_CLK(rtc, RTC, 8, 32768);
/linux-4.1.27/Documentation/virtual/kvm/
Dtimekeeping.txt180 2.2) RTC
186 The RTC is accessed through CMOS variables, which uses an index register to
188 of the CMOS and read of the RTC require lock protection (in addition, it is
189 dangerous to allow userspace utilities such as hwclock to have direct RTC
192 The RTC generates an interrupt which is usually routed to IRQ 8. The interrupt
195 The type of interrupt is signalled in the RTC status registers.
197 The RTC will update the current time fields by battery power even while the
202 programmed to a 32kHz divider if the RTC is to count seconds.
204 This is the RAM map originally used for the RTC/CMOS:
253 bit 7 = RTC has power
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/
Dcirrus,clps711x-intc.txt22 10: RTCMI RTC compare match
/linux-4.1.27/arch/powerpc/boot/dts/
Dep405.dts165 /* NVRAM and RTC */
179 01 /* RTC */
Dwalnut.dts180 /* NVRAM and RTC */
Debony.dts164 /* NVRAM & RTC */
/linux-4.1.27/arch/metag/boot/dts/
Dtz1090.dtsi42 <30 IRQ_TYPE_LEVEL_HIGH>, /* Perip 0 (RTC) */
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dste-u300-syscon-clock.txt24 0 6 RTC clock
Dexynos5433-clock.txt19 which generates clocks for PMU/TMU/MCT/WDT/RTC/SECKEY/TZPC IPs.
/linux-4.1.27/arch/blackfin/mach-bf533/
DKconfig33 int "RTC ERROR"
/linux-4.1.27/kernel/power/
DKconfig167 make it wake up a few seconds later using an RTC wakeup alarm.
170 You probably want to have your system's RTC driver statically
198 example does by saving things in the RTC, see below.
215 RTC across reboots, so that you can debug a machine that just hangs
/linux-4.1.27/drivers/mfd/
DKconfig39 controllers, 11 LDOs, RTC, automatic battery, temperature and
254 functions, such as regulators, RTC, codec, Coulomb counter, etc.
402 select individual components like voltage regulators, RTC and
425 select individual components like voltage regulators, RTC and
452 MAX77802 which are Power Management IC with an RTC on chip.
514 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
723 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
738 including interrupts, RTC, LDO & DCDC regulators, and onkey.
839 of the AB3100 such as battery-backed RTC, charging control,
975 inputs from buttons and the IR remote, LEDs, an RTC, and more.
[all …]
Dlp8788.c114 MFD_DEV_WITH_RESOURCE(RTC, rtc_irqs, ARRAY_SIZE(rtc_irqs)),
Ddb8500-prcmu.c307 IRQ_ENTRY(RTC),
335 WAKEUP_ENTRY(RTC),
/linux-4.1.27/arch/ia64/include/asm/sn/
Dshub_mmr.h473 #define SH_RTC shubmmr(SH, RTC)
/linux-4.1.27/drivers/staging/iio/
DTODO63 subsystem. Current approach is abusing purpose of RTC.
/linux-4.1.27/Documentation/devicetree/bindings/crypto/
Dfsl-sec4.txt12 -Secure Non-Volatile Storage (SNVS) Low Power (LP) RTC Node
352 Secure Non-Volatile Storage (SNVS) Low Power (LP) RTC Node
354 A SNVS child node that defines SNVS LP RTC.
/linux-4.1.27/arch/mn10300/
DKconfig234 bool "Using MN10300 RTC"
239 This option enables support for the RTC, thus enabling time to be
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt128 <3> - RTC clock input.
/linux-4.1.27/arch/m68k/q40/
DREADME30 genrtc.c # RTC
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig174 Complie in platform device definition for RTC
/linux-4.1.27/arch/arm/mach-versatile/
Dcore.c654 APB_DEVICE(rtc, "dev:e8", RTC, NULL);
/linux-4.1.27/arch/alpha/
DKconfig184 MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized
386 SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size.
/linux-4.1.27/arch/powerpc/platforms/
DKconfig333 platform devices for direct mapped RTC chips like the DS1742 or DS1743.
/linux-4.1.27/drivers/macintosh/
DKconfig86 RAM and the RTC (real time clock) chip. Say Y to enable support for
/linux-4.1.27/drivers/media/dvb-frontends/
Dstv0900_sw.c486 stv0900_write_reg(intp, RTC, 0x80); in stv0900_check_timing_lock()
506 stv0900_write_reg(intp, RTC, 0x88); in stv0900_check_timing_lock()
Dstv090x.c1535 if (STV090x_WRITE_DEMOD(state, RTC, 0x88) < 0) in stv090x_start_search()
2094 if (STV090x_WRITE_DEMOD(state, RTC, 0x80) < 0) in stv090x_chk_tmg()
2124 if (STV090x_WRITE_DEMOD(state, RTC, 0x88) < 0) /* DVB-S1 timing */ in stv090x_chk_tmg()
Dstv0900_reg.h2519 #define RTC REGx(R0900_P1_RTC) macro
Dstv0900_core.c1048 stv0900_write_reg(intp, RTC, 0x88); in stv0900_start_search()
/linux-4.1.27/drivers/zorro/
Dzorro.ids345 2000 A1200 T68030 RTC [Accelerator]
/linux-4.1.27/arch/blackfin/mach-bf548/include/mach/
DdefBF54x_base.h1523 #define RTC 0x80 /* Real-Time Clock */ macro
/linux-4.1.27/arch/cris/arch-v32/drivers/
DKconfig156 This option enables the I2C driver used by e.g. the RTC driver.
/linux-4.1.27/arch/blackfin/
DKconfig1268 such as GPIO interrupt or RTC activity wakes up the processor.
1281 this mode. Typically an external event or RTC activity will wake
/linux-4.1.27/arch/sh/
DKconfig576 platforms lacking an RTC.
/linux-4.1.27/Documentation/arm64/
Dacpi_object_usage.txt566 -- Section 9.15: PC/AT RTC/CMOS devices
/linux-4.1.27/arch/x86/
DKconfig732 time in preference to the PIT and RTC, if a HPET is
748 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
/linux-4.1.27/drivers/net/ethernet/amd/xgbe/
Dxgbe-dev.c272 XGMAC_MTL_IOWRITE_BITS(pdata, i, MTL_Q_RQOMR, RTC, val); in xgbe_config_rx_threshold()
/linux-4.1.27/drivers/watchdog/
DKconfig385 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
/linux-4.1.27/
DCREDITS1294 D: Author of RTC driver & several net drivers, Ethernet & BootPrompt Howto.
4062 D: RTC subsystem
DMAINTAINERS2008 BLACKFIN RTC DRIVER
7995 PXA RTC DRIVER
8235 REAL TIME CLOCK (RTC) SUBSYSTEM
/linux-4.1.27/arch/mips/
DKconfig1980 Set this to non-zero if building a guest kernel for KVM to skip RTC