| /linux-6.14.4/tools/perf/pmu-events/arch/x86/broadwell/ |
| D | uncore-cache.json | 3 … "BriefDescription": "L3 Lookup any request that access cache and found line in E or S-state",
8 … "PublicDescription": "L3 Lookup any request that access cache and found line in E or S-state.",
13 "BriefDescription": "L3 Lookup any request that access cache and found line in I-state",
18 "PublicDescription": "L3 Lookup any request that access cache and found line in I-state.",
23 "BriefDescription": "L3 Lookup any request that access cache and found line in M-state",
28 "PublicDescription": "L3 Lookup any request that access cache and found line in M-state.",
33 "BriefDescription": "L3 Lookup any request that access cache and found line in MESI-state",
38 … "PublicDescription": "L3 Lookup any request that access cache and found line in MESI-state.",
43 … "BriefDescription": "L3 Lookup read request that access cache and found line in E or S-state",
48 … "PublicDescription": "L3 Lookup read request that access cache and found line in E or S-state.",
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/skylake/ |
| D | uncore-cache.json | 3 … "BriefDescription": "L3 Lookup any request that access cache and found line in E or S-state",
8 … "PublicDescription": "L3 Lookup any request that access cache and found line in E or S-state.",
13 "BriefDescription": "L3 Lookup any request that access cache and found line in I-state",
18 "PublicDescription": "L3 Lookup any request that access cache and found line in I-state.",
23 "BriefDescription": "L3 Lookup any request that access cache and found line in M-state",
28 "PublicDescription": "L3 Lookup any request that access cache and found line in M-state.",
33 "BriefDescription": "L3 Lookup any request that access cache and found line in MESI-state",
38 … "PublicDescription": "L3 Lookup any request that access cache and found line in MESI-state.",
43 … "BriefDescription": "L3 Lookup read request that access cache and found line in E or S-state",
48 … "PublicDescription": "L3 Lookup read request that access cache and found line in E or S-state.",
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/sandybridge/ |
| D | uncore-cache.json | 3 … "BriefDescription": "L3 Lookup any request that access cache and found line in E or S-state.",
12 "BriefDescription": "L3 Lookup any request that access cache and found line in I-state.",
21 "BriefDescription": "L3 Lookup any request that access cache and found line in M-state.",
30 "BriefDescription": "L3 Lookup any request that access cache and found line in MESI-state.",
39 …Description": "L3 Lookup external snoop request that access cache and found line in E or S-state.",
48 …BriefDescription": "L3 Lookup external snoop request that access cache and found line in I-state.",
57 …BriefDescription": "L3 Lookup external snoop request that access cache and found line in M-state.",
66 …efDescription": "L3 Lookup external snoop request that access cache and found line in MESI-state.",
75 … "BriefDescription": "L3 Lookup read request that access cache and found line in E or S-state.",
84 "BriefDescription": "L3 Lookup read request that access cache and found line in I-state.",
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | uncore-cache.json | 3 … "BriefDescription": "L3 Lookup any request that access cache and found line in E or S-state.",
12 "BriefDescription": "L3 Lookup any request that access cache and found line in I-state.",
21 "BriefDescription": "L3 Lookup any request that access cache and found line in M-state.",
30 "BriefDescription": "L3 Lookup any request that access cache and found line in MESI-state.",
39 …Description": "L3 Lookup external snoop request that access cache and found line in E or S-state.",
48 …BriefDescription": "L3 Lookup external snoop request that access cache and found line in I-state.",
57 …BriefDescription": "L3 Lookup external snoop request that access cache and found line in M-state.",
66 …efDescription": "L3 Lookup external snoop request that access cache and found line in MESI-state.",
75 … "BriefDescription": "L3 Lookup read request that access cache and found line in E or S-state.",
84 "BriefDescription": "L3 Lookup read request that access cache and found line in I-state.",
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/haswell/ |
| D | uncore-cache.json | 3 … "BriefDescription": "L3 Lookup any request that access cache and found line in E or S-state.",
12 "BriefDescription": "L3 Lookup any request that access cache and found line in I-state.",
21 "BriefDescription": "L3 Lookup any request that access cache and found line in M-state.",
30 "BriefDescription": "L3 Lookup any request that access cache and found line in MESI-state.",
39 …Description": "L3 Lookup external snoop request that access cache and found line in E or S-state.",
48 …BriefDescription": "L3 Lookup external snoop request that access cache and found line in I-state.",
57 …BriefDescription": "L3 Lookup external snoop request that access cache and found line in M-state.",
66 …efDescription": "L3 Lookup external snoop request that access cache and found line in MESI-state.",
75 … "BriefDescription": "L3 Lookup read request that access cache and found line in E or S-state.",
84 "BriefDescription": "L3 Lookup read request that access cache and found line in I-state.",
[all …]
|
| /linux-6.14.4/drivers/gpu/drm/nouveau/nvkm/subdev/gpio/ |
| D | nv10.c | 7 * "Software"), to deal in the Software without restriction, including
14 * next paragraph) shall be included in all copies or substantial
20 * IN NO EVENT SHALL THE COPYRIGHT OWNER(S) AND/OR ITS SUPPLIERS BE
21 * LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
22 * OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
23 * WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
29 nv10_gpio_sense(struct nvkm_gpio *gpio, int line) in nv10_gpio_sense() argument
31 struct nvkm_device *device = gpio->subdev.device; in nv10_gpio_sense()
32 if (line < 2) { in nv10_gpio_sense()
33 line = line * 16; in nv10_gpio_sense()
[all …]
|
| /linux-6.14.4/Documentation/userspace-api/gpio/ |
| D | gpio-v2-get-line-ioctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_GET_LINE_IOCTL - Request a line or lines from the kernel.
34 On success, the requesting process is granted exclusive access to the line
35 value, write access to the line configuration, and may receive events when
36 edges are detected on the line, all of which are described in more detail in
37 :ref:`gpio-v2-line-request`.
39 A number of lines may be requested in the one line request, and request
41 as possible. e.g. gpio-v2-line-get-values-ioctl.rst will read all the
44 The state of a line, including the value of output lines, is guaranteed to
46 file descriptor is closed, the state of the line becomes uncontrolled from
[all …]
|
| D | chardev_v1.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 in the future. The v2 API is a functional superset of the v1 API so any
18 First added in 4.8.
20 The API is based around three major objects, the :ref:`gpio-v1-chip`, the
21 :ref:`gpio-v1-line-handle`, and the :ref:`gpio-v1-line-event`.
23 Where "line event" is used in this document it refers to the request that can
24 monitor a line for edge events, not the edge events themselves.
26 .. _gpio-v1-chip:
36 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
38 Lines are requested from the chip using either gpio-get-linehandle-ioctl.rst
[all …]
|
| D | chardev.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 This is latest version (v2) of the character device API, as defined in
10 First added in 5.10.
18 Read Documentation/driver-api/gpio/drivers-on-gpio.rst to avoid reinventing
19 kernel wheels in userspace.
21 Similarly, for multi-function lines there may be other subsystems, such as
23 Documentation/driver-api/pwm.rst, Documentation/w1/index.rst etc, that
26 Basic examples using the character device API can be found in ``tools/gpio/*``.
28 The API is based around two major objects, the :ref:`gpio-v2-chip` and the
29 :ref:`gpio-v2-line-request`.
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | frontend.json | 39 …"BriefDescription": "References per ICache line. This event counts differently than Intel processo…
43 …in an ICache Line. The event strives to count on a cache line basis, so that multiple fetches to …
48 …"BriefDescription": "References per ICache line that are available in the ICache (hit). This event…
52 …in an ICache Line and that cache line is in the ICache (hit). The event strives to count on a cac…
57 …"BriefDescription": "References per ICache line that are not available in the ICache (miss). This …
61 …in an ICache Line and that cache line is not in the ICache (miss). The event strives to count on …
70 … read from the MSROM. The most common case that this counts is when a micro-coded instruction is …
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | frontend.json | 39 …"BriefDescription": "References per ICache line. This event counts differently than Intel processo…
43 …in an ICache Line. The event strives to count on a cache line basis, so that multiple fetches to …
48 …"BriefDescription": "References per ICache line that are available in the ICache (hit). This event…
52 …in an ICache Line and that cache line is in the ICache (hit). The event strives to count on a cac…
57 …"BriefDescription": "References per ICache line that are not available in the ICache (miss). This …
61 …in an ICache Line and that cache line is not in the ICache (miss). The event strives to count on …
70 … read from the MSROM. The most common case that this counts is when a micro-coded instruction is …
|
| /linux-6.14.4/Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 9 debug-print code to obtain additional kernel information.
16 * a Catalog of all *prdbgs* in your kernel.
22 - source filename
23 - function name
24 - line number (including ranges of line numbers)
25 - module name
26 - format string
27 - class name (as known/declared by each module)
29 NOTE: To actually get the debug-print output on the console, you may
31 Read about these kernel parameters in
[all …]
|
| /linux-6.14.4/Documentation/userspace-api/media/v4l/ |
| D | dev-sliced-vbi.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 VBI stands for Vertical Blanking Interval, a gap in the sequence of
15 Sliced VBI devices use hardware to demodulate data transmitted in the
17 :ref:`raw VBI interface <raw-vbi>`. The data is passed as short
18 packets of fixed size, covering one scan line each. The number of
36 respectively, in the ``capabilities`` field of struct
51 .. _sliced-vbi-format-negotitation:
63 services it can identify on a given line are limited. For example on PAL
64 line 16 the hardware may be able to look for a VPS or Teletext signal,
81 hardware must be told which VBI service to expect on each scan line. Not
[all …]
|
| /linux-6.14.4/arch/um/drivers/ |
| D | chan_kern.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2000 - 2007 Jeff Dike (jdike@{linux.intel,addtoit}.com)
27 return -ENODEV; in not_configged_open()
40 return -EIO; in not_configged_read()
47 return -EIO; in not_configged_write()
54 return -EIO; in not_configged_console_write()
62 return -ENODEV; in not_configged_window_size()
94 if (chan->opened) in open_one_chan()
97 if (chan->ops->open == NULL) in open_one_chan()
99 else fd = (*chan->ops->open)(chan->input, chan->output, chan->primary, in open_one_chan()
[all …]
|
| /linux-6.14.4/include/uapi/linux/ |
| D | gpio.h | 1 /* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */
3 * <linux/gpio.h> - userspace ABI for the GPIO character devices
21 * Must be a multiple of 8 to ensure 32/64-bit alignment of structs.
26 * struct gpiochip_info - Information about a certain GPIO chip
41 * Must be no greater than 64, as bitmaps are restricted here to 64-bits
42 * for simplicity, and a multiple of 2 to ensure 32/64-bit alignment of
48 * The maximum number of configuration attributes associated with a line
54 * enum gpio_v2_line_flag - &struct gpio_v2_line_attribute.flags values
55 * @GPIO_V2_LINE_FLAG_USED: line is not available for request
56 * @GPIO_V2_LINE_FLAG_ACTIVE_LOW: line active state is physical low
[all …]
|
| /linux-6.14.4/scripts/ |
| D | show_delta | 2 # SPDX-License-Identifier: GPL-2.0-only
20 the kernel command line option "time" is specified. When run with no
22 each printk line and the next. When run with the '-b' option, all times
23 are relative to a single (base) point in time.
26 -h Show this usage help.
27 -b <base> Specify a base for time references.
29 If it is a string, the first message line
31 line) is used as the time reference.
34 $ show_delta -b NET4 timefile
36 will show times relative to the line in the kernel output
[all …]
|
| D | bpf_doc.py | 2 # SPDX-License-Identifier: GPL-2.0-only
4 # Copyright (C) 2018-2019 Netronome Systems, Inc.
7 # In case user attempts to run with Python 2.
24 def __init__(self, line='<line not provided>', reader=None): argument
27 'Error at file offset %d, parsing line: %s' %
28 (reader.tell(), line))
30 BaseException.__init__(self, 'Error parsing line: %s' % line)
74 for a in args:
92 An object used to parse a file in order to extract the documentation of a
94 stored as Helper object, in the self.helpers() array.
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ |
| D | l1d_cache.json | 4 …rations that missed in the level 1 data cache. This event only counts one event per cache line. Th…
8 …in the CPUs caches (near atomic operations) counts as both a write access and read access. Each ac…
12 …-backs of dirty data from the L1 data cache to the L2 cache. This occurs when either a dirty cache…
16 …"PublicDescription": "Counts cache line refills into the level 1 data cache from any memory read o…
20 …ache accesses from any load operation. Atomic load operations that resolve in the CPUs caches coun…
24 …ified by virtual address) instruction. Near atomic operations that resolve in the CPUs caches coun…
28 …where the memory read operation misses in the level 1 data cache. This event only counts one event…
32 …here the memory write operation misses in the level 1 data cache. This event only counts one event…
36 …"PublicDescription": "Counts level 1 data cache refills where the cache line data came from caches…
40 …ata cache refills for which the cache line data came from outside the immediate cluster of the cor…
[all …]
|
| /linux-6.14.4/tools/testing/kunit/ |
| D | kunit_parser.py | 1 # SPDX-License-Identifier: GPL-2.0
4 # results with reader-friendly format. Stores and returns test results in a
25 results within a test log are stored in a main Test object as
29 status : TestStatus - status of the test
30 name : str - name of the test
31 expected_count : int - expected number of subtests (0 if single
33 subtests : List[Test] - list of subtests
34 log : List[str] - log of KTAP lines that correspond to the test
35 counts : TestCounts - counts of the test statuses and errors of
39 def __init__(self) -> None:
[all …]
|
| /linux-6.14.4/Documentation/sphinx/ |
| D | maintainers_include.py | 2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8; mode: python -*-
7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
16 specific to the Linux kernel's standard "MAINTAINERS" file, in an
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
63 for line in open(path):
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/ |
| D | l1d_cache.json | 4 …rations that missed in the level 1 data cache. This event only counts one event per cache line. Th…
8 …in the CPUs caches (near atomic operations) counts as both a write access and read access. Each ac…
12 …-backs of dirty data from the L1 data cache to the L2 cache. This occurs when either a dirty cache…
16 …ache accesses from any load operation. Atomic load operations that resolve in the CPUs caches coun…
20 …ified by virtual address) instruction. Near atomic operations that resolve in the CPUs caches coun…
24 …where the memory read operation misses in the level 1 data cache. This event only counts one event…
28 …here the memory write operation misses in the level 1 data cache. This event only counts one event…
32 …"PublicDescription": "Counts level 1 data cache refills where the cache line data came from caches…
36 …ata cache refills for which the cache line data came from outside the immediate cluster of the cor…
40 …"PublicDescription": "Counts dirty cache line evictions from the level 1 data cache caused by a ne…
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | l1d_cache.json | 4 …d load or store operations that missed in the level 1 data cache. This event only counts one event…
8 …in the CPUs caches (near atomic operations) counts as both a write access and read access. Each ac…
12 …-backs of dirty data from the L1 data cache to the L2 cache. This occurs when either a dirty cache…
16 …"PublicDescription": "Counts cache line refills into the level 1 data cache from any memory read o…
20 …ache accesses from any load operation. Atomic load operations that resolve in the CPUs caches coun…
24 …ified by virtual address) instruction. Near atomic operations that resolve in the CPUs caches coun…
28 …where the memory read operation misses in the level 1 data cache. This event only counts one event…
32 …here the memory write operation misses in the level 1 data cache. This event only counts one event…
36 …"PublicDescription": "Counts level 1 data cache refills where the cache line data came from caches…
40 …ata cache refills for which the cache line data came from outside the immediate cluster of the cor…
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/s390/cf_z13/ |
| D | extended.json | 3 "Unit": "CPU-M-CF",
6 "BriefDescription": "L1D Read-only Exclusive Writes",
7 …-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated…
10 "Unit": "CPU-M-CF",
14 …"PublicDescription": "A translation entry has been written to the Level-1 Data Translation Lookasi…
17 "Unit": "CPU-M-CF",
21 …"PublicDescription": "Level-1 Data TLB miss in progress. Incremented by one for every cycle a DTLB…
24 "Unit": "CPU-M-CF",
27 "BriefDescription": "DTLB1 One-Megabyte Page Writes",
28 …": "A translation entry has been written to the Level-1 Data Translation Lookaside Buffer for a on…
[all …]
|
| /linux-6.14.4/Documentation/driver-api/gpio/ |
| D | driver.rst | 18 line is not general purpose, it is not GPIO and should not be handled by a
19 GPIO chip. The use case is the indicative: certain lines in a system may be
21 of a general purpose I/O. On the other hand a LED driver line may be used as a
26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
31 use hardware offsets 0..31 for these, corresponding to bits 0..31 in the
35 line is never made visible outside of the driver.
37 On top of this internal number, each GPIO line also needs to have a global
38 number in the integer GPIO namespace so that it can be used with the legacy GPIO
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/s390/cf_z14/ |
| D | extended.json | 3 "Unit": "CPU-M-CF",
6 "BriefDescription": "L1D Read-only Exclusive Writes",
7 …-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated…
10 "Unit": "CPU-M-CF",
17 "Unit": "CPU-M-CF",
21 …": "A TLB2 miss is in progress for a request made by the data cache. Incremented by one for every …
24 "Unit": "CPU-M-CF",
27 "BriefDescription": "DTLB2 One-Megabyte Page Writes",
28 …ritten into the Combined Region and Segment Table Entry array in the Level-2 TLB for a one-megabyt…
31 "Unit": "CPU-M-CF",
[all …]
|