Searched full:real (Results 1 – 25 of 467) sorted by relevance
12345678910>>...19
| /Documentation/devicetree/bindings/rtc/ |
| D | trivial-rtc.yaml | 23 # AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
25 # AB-RTCMC-32.768kHz-EOZ9: Real Time Clock/Calendar Module with I2C Interface
27 # ASPEED BMC ast2400 Real-time Clock
29 # ASPEED BMC ast2500 Real-time Clock
31 # ASPEED BMC ast2600 Real-time Clock
33 # Conexant Digicolor Real Time Clock Controller
37 # Dallas DS1672 Real-time Clock
41 # SD2405AL Real-Time Clock
45 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
47 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
[all …]
|
| D | xgene-rtc.txt | 1 * APM X-Gene Real Time Clock
3 RTC controller for the APM X-Gene Real Time Clock
|
| D | xlnx,zynqmp-rtc.yaml | 7 title: Xilinx Zynq Ultrascale+ MPSoC Real Time Clock
10 RTC controller for the Xilinx Zynq MPSoC Real Time Clock.
|
| D | rtc.yaml | 7 title: Real Time Clock Common Properties
14 describe Real Time Clock devices in a device tree.
|
| /Documentation/mm/ |
| D | active_mm.rst | 30 - we have "real address spaces" and "anonymous address spaces". The
38 this category, but even "real" threads can temporarily say that for
44 - "tsk->mm" points to the "real address space". For an anonymous process,
46 really doesn't _have_ a real address space at all.
52 The rule is that for a process with a real address space (ie tsk->mm is
53 non-NULL) the active_mm obviously always has to be the same as the real
62 "mm_users" counter that is how many "real address space users" there are,
64 users) plus one if there are any real users.
66 Usually there is at least one real user, but it could be that the real
70 gets scheduled away in favour of a real thread, the "zombie" mm gets
[all …]
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 21 debugobjects is not changing the data structure of the real object so it
53 Each of these functions takes the address of the real object and a
70 This function is called whenever the initialization function of a real
73 When the real object is already tracked by debugobjects it is checked,
78 problem before the real initialization of the object happens. E.g. it
82 When the real object is not yet tracked by debugobjects, debugobjects
83 allocates a tracker object for the real object and sets the tracker
93 This function is called whenever the initialization function of a real
96 When the real object is already tracked by debugobjects it is checked,
101 problem before the real initialization of the object happens. E.g. it
[all …]
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 2 Real-Time group scheduling
33 are real-time processes).
42 Real-time scheduling is all about determinism, a group has to be able to rely on
44 multiple groups of real-time tasks, each group must be assigned a fixed portion
45 of the CPU time available. Without a minimum guarantee a real-time group can
53 in a given period. We allocate this "run time" for each real-time group which
54 the other real-time groups will not be permitted to use.
56 Any time not allocated to a real-time group will be used to run normal priority
60 Let's consider an example: a frame fixed real-time renderer must deliver 25
73 real-time tasks have explicitly allocated the CPU time they need to perform
[all …]
|
| D | sched-deadline.rst | 12 3. Scheduling Real-Time Tasks
70 with the "traditional" real-time task model (see Section 3) can effectively
108 said to be "throttled" (also known as "depleted" in real-time literature)
165 real-time guarantees. It therefore enters a transitional state called
168 breaking the real-time guarantees.
302 3. Scheduling Real-Time Tasks
322 suited for periodic or sporadic real-time tasks that need guarantees on their
328 A typical real-time task is composed of a repetition of computation phases
336 A real-time task can be periodic with period P if r_{j+1} = r_j + P, or
339 Summing up, a real-time task can be described as
[all …]
|
| /Documentation/dev-tools/kunit/api/ |
| D | functionredirection.rst | 39 Static stubs are a way of redirecting calls to one function (the "real"
42 It works by adding a macro to the "real" function which checks to see if a test
48 1. Add the KUNIT_STATIC_STUB_REDIRECT() macro to the start of the "real"
53 function, followed by all of the arguments passed to the real function.
62 /* real implementation */
67 These functions should have the same function signature as the real function.
87 the real function, and the replacement function. You can call this several
99 4. Call (perhaps indirectly) the real function.
101 Once the redirection is activated, any call to the real function will call
115 original behaviour of the 'real' function) using
[all …]
|
| /Documentation/arch/parisc/ |
| D | debugging.rst | 12 A lot of the assembly code currently runs in real mode, which means
22 When real-mode code tries to access non-existent memory, you'll get
26 the I/O range); the System Responder address is the address real-mode
31 get translated to a physical address before real-mode code tried to
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rtc-rtc0-device-rtc_calibration | 5 Description: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock
7 calibrate the AB8500.s 32KHz Real Time Clock.
|
| /Documentation/driver-api/hte/ |
| D | tegra-hte.rst | 17 This GTE instance timestamps GPIO in real time. For that to happen GPIO
19 instance supports timestamping GPIOs in real time as it is tightly coupled with
37 This GTE instance timestamps LIC IRQ lines in real time. The hte devicetree
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-sdr-ru12le.rst | 10 Real unsigned 12-bit little endian sample
16 This format contains sequence of real number samples. Each sample is
|
| /Documentation/gpu/rfc/ |
| D | i915_gem_lmem.rst | 8 real, with all the uAPI bits is:
22 * Add pciid for DG1 and turn on uAPI for real
|
| /Documentation/arch/x86/ |
| D | buslock.rst | 83 It is critical for real time system designers who build consolidated real
84 time systems. These systems run hard real time code on some cores and run
85 "untrusted" user processes on other cores. The hard real time cannot afford
86 to have any bus lock from the untrusted processes to hurt real time
89 generating split lock and bus lock to block the hard real time code to
|
| D | boot.rst | 12 real-mode DOS as a mainstream operating system.
103 | Stack/heap | For use by the kernel real-mode code.
105 | Kernel setup | The kernel real-mode code.
121 0x100000 ("high memory"), and the kernel real-mode block (boot sector,
154 | Stack/heap | For use by the kernel real-mode code.
156 | Kernel setup | The kernel real-mode code.
171 The Real-Mode Kernel Header
179 real-mode code (boot sector and setup code) and then examine the
180 following header at offset 0x01f1. The real-mode code can total up to
233 real value is 4.
[all …]
|
| D | usb-legacy-support.rst | 19 mouse is present and a real PS/2 mouse is present. In that case the extra
20 features (wheel, extra buttons, touchpad mode) of the real PS/2 mouse may
|
| /Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 22 a race is possible with loading the driver and the real rootfs not yet being
30 when the real rootfs is ready and mounted.
|
| /Documentation/tools/rtla/ |
| D | rtla.rst | 5 Real-time Linux Analysis tool
17 analyze the real-time properties of Linux. But instead of testing Linux
|
| /Documentation/admin-guide/ |
| D | initrd.rst | 38 6) init mounts the "real" root file system
214 and proceeds with starting the Linux system on the "real" root device.
282 2) ``/sbin/init`` determines what is needed to (1) mount the "real" root FS
332 It works by mounting the "real" root device (i.e. the one set with rdev
340 the real root file system, not the initrd environment.)
342 If /proc is mounted, the "real" root device can be changed from within
344 file /proc/sys/kernel/real-root-dev, e.g.::
346 # echo 0x301 >/proc/sys/kernel/real-root-dev
366 echo 0x0100 >/proc/sys/kernel/real-root-dev
372 the cmdline) before the final execution of the real ``/sbin/init``.
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | atmel,at91sam9260-shdwc.yaml | 41 description: enable real-time timer wake-up
45 description: enable real-time clock wake-up
|
| /Documentation/sound/designs/ |
| D | seq-oss.rst | 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.
159 be processed in real-time. Sending an event ABSTIME 0 switches the operation
160 mode to real-time mode, and sending an event RELTIME 0 switches it off.
161 In the real-time mode, all events are dispatched immediately.
|
| /Documentation/hwmon/ |
| D | ltc4260.rst | 45 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
51 is installed. If a different sense resistor is installed, calculate the real
|
| /Documentation/timers/ |
| D | no_hz.rst | 10 applications and for real-time applications.
59 In addition, if you are running either a real-time workload or an HPC
94 Therefore, systems with aggressive real-time response constraints often
115 for applications with aggressive real-time response constraints because
157 Real-time applications needing to take actions based on CPU time
169 This might in turn perturb load-balancing of real-time tasks.
172 useful for many types of real-time and compute-intensive applications.
228 aggressive real-time workloads, which have the option of disabling
|
| /Documentation/admin-guide/device-mapper/ |
| D | snapshot.rst | 112 volumeGroup-base-real: 0 2097152 linear 8:19 384
118 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
128 "snapshot-merge". The "-real" device is not changed and the "-cow"
142 volumeGroup-base-real: 0 2097152 linear 8:19 384
147 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
|
12345678910>>...19