Home
last modified time | relevance | path

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

12345678910>>...33

/linux-6.12.1/drivers/staging/media/atomisp/pci/
Dgp_timer_defs.h24 #define HIVE_GP_TIMER_VALUE_REG_IDX(timer, timers) (HIVE_GP_TIMER_ENABLE_REG_IDX(time… argument
25 …efine HIVE_GP_TIMER_COUNT_TYPE_REG_IDX(timer, timers) (HIVE_GP_TIMER_VALUE_REG_IDX(timers… argument
26 …e HIVE_GP_TIMER_SIGNAL_SELECT_REG_IDX(timer, timers) (HIVE_GP_TIMER_COUNT_TYPE_REG_IDX(timer… argument
27 …HIVE_GP_TIMER_IRQ_TRIGGER_VALUE_REG_IDX(irq, timers) (HIVE_GP_TIMER_SIGNAL_SELECT_REG_IDX(time… argument
28 …IVE_GP_TIMER_IRQ_TIMER_SELECT_REG_IDX(irq, timers, irqs) (HIVE_GP_TIMER_IRQ_TRIGGER_VALUE_REG_IDX(… argument
29 …e HIVE_GP_TIMER_IRQ_ENABLE_REG_IDX(irq, timers, irqs) (HIVE_GP_TIMER_IRQ_TIMER_SELECT_REG_ID… argument
/linux-6.12.1/arch/powerpc/sysdev/
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-6.12.1/Documentation/timers/
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 …]
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 …]
/linux-6.12.1/fs/bcachefs/
Dclock.c40 for (size_t i = 0; i < clock->timers.nr; i++) in bch2_io_timer_add()
41 if (clock->timers.data[i] == timer) in bch2_io_timer_add()
44 BUG_ON(!min_heap_push(&clock->timers, &timer, &callbacks, NULL)); in bch2_io_timer_add()
58 for (size_t i = 0; i < clock->timers.nr; i++) in bch2_io_timer_del()
59 if (clock->timers.data[i] == timer) { in bch2_io_timer_del()
60 min_heap_del(&clock->timers, i, &callbacks, NULL); in bch2_io_timer_del()
150 if (clock->timers.nr && in get_expired_timer()
151 time_after_eq64(now, clock->timers.data[0]->expire)) { in get_expired_timer()
152 ret = *min_heap_peek(&clock->timers); in get_expired_timer()
153 min_heap_pop(&clock->timers, &callbacks, NULL); in get_expired_timer()
[all …]
/linux-6.12.1/Documentation/sound/
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-6.12.1/drivers/clocksource/
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 …]
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()
/linux-6.12.1/drivers/remoteproc/
Domap_remoteproc.c93 * @num_wd_timers: number of rproc watchdog timers
94 * @timers: timer(s) info used by rproc
111 struct omap_rproc_timer *timers; member
263 * timers associated with a rproc (like IPUs which have 2 watchdog timers,
277 struct omap_rproc_timer *timers = oproc->timers; in omap_rproc_watchdog_isr() local
283 if (timers[i].irq > 0 && irq == timers[i].irq) { in omap_rproc_watchdog_isr()
284 wd_timer = &timers[i]; in omap_rproc_watchdog_isr()
302 * omap_rproc_enable_timers() - enable the timers for a remoteproc
306 * This function is used primarily to enable the timers associated with
321 struct omap_rproc_timer *timers = oproc->timers; in omap_rproc_enable_timers() local
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/remoteproc/
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-6.12.1/arch/arm/boot/dts/st/
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 …]
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-6.12.1/Documentation/devicetree/bindings/mips/brcm/
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-6.12.1/arch/arm/boot/dts/ti/omap/
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-6.12.1/drivers/misc/
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-6.12.1/Documentation/devicetree/bindings/pwm/
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";
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";
/linux-6.12.1/kernel/time/
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
526 * Clean out CPU timers which are still armed when a thread exits. The
527 * timers are only removed from the list. No other updates are done. The
528 * corresponding posix timers are still accessible, but cannot be rearmed.
554 * Insert the timer on the appropriate list before any timers that
570 * for process timers we share expiration cache with itimers in arm_timer()
571 * and RLIMIT_CPU and for thread timers with RLIMIT_RTTIME. in arm_timer()
618 * Guts of sys_timer_settime for CPU timers.
[all …]
Dposix-timers.c3 * 2002-10-15 Posix Clocks & timers
10 * These are all the functions necessary to implement POSIX clocks & timers
25 #include <linux/posix-timers.h>
36 #include "posix-timers.h"
41 * Timers are managed in a hash table for lockless lookup. The hash key is
315 * based timers.
341 * For now let timers with an interval less than a in posix_timer_fn()
356 * Only required when high resolution timers are in posix_timer_fn()
357 * enabled as the periodic tick based timers are in posix_timer_fn()
573 * The hash lookup and the timers are RCU protected. in __lock_timer()
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/timer/
Dsamsung,exynos4210-mct.yaml14 global timer and CPU local timers. The global timer is a 64-bit free running
16 four preset counter values. The CPU local timers are 32-bit free running
56 samsung,local-timers:
61 List of indices of local timers usable from this processor.
77 For MCT block that uses a per-processor interrupt for local timers, such
79 interrupt might be specified, meaning that all local timers use the same
101 samsung,local-timers: false
158 // In this example, the IP contains two local timers, using separate
199 // In this example, the IP contains four local timers, but using
219 // In this example, the IP contains four local timers, but using
/linux-6.12.1/Documentation/devicetree/bindings/mfd/
Dst,stm32-timers.yaml4 $id: http://devicetree.org/schemas/mfd/st,stm32-timers.yaml#
7 title: STMicroelectronics STM32 Timers
11 - advanced-control timers consist of a 16-bit auto-reload counter driven
14 - general-purpose timers consist of a 16-bit or 32-bit auto-reload counter
16 - basic timers consist of a 16-bit auto-reload counter driven by a
24 const: st,stm32-timers
156 compatible = "st,stm32-timers";
/linux-6.12.1/include/kvm/
Darm_arch_timer.h88 struct arch_timer_context timers[NR_KVM_TIMERS]; member
123 #define vcpu_get_timer(v,t) (&vcpu_timer(v)->timers[(t)])
124 #define vcpu_vtimer(v) (&(v)->arch.timer_cpu.timers[TIMER_VTIMER])
125 #define vcpu_ptimer(v) (&(v)->arch.timer_cpu.timers[TIMER_PTIMER])
126 #define vcpu_hvtimer(v) (&(v)->arch.timer_cpu.timers[TIMER_HVTIMER])
127 #define vcpu_hptimer(v) (&(v)->arch.timer_cpu.timers[TIMER_HPTIMER])
129 #define arch_timer_ctx_index(ctx) ((ctx) - vcpu_timer((ctx)->vcpu)->timers)
/linux-6.12.1/Documentation/virt/hyperv/
Dclocks.rst3 Clocks and Timers
14 per-CPU timers as described in the TLFS, they are not used by the
20 out-of-tree patch to use the Hyper-V synthetic clocks/timers instead.
25 and four synthetic per-CPU timers as described in the TLFS. Hyper-V
66 While Hyper-V offers 4 synthetic timers for each CPU, Linux only uses
81 The driver for the Hyper-V synthetic system clock and timers is
/linux-6.12.1/Documentation/devicetree/bindings/powerpc/fsl/
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-6.12.1/drivers/leds/
Dleds-netxbig.c427 struct netxbig_led_timer *timers; in netxbig_leds_get_of_pdata() local
459 /* Timers (optional) */ in netxbig_leds_get_of_pdata()
460 ret = of_property_count_u32_elems(np, "timers"); in netxbig_leds_get_of_pdata()
468 timers = devm_kcalloc(dev, num_timers, sizeof(*timers), in netxbig_leds_get_of_pdata()
470 if (!timers) { in netxbig_leds_get_of_pdata()
477 of_property_read_u32_index(np, "timers", 3 * i, in netxbig_leds_get_of_pdata()
478 &timers[i].mode); in netxbig_leds_get_of_pdata()
479 if (timers[i].mode >= NETXBIG_LED_MODE_NUM) { in netxbig_leds_get_of_pdata()
483 of_property_read_u32_index(np, "timers", in netxbig_leds_get_of_pdata()
485 timers[i].delay_on = tmp; in netxbig_leds_get_of_pdata()
[all …]

12345678910>>...33