Home
last modified time | relevance | path

Searched +full:real +full:- +full:time (Results 1 – 25 of 1072) sorted by relevance

12345678910>>...43

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/
Dtrivial-rtc.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
18 - $ref: "rtc.yaml#"
23 # AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
24 - abracon,abb5zes3
25 # AB-RTCMC-32.768kHz-EOZ9: Real Time Clock/Calendar Module with I2C Interface
26 - abracon,abeoz9
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/rtc/
Dtrivial-rtc.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
18 - $ref: rtc.yaml#
23 # AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
24 - abracon,abb5zes3
25 # AB-RTCMC-32.768kHz-EOZ9: Real Time Clock/Calendar Module with I2C Interface
26 - abracon,abeoz9
[all …]
/kernel/linux/linux-6.6/Documentation/scheduler/
Dsched-deadline.rst12 3. Scheduling Real-Time Tasks
18 4.1 System-wide settings
33 system behavior. As for -rt (group) scheduling, it is assumed that root users
50 ------------------
54 "runtime" microseconds of execution time every "period" microseconds, and
57 every time the task wakes up, the scheduler computes a "scheduling deadline"
61 task actually receives "runtime" time units within "deadline" if a proper
70 with the "traditional" real-time task model (see Section 3) can effectively
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
79 - The state of the task is described by a "scheduling deadline", and
[all …]
/kernel/linux/linux-5.10/Documentation/scheduler/
Dsched-deadline.rst12 3. Scheduling Real-Time Tasks
18 4.1 System-wide settings
33 system behavior. As for -rt (group) scheduling, it is assumed that root users
50 ------------------
54 "runtime" microseconds of execution time every "period" microseconds, and
57 every time the task wakes up, the scheduler computes a "scheduling deadline"
61 task actually receives "runtime" time units within "deadline" if a proper
70 with the "traditional" real-time task model (see Section 3) can effectively
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
79 - The state of the task is described by a "scheduling deadline", and
[all …]
/kernel/linux/linux-6.6/include/linux/mfd/syscon/
Datmel-st.h1 /* SPDX-License-Identifier: GPL-2.0+ */
6 * System Timer (ST) - System peripherals registers.
26 #define AT91_ST_RTMR 0x0c /* Real-time Mode Register */
27 #define AT91_ST_RTPRES 0xffff /* Real-time Prescalar Value */
32 #define AT91_ST_RTTINC BIT(2) /* Real-time Timer Increment */
39 #define AT91_ST_RTAR 0x20 /* Real-time Alarm Register */
42 #define AT91_ST_CRTR 0x24 /* Current Real-time Register */
43 #define AT91_ST_CRTV 0xfffff /* Current Real-Time Value */
/kernel/linux/linux-5.10/include/linux/mfd/syscon/
Datmel-st.h1 /* SPDX-License-Identifier: GPL-2.0+ */
6 * System Timer (ST) - System peripherals registers.
26 #define AT91_ST_RTMR 0x0c /* Real-time Mode Register */
27 #define AT91_ST_RTPRES 0xffff /* Real-time Prescalar Value */
32 #define AT91_ST_RTTINC BIT(2) /* Real-time Timer Increment */
39 #define AT91_ST_RTAR 0x20 /* Real-time Alarm Register */
42 #define AT91_ST_CRTR 0x24 /* Current Real-time Register */
43 #define AT91_ST_CRTV 0xfffff /* Current Real-Time Value */
/kernel/linux/linux-6.6/include/linux/
Dtimekeeping.h1 /* SPDX-License-Identifier: GPL-2.0 */
24 * ktime_get() family: read the current time in a multitude of ways,
26 * The default time reference is CLOCK_MONOTONIC, starting at
27 * boot time but not counting the time spent in suspend.
28 * For other references, use the functions with "real", "clocktai",
31 * To get the time in a different format, use the ones wit
34 * See Documentation/core-api/timekeeping.rst for more details.
75 * ktime_get_real - get the real (wall-) time in ktime_t format
88 * ktime_get_boottime - Returns monotonic time since boot in ktime_t format
91 * time spent in suspend.
[all …]
/kernel/linux/linux-5.10/include/linux/
Dtimekeeping.h1 /* SPDX-License-Identifier: GPL-2.0 */
24 * ktime_get() family: read the current time in a multitude of ways,
26 * The default time reference is CLOCK_MONOTONIC, starting at
27 * boot time but not counting the time spent in suspend.
28 * For other references, use the functions with "real", "clocktai",
31 * To get the time in a different format, use the ones wit
34 * See Documentation/core-api/timekeeping.rst for more details.
75 * ktime_get_real - get the real (wall-) time in ktime_t format
88 * ktime_get_boottime - Returns monotonic time since boot in ktime_t format
91 * time spent in suspend.
[all …]
/kernel/liteos_a/testsuites/unittest/libc/time/clock/full/
Dclock_test_006.cpp2 * Copyright (c) 2013-2019 Huawei Technologies Co., Ltd. All rights reserved.
3 * Copyright (c) 2020-2021 Huawei Device Co., Ltd. All rights reserved.
34 #include <time.h>
40 /* When clock time is changed, timers for a relative interval are unaffected,
41 * but timers for an absolute point in time are affected.
56 /* get current real coarse time */ in ClockTest()
59 printf("The current coarse real time: sec is %lld, nsec is %ld\n", oldtp.tv_sec, oldtp.tv_nsec); in ClockTest()
64 /* set real coarse time */ in ClockTest()
66 ICUNIT_ASSERT_EQUAL(ret, -1, ret); in ClockTest()
69 printf("get coarse real time clock again\n"); in ClockTest()
[all …]
Dclock_test_001.cpp2 * Copyright (c) 2013-2019 Huawei Technologies Co., Ltd. All rights reserved.
3 * Copyright (c) 2020-2021 Huawei Device Co., Ltd. All rights reserved.
34 #include <time.h>
40 /* When clock time is changed, timers for a relative interval are unaffected,
41 * but timers for an absolute point in time are affected.
56 /* get current real time */ in ClockTest()
58 printf("The current real time: sec is %lld, nsec is %ld\n", oldtp.tv_sec, oldtp.tv_nsec); in ClockTest()
67 /* set real time */ in ClockTest()
69 printf("Setting time: sec is %lld, nsec is %ld\n", tp.tv_sec, tp.tv_nsec); in ClockTest()
72 printf("get real time clock again\n"); in ClockTest()
[all …]
/kernel/linux/linux-5.10/drivers/rtc/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
14 bool "Real Time Clock"
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
31 unnecessary fsck runs at boot time, and to network better.
34 string "RTC used to set the system time"
41 device should record time in UTC, since the kernel won't do
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
49 be useful to reinitialize system time when resuming from system
[all …]
Drtc-at91sam9.c1 // SPDX-License-Identifier: GPL-2.0+
3 * "RTT as Real Time Clock" driver for AT91SAM9 SoC family
7 * Based on rtc-at91rm9200.c by Rick Bronson
23 #include <linux/time.h>
28 * to implement the Real Time Clock interfaces
30 * - A "Real-time Timer" (RTT) counts up in seconds from a base time.
33 * - One of the "General Purpose Backup Registers" (GPBRs) holds the
34 * base time, normally an offset from the beginning of the POSIX
35 * epoch (1970-Jan-1 00:00:00 UTC). Some systems also include the
42 * choose from, or a "real" RTC module. All systems have multiple GPBR
[all …]
/kernel/linux/linux-5.10/include/uapi/linux/
Dacct.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
3 * BSD Process Accounting for Linux - Definitions
8 * BSD-style process accounting. The kernel accounting code and all
9 * user-level programs that try to do something useful with the
12 * Copyright (C) 1995 - 1997 Marco van Wieringen - ELM Consultancy B.V.
25 * comp_t is a 16-bit "floating" point number with a 3-bit base 8
26 * exponent and a 13-bit fraction.
27 * comp2_t is 24-bit with 5-bit base 2 exponent and 20 bit fraction
49 __u16 ac_uid16; /* LSB of Real User ID */
50 __u16 ac_gid16; /* LSB of Real Group ID */
[all …]
/kernel/linux/linux-6.6/include/uapi/linux/
Dacct.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
3 * BSD Process Accounting for Linux - Definitions
8 * BSD-style process accounting. The kernel accounting code and all
9 * user-level programs that try to do something useful with the
12 * Copyright (C) 1995 - 1997 Marco van Wieringen - ELM Consultancy B.V.
25 * comp_t is a 16-bit "floating" point number with a 3-bit base 8
26 * exponent and a 13-bit fraction.
27 * comp2_t is 24-bit with 5-bit base 2 exponent and 20 bit fraction
49 __u16 ac_uid16; /* LSB of Real User ID */
50 __u16 ac_gid16; /* LSB of Real Group ID */
[all …]
/kernel/linux/linux-6.6/drivers/rtc/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
14 bool "Real Time Clock"
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
31 unnecessary fsck runs at boot time, and to network better.
34 string "RTC used to set the system time"
41 device should record time in UTC, since the kernel won't do
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
49 be useful to reinitialize system time when resuming from system
[all …]
Drtc-at91sam9.c1 // SPDX-License-Identifier: GPL-2.0+
3 * "RTT as Real Time Clock" driver for AT91SAM9 SoC family
7 * Based on rtc-at91rm9200.c by Rick Bronson
23 #include <linux/time.h>
28 * to implement the Real Time Clock interfaces
30 * - A "Real-time Timer" (RTT) counts up in seconds from a base time.
33 * - One of the "General Purpose Backup Registers" (GPBRs) holds the
34 * base time, normally an offset from the beginning of the POSIX
35 * epoch (1970-Jan-1 00:00:00 UTC). Some systems also include the
42 * choose from, or a "real" RTC module. All systems have multiple GPBR
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Datmel-sysregs.txt4 - compatible: Should be "atmel,sama5d2-chipid"
5 - reg : Should contain registers location and length
8 - compatible: Should be "atmel,at91sam9260-pit"
9 - reg: Should contain registers location and length
10 - interrupts: Should contain interrupt for the PIT which is the IRQ line
14 - compatible: Should be "microchip,sam9x60-pit64b"
15 - reg: Should contain registers location and length
16 - interrupts: Should contain interrupt for PIT64B timer
17 - clocks: Should contain the available clock sources for PIT64B timer.
20 - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd"
[all …]
/kernel/linux/linux-5.10/Documentation/vm/
Dactive_mm.rst9 List: linux-kernel
12 Date: 1999-07-30 21:36:24
14 Cc'd to linux-kernel, because I don't write explanations all that often,
21 > discussed on the mailing lists---I just returned from vacation and
22 > wasn't able to follow linux-kernel for a while).
26 - we have "real address spaces" and "anonymous address spaces". The
28 user-level page tables at all, so when we do a context switch into an
33 doesn't need any user mappings - all kernel threads basically fall into
34 this category, but even "real" threads can temporarily say that for
35 some amount of time they are not going to be interested in user space,
[all …]
/kernel/linux/linux-6.6/Documentation/mm/
Dactive_mm.rst6 (running tasks with ->active_mm == mm && ->mm == NULL) on kernels
13 List: linux-kernel
16 Date: 1999-07-30 21:36:24
18 Cc'd to linux-kernel, because I don't write explanations all that often,
25 > discussed on the mailing lists---I just returned from vacation and
26 > wasn't able to follow linux-kernel for a while).
30 - we have "real address spaces" and "anonymous address spaces". The
32 user-level page tables at all, so when we do a context switch into an
37 doesn't need any user mappings - all kernel threads basically fall into
38 this category, but even "real" threads can temporarily say that for
[all …]
/kernel/linux/linux-6.6/kernel/rcu/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # RCU-related configuration options
11 # Dynticks-idle tracking
26 thousands of CPUs, but for which real-time response
37 designed for UP systems from which real-time response
42 bool "Make expert-level adjustments to RCU configuration"
46 expert-level adjustments to RCU configuration. By default,
47 no such adjustments can be made, which has the often-beneficial
48 side-effect of preventing "make oldconfig" from asking you all
52 Say Y if you need to make expert-level adjustments to RCU.
[all …]
/kernel/linux/linux-5.10/Documentation/sound/designs/
Dseq-oss.rst15 What this does - it provides the emulation of the OSS sequencer, access
53 However, each MIDI device is exclusive - that is, if a MIDI device
57 * Real-time event processing:
59 The events can be processed in real time without using out of bound
60 ioctl. To switch to real-time mode, send ABSTIME 0 event. The followed
61 events will be processed in real-time without queued. To switch off the
62 real-time mode, send RELTIME 0 event.
67 ``/proc/asound/seq/oss`` at any time. In the later version,
74 Run configure script with both sequencer support (``--with-sequencer=yes``)
75 and OSS emulation (``--with-oss=yes``) options. A module ``snd-seq-oss.o``
[all …]
/kernel/linux/linux-6.6/Documentation/sound/designs/
Dseq-oss.rst15 What this does - it provides the emulation of the OSS sequencer, access
53 However, each MIDI device is exclusive - that is, if a MIDI device
57 * Real-time event processing:
59 The events can be processed in real time without using out of bound
60 ioctl. To switch to real-time mode, send ABSTIME 0 event. The followed
61 events will be processed in real-time without queued. To switch off the
62 real-time mode, send RELTIME 0 event.
67 ``/proc/asound/seq/oss`` at any time. In the later version,
74 Run configure script with both sequencer support (``--with-sequencer=yes``)
75 and OSS emulation (``--with-oss=yes``) options. A module ``snd-seq-oss.o``
[all …]
/kernel/linux/linux-6.6/Documentation/arch/x86/
Dbuslock.rst1 .. SPDX-License-Identifier: GPL-2.0
10 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
11 - Tony Luck <tony.luck@intel.com>
21 memory or any locked access to non-WB memory. This is typically thousands of
32 --------------------------------------
38 ------------------------------------
50 +------------------+----------------------------+-----------------------+
52 +------------------+----------------------------+-----------------------+
54 +------------------+----------------------------+-----------------------+
66 +------------------+----------------------------+-----------------------+
[all …]
/kernel/linux/linux-6.6/Documentation/timers/
Dno_hz.rst2 NO_HZ: Reducing Scheduling-Clock Ticks
7 reduce the number of scheduling-clock interrupts, thereby improving energy
9 some types of computationally intensive high-performance computing (HPC)
10 applications and for real-time applications.
12 There are three main ways of managing scheduling-clock interrupts
13 (also known as "scheduling-clock ticks" or simply "ticks"):
15 1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or
16 CONFIG_NO_HZ=n for older kernels). You normally will -not-
19 2. Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or
23 3. Omit scheduling-clock ticks on CPUs that are either idle or that
[all …]
/kernel/linux/linux-5.10/kernel/
DKconfig.preempt1 # SPDX-License-Identifier: GPL-2.0-only
12 time, but there are no guarantees and occasional longer delays
39 bool "Preemptible Kernel (Low-Latency Desktop)"
59 bool "Fully Preemptible Kernel (Real-Time)"
63 This option turns the kernel into a real-time kernel by replacing
65 preemptible priority-inheritance aware variants, enforcing
67 non-preemptible sections. This makes the kernel, except for very
73 require real-time guarantees.

12345678910>>...43