Home
last modified time | relevance | path

Searched +full:pre +full:- +full:stored (Results 1 – 25 of 791) sorted by relevance

12345678910>>...32

/kernel/linux/linux-6.6/Documentation/netlink/specs/
Ddevlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 -
12 name: sb-pool-type
14 -
16 -
19 attribute-sets:
20 -
22 name-prefix: devlink-attr-
24 -
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt1 tdc - Adding plugins for tdc
3 Author: Brenda J. Butler - bjb@mojatatu.com
6 --------------
9 There are some examples in plugin-lib.
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
17 - ability to alter the command to be run in any phase:
18 pre (the pre-suite stage)
23 post (the post-suite stage)
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt1 tdc - Adding plugins for tdc
3 Author: Brenda J. Butler - bjb@mojatatu.com
6 --------------
9 There are some examples in plugin-lib.
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
17 - ability to alter the command to be run in any phase:
18 pre (the pre-suite stage)
23 post (the post-suite stage)
[all …]
/kernel/linux/linux-5.10/Documentation/networking/
Dframerelay.rst1 .. SPDX-License-Identifier: GPL-2.0
13 Each DLCI is a point-to-point link between your machine and a remote one.
15 net-tools archives is 'dlcicfg'. This program will communicate with the
21 of which are stored in the FRAD's private data area. assoc/deassoc,
31 Configuration of the FRAD makes use of another net-tools program, 'fradcfg'.
41 the net-tools distribution. They can be found at ftp.invlogic.com, in
43 use 'cd linux'. v0.10 is for use on pre-2.0.3 and earlier, v0.15 is for
44 pre-2.0.4 and later.
/kernel/linux/linux-6.6/kernel/trace/
Dtracing_map.h1 // SPDX-License-Identifier: GPL-2.0
21 * aren't discussed here - this is just a general overview of the data
25 * zeroed array of struct tracing_map_entry (stored in the map field
27 * structure containing only two fields: a 32-bit unsigned 'key'
32 * this indirectly via an array of tracing_map_sort_entry - see the
34 * sorting-related data structures below).
38 * arbitrarily-sized key passed into it into a 32-bit unsigned key.
44 * the new 32-bit hashed key. Once claimed, that tracing_map_entry's
46 * forever associated with that 32-bit hashed key in the
53 * 32-bit hashed key it's associated with. Things such as the unique
[all …]
/kernel/linux/linux-6.6/drivers/gpu/drm/
Ddrm_blend.c43 * sub-pixel accuracy, which is scaled up to a pixel-aligned destination
45 * defined by the horizontal and vertical visible pixels (stored in @hdisplay
46 * and @vdisplay) of the requested mode (stored in &drm_crtc_state.mode). These
47 * two rectangles are both stored in the &drm_plane_state.
96 * plane-wide opacity, from transparent (0) to opaque (0xffff). It can be
99 * pre-multiplied by the global alpha associated to the plane.
109 * "rotate-<degrees>":
113 * "reflect-<axis>":
117 * reflect-x::
120 * | | -> | |
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_blend.c43 * sub-pixel accuracy, which is scaled up to a pixel-aligned destination
45 * defined by the horizontal and vertical visible pixels (stored in @hdisplay
46 * and @vdisplay) of the requested mode (stored in &drm_crtc_state.mode). These
47 * two rectangles are both stored in the &drm_plane_state.
96 * plane-wide opacity, from transparent (0) to opaque (0xffff). It can be
99 * pre-multiplied by the global alpha associated to the plane.
109 * "rotate-<degrees>":
113 * "reflect-<axis>":
117 * reflect-x::
120 * | | -> | |
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/thermal/
Dexynos_thermal.rst15 ---------------------------
19 The chip only exposes the measured 8-bit temperature code value
27 Tc = (T - 25) * (TI2 - TI1) / (85 - 25) + TI1
31 Tc = T + TI1 - 25
40 Trimming info for 25 degree Celsius (stored at TRIMINFO register)
43 Trimming info for 85 degree Celsius (stored at TRIMINFO register)
47 when temperature exceeds pre-defined levels.
65 -----------------------
74 TMU configuration data -----> TMU Driver <----> Exynos Core thermal wrapper
/kernel/linux/linux-6.6/Documentation/driver-api/thermal/
Dexynos_thermal.rst15 ---------------------------
19 The chip only exposes the measured 8-bit temperature code value
27 Tc = (T - 25) * (TI2 - TI1) / (85 - 25) + TI1
31 Tc = T + TI1 - 25
40 Trimming info for 25 degree Celsius (stored at TRIMINFO register)
43 Trimming info for 85 degree Celsius (stored at TRIMINFO register)
47 when temperature exceeds pre-defined levels.
65 -----------------------
74 TMU configuration data -----> TMU Driver <----> Exynos Core thermal wrapper
/kernel/linux/linux-5.10/kernel/trace/
Dtracing_map.h1 // SPDX-License-Identifier: GPL-2.0
21 * aren't discussed here - this is just a general overview of the data
25 * zeroed array of struct tracing_map_entry (stored in the map field
27 * structure containing only two fields: a 32-bit unsigned 'key'
32 * this indirectly via an array of tracing_map_sort_entry - see the
34 * sorting-related data structures below).
38 * arbitrarily-sized key passed into it into a 32-bit unsigned key.
44 * the new 32-bit hashed key. Once claimed, that tracing_map_entry's
46 * forever associated with that 32-bit hashed key in the
53 * 32-bit hashed key it's assocated with. Things such as the unique
[all …]
/kernel/linux/linux-5.10/drivers/s390/scsi/
Dzfcp_dbf.h1 /* SPDX-License-Identifier: GPL-2.0 */
28 * struct zfcp_dbf_rec_trigger - trace record for triggered recovery action
42 * struct zfcp_dbf_rec_running - trace record for running recovery
58 * enum zfcp_dbf_rec_id - recovery trace record id
68 * struct zfcp_dbf_rec - trace record for error recovery actions
97 * enum zfcp_dbf_san_id - SAN trace record identifier
108 /** struct zfcp_dbf_san - trace record for SAN requests and responses
126 * struct zfcp_dbf_hba_res - trace record for hba responses
146 * struct zfcp_dbf_hba_uss - trace record for unsolicited status
162 * struct zfcp_dbf_hba_fces - trace record for FC Endpoint Security
[all …]
/kernel/linux/linux-6.6/drivers/s390/scsi/
Dzfcp_dbf.h1 /* SPDX-License-Identifier: GPL-2.0 */
28 * struct zfcp_dbf_rec_trigger - trace record for triggered recovery action
42 * struct zfcp_dbf_rec_running - trace record for running recovery
58 * enum zfcp_dbf_rec_id - recovery trace record id
68 * struct zfcp_dbf_rec - trace record for error recovery actions
97 * enum zfcp_dbf_san_id - SAN trace record identifier
108 /** struct zfcp_dbf_san - trace record for SAN requests and responses
126 * struct zfcp_dbf_hba_res - trace record for hba responses
146 * struct zfcp_dbf_hba_uss - trace record for unsolicited status
162 * struct zfcp_dbf_hba_fces - trace record for FC Endpoint Security
[all …]
/kernel/linux/linux-5.10/Documentation/vm/
Dfrontswap.rst9 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
11 (Note, frontswap -- and :ref:`cleancache` (merged at 3.0) -- are the "frontends"
13 all other supporting code -- the "backends" -- is implemented as drivers.
21 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
23 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
24 this pseudo-RAM device is not directly accessible or addressable by the
25 kernel and is of unknown and possibly time-varying size. The driver
40 Once a page is successfully stored, a matching load on the page will normally
50 in swap device writes is lost (and also a non-trivial performance advantage)
54 Note that if a page is stored and the page already exists in transcendent memory
[all …]
/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-class-backlight8 - FB_BLANK_UNBLANK (0) : power on.
9 - FB_BLANK_POWERDOWN (4) : power off
19 show the brightness level stored in the driver, which
46 "platform": The driver uses a platform-specific interface
56 holdover from pre-standardisation of firmware
/kernel/linux/linux-6.6/Documentation/ABI/stable/
Dsysfs-class-backlight8 - FB_BLANK_UNBLANK (0) : power on.
9 - FB_BLANK_POWERDOWN (4) : power off
19 show the brightness level stored in the driver, which
46 "platform": The driver uses a platform-specific interface
56 holdover from pre-standardisation of firmware
/kernel/linux/linux-5.10/tools/memory-model/Documentation/
Dexplanation.txt1 Explanation of the Linux-Kernel Memory Consistency Model
15 7. THE PROGRAM ORDER RELATION: po AND po-loc
18 10. THE READS-FROM RELATION: rf, rfi, and rfe
20 12. THE FROM-READS RELATION: fr, fri, and fre
22 14. PROPAGATION ORDER RELATION: cumul-fence
28 20. THE HAPPENS-BEFORE RELATION: hb
29 21. THE PROPAGATES-BEFORE RELATION: pb
30 22. RCU RELATIONS: rcu-link, rcu-gp, rcu-rscsi, rcu-order, rcu-fence, and rb
38 ------------
40 The Linux-kernel memory consistency model (LKMM) is rather complex and
[all …]
/kernel/linux/linux-6.6/Documentation/userspace-api/media/dvb/
Dfrontend-stat-properties.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _frontend-stat-properties:
27 The number of filled elements are stored at ``dtv_property.stat.len``.
32 - ``svalue`` or ``uvalue``, where ``svalue`` is for signed values of
36 - ``scale`` - Scale for the value. It can be:
38 - ``FE_SCALE_NOT_AVAILABLE`` - The parameter is supported by the
42 - ``FE_SCALE_DECIBEL`` - parameter is a signed value, measured in
45 - ``FE_SCALE_RELATIVE`` - parameter is a unsigned value, where 0
48 - ``FE_SCALE_COUNTER`` - parameter is a unsigned value that counts
53 .. _DTV-STAT-SIGNAL-STRENGTH:
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/
Dfrontend-stat-properties.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _frontend-stat-properties:
27 The number of filled elements are stored at ``dtv_property.stat.len``.
32 - ``svalue`` or ``uvalue``, where ``svalue`` is for signed values of
36 - ``scale`` - Scale for the value. It can be:
38 - ``FE_SCALE_NOT_AVAILABLE`` - The parameter is supported by the
42 - ``FE_SCALE_DECIBEL`` - parameter is a signed value, measured in
45 - ``FE_SCALE_RELATIVE`` - parameter is a unsigned value, where 0
48 - ``FE_SCALE_COUNTER`` - parameter is a unsigned value that counts
53 .. _DTV-STAT-SIGNAL-STRENGTH:
[all …]
/kernel/linux/linux-5.10/arch/um/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 menu "UML-specific options"
98 While the User-Mode Linux port uses its own root file system for
100 access files stored on the host. It does not require any
104 mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
111 <http://user-mode-linux.sourceforge.net/hostfs.html>.
113 If you'd like to be able to work with files stored on the host,
121 The user mode linux management console is a low-level interface to
123 a full-blown operating system running under every user mode linux
129 2.4.5-9um and later (path /tools/mconsole), and is also in the
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/display/
Dintel_vbt_defs.h2 * Copyright © 2006-2016 Intel Corporation
43 * struct vbt_header - VBT Header structure
51 * @aim_offset: Offsets of add-in data blocks from beginning of VBT
65 * struct bdb_header - BDB Header structure
123 * Block 1 - General Bit Definitions
168 * Block 2 - General Bytes Definition
171 /* pre-915 */
177 /* Pre 915 */
275 /* dvo_port pre BDB 155 */
354 * When we copy the child device configs to dev_priv->vbt.child_dev, we reserve
[all …]
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/modes/interface/
Disp_types.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 Copyright (c) 2010 - 2015, Intel Corporation.
25 * The bit depth of each pixel element is stored in the global variable
67 /* pre-gdc output frame (gdc input) */
/kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/isp/modes/interface/
Disp_types.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 * Copyright (c) 2010 - 2015, Intel Corporation.
28 * The bit depth of each pixel element is stored in the global variable
72 /* pre-gdc output frame (gdc input) */
/kernel/linux/linux-6.6/tools/memory-model/Documentation/
Dexplanation.txt1 Explanation of the Linux-Kernel Memory Consistency Model
15 7. THE PROGRAM ORDER RELATION: po AND po-loc
18 10. THE READS-FROM RELATION: rf, rfi, and rfe
20 12. THE FROM-READS RELATION: fr, fri, and fre
22 14. PROPAGATION ORDER RELATION: cumul-fence
28 20. THE HAPPENS-BEFORE RELATION: hb
29 21. THE PROPAGATES-BEFORE RELATION: pb
30 22. RCU RELATIONS: rcu-link, rcu-gp, rcu-rscsi, rcu-order, rcu-fence, and rb
31 23. SRCU READ-SIDE CRITICAL SECTIONS
39 ------------
[all …]
/kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/runtime/binary/interface/
Dia_css_binary.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 Copyright (c) 2010 - 2015, Intel Corporation.
28 /* The binary mode is used in pre-processor expressions so we cannot
102 struct ia_css_frame_info *in_info; /* the info of the input-frame with the
183 * The shading information necessary as API is stored in the shading_info.
187 * The shading information related to ISP (but, not necessary as API) is stored in the pipe_config.
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/runtime/binary/interface/
Dia_css_binary.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 Copyright (c) 2010 - 2015, Intel Corporation.
28 /* The binary mode is used in pre-processor expressions so we cannot
103 struct ia_css_frame_info *in_info; /* the info of the input-frame with the
186 * The shading information necessary as API is stored in the shading_info.
190 * The shading information related to ISP (but, not necessary as API) is stored in the pipe_config.

12345678910>>...32