Home
last modified time | relevance | path

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

12345678910>>...19

/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 …]
Dxgene-rtc.txt1 * APM X-Gene Real Time Clock
3 RTC controller for the APM X-Gene Real Time Clock
6 - compatible : Should be "apm,xgene-rtc"
7 - reg: physical base address of the controller and length of memory mapped
9 - interrupts: IRQ line for the RTC.
10 - #clock-cells: Should be 1.
11 - clocks: Reference to the clock entry.
16 compatible = "fixed-clock";
17 #clock-cells = <1>;
18 clock-frequency = <100000000>;
[all …]
Dxlnx,zynqmp-rtc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rtc/xlnx,zynqmp-rtc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx Zynq Ultrascale+ MPSoC Real Time Clock
10 RTC controller for the Xilinx Zynq MPSoC Real Time Clock.
14 - Michal Simek <michal.simek@amd.com>
17 - $ref: rtc.yaml#
22 - const: xlnx,zynqmp-rtc
23 - items:
[all …]
Drtc.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Real Time Clock Common Properties
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
14 describe Real Time Clock devices in a device tree.
18 pattern: "^rtc(@.*|-([0-9]|[1-9][0-9]+))?$"
20 aux-voltage-chargeable:
29 quartz-load-femtofarads:
31 The capacitive load of the quartz(x-tal), expressed in femto
[all …]
/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 …]
/Documentation/core-api/
Ddebug-objects.rst2 The object-lifetime debugging infrastructure
15 - Activation of uninitialized objects
17 - Initialization of active objects
19 - Usage of freed/destroyed objects
21 debugobjects is not changing the data structure of the real object so it
39 - debug_object_init
41 - debug_object_init_on_stack
43 - debug_object_activate
45 - debug_object_deactivate
47 - debug_object_destroy
[all …]
/Documentation/scheduler/
Dsched-rt-group.rst2 Real-Time group scheduling
12 2.1 System-wide settings
33 are real-time processes).
40 ---------------
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
50 ----------------
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.
[all …]
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 ------------------
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
82 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
86 ---------------------------------- > ---------
87 scheduling deadline - current time period
[all …]
/Documentation/dev-tools/kunit/api/
Dfunctionredirection.rst1 .. SPDX-License-Identifier: GPL-2.0
14 stability of the rest of the system (making it less likely for test-specific
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.
57 .. code-block:: c
62 /* real implementation */
67 These functions should have the same function signature as the real function.
68 In the event they need to access or modify test-specific state, they can use
[all …]
/Documentation/arch/parisc/
Ddebugging.rst2 PA-RISC Debugging
5 okay, here are some hints for debugging the lower-level parts of
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
41 was interrupted - so if you get an interruption between the instruction
/Documentation/ABI/testing/
Dsysfs-class-rtc-rtc0-device-rtc_calibration5 Description: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock
7 calibrate the AB8500.s 32KHz Real Time Clock.
11 The range of the attribute is -127 to +127 in units of
12 30.5 micro-seconds (half-parts-per-million of the 32KHz clock)
13 Users: The /vendor/st-ericsson/base_utilities/core/rtc_calibration
/Documentation/driver-api/hte/
Dtegra-hte.rst1 .. SPDX-License-Identifier: GPL-2.0+
7 -----------
15 --------
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
31 specified during IOCTL calls. Refer to ``tools/gpio/gpio-event-mon.c``, which
35 -----------------------------------------
37 This GTE instance timestamps LIC IRQ lines in real time. The hte devicetree
40 one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
45 ``drivers/hte/hte-tegra194.c``. The test driver
[all …]
/Documentation/userspace-api/media/v4l/
Dpixfmt-sdr-ru12le.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _V4L2-SDR-FMT-RU12LE:
10 Real unsigned 12-bit little endian sample
16 This format contains sequence of real number samples. Each sample is
26 .. flat-table::
27 :header-rows: 0
28 :stub-columns: 0
30 * - start + 0:
31 - I'\ :sub:`0[7:0]`
32 - I'\ :sub:`0[11:8]`
/Documentation/gpu/rfc/
Di915_gem_lmem.rst8 real, with all the uAPI bits is:
13 start running IGTs which can utilize local-memory in CI
21 * Send RFC(with mesa-dev on cc) for final sign off on the uAPI
22 * Add pciid for DG1 and turn on uAPI for real
/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 …]
Dboot.rst1 .. SPDX-License-Identifier: GPL-2.0
12 real-mode DOS as a mainstream operating system.
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
31 safe for systems which use the EBDA from SMM or 32-bit
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
54 Protocol 2.09 (Kernel 2.6.26) Added a field of 64-bit physical
68 Protocol 2.13 (Kernel 3.14) Support 32- and 64-bit flags being set in
69 xloadflags to support booting a 64-bit kernel from 32-bit
99 0A0000 +------------------------+
101 09A000 +------------------------+
[all …]
Dusb-legacy-support.rst2 .. SPDX-License-Identifier: GPL-2.0
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
27 3) If AMD64 64-bit mode is enabled, again system crashes often happen,
28 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The
29 BIOS manufacturers only test with Windows, and Windows doesn't do 64-bit
38 compiled-in, too.
/Documentation/tools/rtla/
Drtla.rst4 --------------------------------
5 Real-time Linux Analysis tool
6 --------------------------------
16 The **rtla** is a meta-tool that includes a set of commands that aims to
17 analyze the real-time properties of Linux. But instead of testing Linux
34 **-h**, **--help**
42 **rtla-osnoise**\(1), **rtla-timerlat**\(1)
/Documentation/driver-api/firmware/
Ddirect-fs-lookup.rst10 The max path allowed is PATH_MAX -- currently this is 4096 characters.
18 ----------------------
20 Drivers which are built-in to the kernel should have the firmware integrated
22 a race is possible with loading the driver and the real rootfs not yet being
28 remote-proc subsystem. For such cases using a userspace fallback mechanism
30 when the real rootfs is ready and mounted.
/Documentation/admin-guide/
Dinitrd.rst15 where the kernel comes up with a minimum set of compiled-in drivers, and
23 ---------
38 6) init mounts the "real" root file system
51 Boot command-line options
52 -------------------------
70 Note: /dev/initrd is read-only and it can only be used once. As soon
80 ----------------------
88 find . | cpio --quiet -H newc -o | gzip -9 -n > /boot/imagefile.img
94 gzip -cd /boot/imagefile.img | cpio -imd --quiet
97 ------------
[all …]
/Documentation/devicetree/bindings/power/reset/
Datmel,at91sam9260-shdwc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/atmel,at91sam9260-shdwc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Claudiu Beznea <claudiu.beznea@microchip.com>
14 and VDDCORE and the wake-up detection on debounced input lines.
19 - atmel,at91sam9260-shdwc
20 - atmel,at91sam9rl-shdwc
21 - atmel,at91sam9x5-shdwc
29 atmel,wakeup-mode:
[all …]
/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.
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``
102 midi 0: [Emu8000 Port-0] ALSA port 65:0
[all …]
/Documentation/hwmon/
Dltc4260.rst10 Addresses scanned: -
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
27 -----------
37 $ echo ltc4260 0x10 > /sys/bus/i2c/devices/i2c-1/new_device
41 -------------
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/
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 …]
/Documentation/admin-guide/device-mapper/
Dsnapshot.rst2 Device-mapper snapshot support
5 Device-mapper allows you, without massive data copying:
7 - To create snapshots of any block device i.e. mountable, saved states of
10 - To create device "forks", i.e. multiple different versions of the
12 - To merge a snapshot of a block device back into the snapshot's origin
16 changed and uses a separate copy-on-write (COW) block device for
24 snapshot, snapshot-origin, and snapshot-merge.
26 - snapshot-origin <origin>
34 - snapshot <origin> <COW device> <persistent?> <chunksize>
45 <persistent?> is P (Persistent) or N (Not persistent - will not survive
[all …]

12345678910>>...19