Home
last modified time | relevance | path

Searched +full:one +full:- +full:timer +full:- +full:only (Results 1 – 25 of 1035) sorted by relevance

12345678910>>...42

/Linux-v6.1/Documentation/devicetree/bindings/timer/
Dxlnx,xps-timer.yaml1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/timer/xlnx,xps-timer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx LogiCORE IP AXI Timer
10 - Sean Anderson <sean.anderson@seco.com>
15 const: xlnx,xps-timer-1.00.a
20 clock-names:
29 '#pwm-cells': true
31 xlnx,count-width:
[all …]
Dnvidia,tegra-timer.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: "http://devicetree.org/schemas/timer/nvidia,tegra-timer.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: NVIDIA Tegra timer
10 - Stephen Warren <swarren@nvidia.com>
13 - if:
17 const: nvidia,tegra210-timer
25 A list of 14 interrupts; one per each timer channels 0 through 13
27 - if:
[all …]
Darm,sp804.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/timer/arm,sp804.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Haojian Zhuang <haojian.zhuang@linaro.org>
14 16 or 32 bit operation and capable of running in one-shot, periodic, or
15 free-running mode. The input clock is shared, but can be gated and prescaled
16 independently for each timer.
18 There is a viriant of Arm SP804: Hisilicon 64-bit SP804 timer. Some Hisilicon
27 - arm,sp804
[all …]
Dsamsung,exynos4210-mct.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/timer/samsung,exynos4210-mct.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos SoC Multi Core Timer (MCT)
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 The Samsung's Multi Core Timer (MCT) module includes two main blocks, the
14 global timer and CPU local timers. The global timer is a 64-bit free running
15 up-counter and can generate 4 interrupts when the counter reaches one of the
16 four preset counter values. The CPU local timers are 32-bit free running
[all …]
Dnvidia,tegra186-timer.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/timer/nvidia,tegra186-timer.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: NVIDIA Tegra186 timer
10 - Thierry Reding <treding@nvidia.com>
13 The Tegra timer provides 29-bit timer counters and a 32-bit timestamp
14 counter. Each NV timer selects its timing reference signal from the 1 MHz
16 programmed to generate one-shot, periodic, or watchdog interrupts.
22 - const: nvidia,tegra186-timer
[all …]
Dbrcm,kona-timer.txt1 Broadcom Kona Family timer
2 -----------------------------------------------------
3 This timer is used in the following Broadcom SoCs:
7 - compatible : "brcm,kona-timer"
8 - DEPRECATED: compatible : "bcm,kona-timer"
9 - reg : Register range for the timer
10 - interrupts : interrupt for the timer
11 - clocks: phandle + clock specifier pair of the external clock
12 - clock-frequency: frequency that the clock operates
14 Only one of clocks or clock-frequency should be specified.
[all …]
Dingenic,sysost.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/timer/ingenic,sysost.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - 周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com>
13 The SYSOST in an Ingenic SoC provides one 64bit timer for clocksource
14 and one or more 32bit timers for clockevent.
17 "#clock-cells":
22 - ingenic,x1000-ost
23 - ingenic,x2000-ost
[all …]
Dcdns,ttc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/timer/cdns,ttc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Cadence TTC - Triple Timer Counter
10 - Michal Simek <michal.simek@xilinx.com>
22 A list of 3 interrupts; one per timer channel.
27 power-domains:
30 timer-width:
33 Bit width of the timer, necessary if not 16.
[all …]
/Linux-v6.1/Documentation/virt/kvm/x86/
Dtimekeeping.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Timekeeping Virtualization for X86-Based Architectures
20 One of the most complicated parts of the X86 platform, and specifically,
32 information relevant to KVM and hardware-based virtualization.
41 2.1. i8254 - PIT
42 ----------------
44 One of the first timer devices available is the programmable interrupt timer,
46 channels which can be programmed to deliver periodic or one-shot interrupts.
53 The PIT uses I/O ports 0x40 - 0x43. Access to the 16-bit counters is done
55 available, but not all modes are available to all timers, as only timer 2
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/soc/microchip/
Datmel,at91rm9200-tcb.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/microchip/atmel,at91rm9200-tcb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Atmel Timer Counter Block
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
13 The Atmel (now Microchip) SoCs have timers named Timer Counter Block. Each
14 timer has three channels with two counters each.
19 - enum:
20 - atmel,at91rm9200-tcb
[all …]
/Linux-v6.1/arch/arm/mach-at91/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
14 bool "SAM Cortex-M7 family" if ARM_SINGLE_ARMV7M
34 Select this if ou are using one of Microchip's SAMA5D2 family SoC.
45 Select this if you are using one of Microchip's SAMA5D3 family SoC.
59 Select this if you are using one of Microchip's SAMA5D4 family SoC.
70 Select this if you are using one of Microchip's SAMA7G5 family SoC.
111 Select this if you are using one of those Microchip SoC:
149 bool "Periodic Interval Timer (PIT) support"
155 Timer. It has a relatively low resolution and the TC Block clocksource
159 bool "Timer Counter Blocks (TCB) support"
[all …]
/Linux-v6.1/arch/parisc/kernel/
Dtime.c1 // SPDX-License-Identifier: GPL-2.0
9 * 1994-07-02 Alan Modra
11 * 1998-12-20 Updated NTP code according to technical memorandum Jan '96
45 static unsigned long clocktick __ro_after_init; /* timer cycles per tick */
48 * We keep time on PA-RISC Linux by using the Interval Timer which is
49 * a pair of registers; one is read-only and one is write-only; both
50 * accessed through CR16. The read-only register is 32 or 64 bits wide,
51 * and increments by 1 every CPU clock tick. The architecture only
53 * rate of 1. The write-only register is 32-bits wide. When the lowest
54 * 32 bits of the read-only register compare equal to the write-only
[all …]
/Linux-v6.1/drivers/watchdog/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
8 bool "Watchdog Timer Support"
10 If you say Y here (and to one of the following options) and create a
16 on-line as fast as possible after a lock-up. There's both a watchdog
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
34 tristate "WatchDog Timer Driver Core"
36 Say Y here if you want to use the new watchdog timer driver core.
37 This driver provides a framework for all watchdog timer drivers
45 to stop the timer if the process managing it closes the file
51 bool "Update boot-enabled watchdog until userspace takes over"
[all …]
/Linux-v6.1/Documentation/mips/
Dingenic-tcu.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Ingenic JZ47xx SoCs Timer/Counter Unit hardware
7 The Timer/Counter Unit (TCU) in Ingenic JZ47xx SoCs is a multi-function
11 - JZ4725B, JZ4750, JZ4755 only have six TCU channels. The other SoCs all
14 - JZ4725B introduced a separate channel, called Operating System Timer
15 (OST). It is a 32-bit programmable timer. On JZ4760B and above, it is
16 64-bit.
18 - Each one of the TCU channels has its own clock, which can be reparented to three
21 - The watchdog and OST hardware blocks also feature a TCSR register with the same
23 - The TCU registers used to gate/ungate can also gate/ungate the watchdog and
[all …]
/Linux-v6.1/include/soc/at91/
Datmel_tcb.h2 * Timer/Counter Unit (TC) registers.
17 * Many 32-bit Atmel SOCs include one or more TC blocks, each of which holds
18 * three general-purpose 16-bit timers. These timers share one register bank.
19 * Depending on the SOC, each timer may have its own clock and IRQ, or those
23 * clocks or clock gates, and per-timer TIOA and TIOB signals used for PWM
37 * struct atmel_tcb_config - SoC data for a Timer/Counter Block
38 * @counter_width: size in bits of a timer counter register
39 * @has_gclk: boolean indicating if a timer counter has a generic clock
40 * @has_qdec: boolean indicating if a timer counter has a quadrature
50 * struct atmel_tc - information about a Timer/Counter Block
[all …]
/Linux-v6.1/drivers/clocksource/
Dtimer-cs5535.c1 // SPDX-License-Identifier: GPL-2.0-only
19 #define DRV_NAME "cs5535-clockevt"
26 * We are using the 32.768kHz input clock - it's the only one that has the
53 * as clock event sources - not as good as a HPET or APIC, but certainly
55 * a simplified one designed specifically to act as a clock event source.
59 static void disable_timer(struct cs5535_mfgpt_timer *timer) in disable_timer() argument
62 cs5535_mfgpt_write(timer, MFGPT_REG_SETUP, in disable_timer()
67 static void start_timer(struct cs5535_mfgpt_timer *timer, uint16_t delta) in start_timer() argument
69 cs5535_mfgpt_write(timer, MFGPT_REG_CMP2, delta); in start_timer()
70 cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0); in start_timer()
[all …]
/Linux-v6.1/drivers/char/ipmi/
Dipmi_watchdog.c1 // SPDX-License-Identifier: GPL-2.0+
5 * A watchdog timer based upon the IPMI interface.
42 * This is ugly, but I've determined that x86 is the only architecture
56 * The IPMI command/response information for the watchdog timer.
97 * pre-timeout in seconds.
108 * Setting/getting the watchdog timer value. This is for bytes 5 and
134 /* The pre-timeout is disabled by default. */
159 static int ifnum_to_use = -1;
183 return -EINVAL; in set_param_timeout()
186 return -EINVAL; in set_param_timeout()
[all …]
/Linux-v6.1/Documentation/admin-guide/pm/
Dcpuidle.rst1 .. SPDX-License-Identifier: GPL-2.0
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
37 software as individual single-core processors. In other words, a CPU is an
38 entity which appears to be fetching instructions that belong to one sequence
42 First, if the whole processor can only follow one sequence of instructions (one
46 Second, if the processor is multi-core, each core in it is able to follow at
47 least one program at a time. The cores need not be entirely independent of each
49 work physically in parallel with each other, so if each of them executes only
50 one program, those programs run mostly independently of each other at the same
[all …]
/Linux-v6.1/arch/m68k/include/asm/
Dmac_via.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 * via them as are assorted bits and bobs - eg rtc, adb. The picture
59 * state-control line SEL" on all but IIfx
83 /* Macintosh Family Hardware sez: bits 0-2 of VIA1A are volume control
85 * On IIci,IIfx, bits 1-2 are the rest of the CPU ID:
89 * CHRP sez: VIA1A bits 0-2 and 5 are 'unused': if programmed as
112 #define VIA1B_vRTCClk 0x02 /* Real time clock serial-clock line. */
113 #define VIA1B_vRTCData 0x01 /* Real time clock serial-data line. */
117 * correspond to a VIA work-alike named 'EVR'. */
132 * defines the 'Video IRQ' as 0x40 for the 'EVR' VIA work-alike.
[all …]
/Linux-v6.1/drivers/staging/media/atomisp/pci/
Dia_css_event_public.h1 /* SPDX-License-Identifier: GPL-2.0 */
20 * This file contains CSS-API events functionality
64 /** Timer event for measuring the SP side latencies. It contains the
65 32-bit timer value from the SP */
110 The exposure ID is unique only within a logical stream and it is
111 only generated on systems that have an input system (such as 2400
118 Exposure IDs start at IA_CSS_MIN_EXPOSURE_ID, increment by one
128 /** Firmware warning code, only for WARNING events. */
130 /** Firmware module id, only for ASSERT events, should be logged by driver. */
132 /** Firmware line number, only for ASSERT events, should be logged by driver. */
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-timer.txt4 - compatible: "fsl,mpic-global-timer"
6 - reg : Contains two regions. The first is the main timer register bank
7 (GTCCRxx, GTBCRxx, GTVPRxx, GTDRxx). The second is the timer control
10 - fsl,available-ranges: use <start count> style section to define which
11 timer interrupts can be used. This property is optional; without this,
14 - interrupts: one interrupt per timer in the group, in order, starting
15 with timer zero. If timer-available-ranges is present, only the
19 /* Note that this requires #interrupt-cells to be 4 */
20 timer0: timer@41100 {
21 compatible = "fsl,mpic-global-timer";
[all …]
/Linux-v6.1/Documentation/kernel-hacking/
Dlocking.rst37 +------------------------------------+------------------------------------+
41 +------------------------------------+------------------------------------+
43 +------------------------------------+------------------------------------+
45 +------------------------------------+------------------------------------+
47 +------------------------------------+------------------------------------+
49 +------------------------------------+------------------------------------+
51 +------------------------------------+------------------------------------+
57 +------------------------------------+------------------------------------+
61 +------------------------------------+------------------------------------+
63 +------------------------------------+------------------------------------+
[all …]
/Linux-v6.1/drivers/counter/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 interface. You only need to enable this, if you also want to enable
11 one or more of the counter device drivers below.
16 tristate "ACCES 104-QUAD-8 driver"
20 Say yes here to build support for the ACCES 104-QUAD-8 quadrature
21 encoder counter/interface device family (104-QUAD-8, 104-QUAD-4).
25 104-QUAD-8 counters have a 25-bit range, only the lower 24 bits may be
40 module will be called interrupt-cnt.
43 tristate "STM32 Timer encoder counter driver"
46 Select this option to enable STM32 Timer quadrature encoder
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/watchdog/
Ddigicolor-wdt.txt1 Conexant Digicolor SoCs Watchdog timer
5 timer counters. The first timer (called "Timer A") is the only one that can be
10 - compatible : Should be "cnxt,cx92755-wdt"
11 - reg : Specifies base physical address and size of the registers
12 - clocks : phandle; specifies the clock that drives the timer
16 - timeout-sec : Contains the watchdog timeout in seconds
21 compatible = "cnxt,cx92755-wdt";
24 timeout-sec = <15>;
/Linux-v6.1/drivers/pwm/
Dpwm-xilinx.c1 // SPDX-License-Identifier: GPL-2.0+
6 * - When changing both duty cycle and period, we may end up with one cycle
8 * may only be reloaded by first stopping them, or by letting them be
13 * - Cannot produce 100% duty cycle by configuring the TLRs. This might be
16 * - Only produces "normal" output.
17 * - Always produces low output if disabled.
20 #include <clocksource/timer-xilinx.h>
22 #include <linux/clk-provider.h>
37 WARN_ON(cycles < 2 || cycles - 2 > priv->max); in xilinx_timer_tlr_cycles()
40 return cycles - 2; in xilinx_timer_tlr_cycles()
[all …]

12345678910>>...42