Home
last modified time | relevance | path

Searched full:timers (Results 1 – 25 of 653) sorted by relevance

12345678910>>...27

/linux/arch/powerpc/sysdev/
H A Dfsl_gtm.c3 * Freescale General-purpose Timers Module
72 struct gtm_timer timers[4]; member
95 for (i = 0; i < ARRAY_SIZE(gtm->timers); i++) { in gtm_get_timer16()
96 if (!gtm->timers[i].requested) { in gtm_get_timer16()
97 gtm->timers[i].requested = true; in gtm_get_timer16()
99 return &gtm->timers[i]; in gtm_get_timer16()
132 if (gtm->timers[timer].requested) in gtm_get_specific_timer16()
135 ret = &gtm->timers[timer]; in gtm_get_specific_timer16()
169 int num = tmr - &gtm->timers[0]; in gtm_set_ref_timer16()
206 * Properly reset timers: stop, reset, set up prescalers, reference in gtm_set_ref_timer16()
[all …]
/linux/Documentation/timers/
H A Dhrtimers.rst2 hrtimers - subsystem for high-resolution kernel timers
5 This patch introduces a new subsystem for high-resolution kernel timers.
8 (kernel/timers.c), why do we need two timer subsystems? After a lot of
18 - the forced handling of low-resolution and high-resolution timers in
20 mess. The timers.c code is very "tightly coded" around jiffies and
27 high-res timers.
30 necessitate a more complex handling of high resolution timers, which
34 degrading other portions of the timers.c code in an unacceptable way.
38 the required readjusting of absolute CLOCK_REALTIME timers at
41 timers.
[all …]
H A Dhighres.rst2 High resolution timers and dynamic ticks design notes
34 the base implementation are covered in Documentation/timers/hrtimers.rst. See
38 timers are:
64 Timers" was written by J. Stultz, D.V. Hart, & N. Aravamudan.
82 functionality like high resolution timers or dynamic ticks.
102 accounting, profiling, and high resolution timers.
134 enabling of high resolution timers and dynamic ticks is simply provided by
156 configured for high resolution timers can run on a system which lacks the
167 The time ordered insertion of timers provides all the infrastructure to decide
175 from the clock event distribution code and moves expired timers from the
[all …]
H A Dhpet.rst12 also called "timers", which can be misleading since usually timers are
19 mode where the first two comparators block interrupts from 8254 timers
30 file:samples/timers/hpet_example.c
/linux/fs/bcachefs/
H A Dclock.c32 for (size_t i = 0; i < clock->timers.nr; i++) in bch2_io_timer_add()
33 if (clock->timers.data[i] == timer) in bch2_io_timer_add()
36 BUG_ON(!min_heap_push(&clock->timers, &timer, &callbacks, NULL)); in bch2_io_timer_add()
45 for (size_t i = 0; i < clock->timers.nr; i++) in bch2_io_timer_del()
46 if (clock->timers.data[i] == timer) { in bch2_io_timer_del()
47 min_heap_del(&clock->timers, i, &callbacks, NULL); in bch2_io_timer_del()
133 if (clock->timers.nr && in get_expired_timer()
134 time_after_eq64(now, clock->timers.data[0]->expire)) { in get_expired_timer()
135 ret = *min_heap_peek(&clock->timers); in get_expired_timer()
136 min_heap_pop(&clock->timers, &callbacks, NULL); in get_expired_timer()
[all …]
/linux/drivers/clocksource/
H A Dbcm_kona_timer.c32 static struct kona_bcm_timers timers; variable
37 * We use the peripheral timers for system tick, the cpu global timer for
100 * timer-interrupt->set_next_event. CPU local timers, when in kona_timer_set_next_event()
108 ret = kona_timer_get_counter(timers.tmr_regs, &msw, &lsw); in kona_timer_set_next_event()
113 writel(lsw + clc, timers.tmr_regs + KONA_GPTIMER_STCM0_OFFSET); in kona_timer_set_next_event()
116 reg = readl(timers.tmr_regs + KONA_GPTIMER_STCS_OFFSET); in kona_timer_set_next_event()
118 writel(reg, timers.tmr_regs + KONA_GPTIMER_STCS_OFFSET); in kona_timer_set_next_event()
125 kona_timer_disable_and_clear(timers.tmr_regs); in kona_timer_shutdown()
148 kona_timer_disable_and_clear(timers.tmr_regs); in kona_timer_interrupt()
171 timers.tmr_irq = irq_of_parse_and_map(node, 0); in kona_timer_init()
[all …]
H A Dtimer-probe.c21 unsigned timers = 0; in timer_probe() local
38 timers++; in timer_probe()
41 timers += acpi_probe_device_table(timer); in timer_probe()
43 if (!timers) in timer_probe()
44 pr_crit("%s: no matching timers found\n", __func__); in timer_probe()
H A Dingenic-timer.c46 struct ingenic_tcu_timer timers[]; member
69 return container_of(timer, struct ingenic_tcu, timers[timer->cpu]); in to_ingenic_tcu()
143 struct ingenic_tcu_timer *timer = &tcu->timers[cpu]; in ingenic_tcu_setup_cevt()
289 tcu = kzalloc(struct_size(tcu, timers, num_possible_cpus()), in ingenic_tcu_init()
317 timer = &tcu->timers[cpu]; in ingenic_tcu_init()
340 pr_crit("%s: Unable to start CPU timers: %d\n", __func__, ret); in ingenic_tcu_init()
380 clk_disable(tcu->timers[cpu].clk); in ingenic_tcu_suspend()
392 ret = clk_enable(tcu->timers[cpu].clk); in ingenic_tcu_resume()
405 clk_disable(tcu->timers[cpu - 1].clk); in ingenic_tcu_resume()
/linux/Documentation/sound/
H A Dutimers.rst4 Userspace-driven timers
12 This document describes the userspace-driven timers: virtual ALSA timers
14 IOCTL calls. Such timers could be useful when synchronizing audio
15 stream with timer sources which we don't have ALSA timers exported for
21 Enabling userspace-driven timers
24 The userspace-driven timers could be enabled in the kernel using the
28 Userspace-driven timers API
51 applications. There could be up to 128 userspace-driven timers in the
96 Userspace-driven timers and snd-aloop
99 Userspace-driven timers could be easily used with ``snd-aloop`` module
[all …]
/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,omap-remoteproc.yaml37 'timers', 'watchdog-timers' etc.
142 ti,timers:
148 as System/Tick timers for the OS running on the remote
152 to reserve specific timers to be dedicated to the
157 features. The timers to be used should match with the
158 timers used in the firmware image.
160 ti,watchdog-timers:
166 serve as Watchdog timers for the processor cores. This
170 The timers to be used should match with the watchdog
171 timers used in the firmware image.
[all …]
/linux/arch/arm/boot/dts/st/
H A Dstm32f746.dtsi78 timers2: timers@40000000 {
81 compatible = "st,stm32-timers";
100 timers3: timers@40000400 {
103 compatible = "st,stm32-timers";
122 timers4: timers@40000800 {
125 compatible = "st,stm32-timers";
144 timers5: timers@40000c00 {
147 compatible = "st,stm32-timers";
166 timers6: timers@40001000 {
169 compatible = "st,stm32-timers";
[all …]
H A Dstm32f429.dtsi96 timers2: timers@40000000 {
99 compatible = "st,stm32-timers";
118 timers3: timers@40000400 {
121 compatible = "st,stm32-timers";
140 timers4: timers@40000800 {
143 compatible = "st,stm32-timers";
162 timers5: timers@40000c00 {
165 compatible = "st,stm32-timers";
184 timers6: timers@40001000 {
187 compatible = "st,stm32-timers";
[all …]
/linux/Documentation/devicetree/bindings/mips/brcm/
H A Dsoc.txt145 == Timers
148 timers that can be used.
153 "brcm,bcm7425-timers"
154 "brcm,bcm7429-timers"
155 "brcm,bcm7435-timers" and
156 "brcm,brcmstb-timers"
157 - reg : the timers register range
162 timers: timer@4067c0 {
163 compatible = "brcm,bcm7425-timers", "brcm,brcmstb-timers";
/linux/drivers/misc/
H A Dcs5535-mfgpt.c3 * Driver for the CS5535/CS5536 Multi-Function General Purpose Timers (MFGPT)
24 MODULE_PARM_DESC(mfgptfix, "Try to reset the MFGPT timers during init; "
27 "2 = perform a soft reset by unconfiguring all timers); "
62 * XXX: According to the docs, we cannot reset timers above in cs5535_mfgpt_toggle_event()
155 /* only allocate timers from the working domain if requested */ in cs5535_mfgpt_alloc_timer()
173 /* set timer_nr to -1 if no timers available */ in cs5535_mfgpt_alloc_timer()
242 * This is a sledgehammer that resets all MFGPT timers. This is required by
245 * whether or not this secret MSR can be used to release individual timers.
253 /* The following undocumented bit resets the MFGPT timers */ in reset_all_timers()
259 * This is another sledgehammer to reset all MFGPT timers.
[all …]
/linux/arch/arm/boot/dts/ti/omap/
H A Ddra7-ipu-dsp-common.dtsi25 ti,timers = <&timer3>;
26 ti,watchdog-timers = <&timer4>, <&timer9>;
31 ti,timers = <&timer11>;
32 ti,watchdog-timers = <&timer7>, <&timer8>;
37 ti,timers = <&timer5>;
38 ti,watchdog-timers = <&timer10>;
/linux/Documentation/devicetree/bindings/pwm/
H A Dpwm-samsung.yaml7 title: Samsung SoC PWM timers
15 and clock event timers, as well as to drive SoC outputs with PWM signal. Each
49 - "timers" - PWM base clock used to generate PWM signals,
58 - const: timers
60 - const: timers
63 - const: timers
66 - const: timers
126 clock-names = "timers";
H A Dsnps,dw-apb-timers-pwm2.yaml5 $id: http://devicetree.org/schemas/pwm/snps,dw-apb-timers-pwm2.yaml#
8 title: Synopsys DW-APB timers PWM controller
14 This describes the DesignWare APB timers module when used in the PWM
28 const: snps,dw-apb-timers-pwm2
62 compatible = "snps,dw-apb-timers-pwm2";
H A Dti,omap-dmtimer-pwm.yaml25 ti,timers:
49 - ti,timers
57 ti,timers = <&timer9>;
/linux/kernel/time/
H A Dposix-cpu-timers.c8 #include <linux/posix-timers.h>
20 #include "posix-timers.h"
289 * CPU timers armed. Before starting a timer it's required to check whether
534 * Clean out CPU timers which are still armed when a thread exits. The
535 * timers are only removed from the list. No other updates are done. The
536 * corresponding posix timers are still accessible, but cannot be rearmed.
562 * Insert the timer on the appropriate list before any timers that
578 * for process timers we share expiration cache with itimers in arm_timer()
579 * and RLIMIT_CPU and for thread timers with RLIMIT_RTTIME. in arm_timer()
608 /* Disable oneshot timers */ in cpu_timer_fire()
[all …]
H A Dposix-timers.c3 * 2002-10-15 Posix Clocks & timers
10 * These are all the functions necessary to implement POSIX clocks & timers
21 #include <linux/posix-timers.h>
31 #include "posix-timers.h"
36 * Timers are managed in a hash table for lockless lookup. The hash key is
341 * whether the signal should be dropped and rearms interval timers. The
381 * based timers.
493 /* Special case for CRIU to restore timers with a given timer ID. */ in do_timer_create()
624 * The hash lookup and the timers are RCU protected. in __lock_timer()
626 * Timers are added to the hash in invalid state where in __lock_timer()
[all …]
H A Dtimer.c3 * Kernel internal timers
7 * 1997-01-28 Modified by Finn Arne Gangstad to make timers scale better.
33 #include <linux/posix-timers.h>
77 * expiry of the timers, this implementation removes the need for recascading
78 * the timers into the lower array levels. The previous 'classic' timer wheel
85 * timeout timers (networking, disk I/O ...) are canceled before expiry. If
89 * The only exception to this are networking timers with a small expiry
93 * We don't have cascading anymore. timers with a expiry time above the
185 * wheels so we have a separate storage for the deferrable timers.
208 * @running_timer: When expiring timers, the lock is dropped. To make
[all …]
/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dmpic-timer.txt1 * Freescale MPIC timers
12 all timers within the group can be used.
16 interrupts that correspond to available timers shall be present.
24 /* Another AMP partition is using timers 0 and 1 */
/linux/Documentation/devicetree/bindings/timer/
H A Dmediatek,timer.yaml7 title: MediaTek SoC timers
13 MediaTek SoCs have different timers on different platforms,
25 # GPT Timers
38 # SYST Timers
/linux/include/linux/
H A Dhrtimer_defs.h14 * idea of the (in)accuracy of timers. Timer values are rounded up to
43 * @active: red black tree root node for the active timers
73 * and timers
75 * @active_bases: Bitfield to mark bases with active timers
/linux/include/uapi/linux/
H A Dtime.h39 * Names of the interval timers, and structure
47 * The IDs of the various system clocks (for POSIX.1b interval timers):
71 * The various flags for setting POSIX.1b interval timers:

12345678910>>...27