| /kernel/linux/linux-6.6/arch/x86/platform/efi/ |
| D | memmap.c | 1 // SPDX-License-Identifier: GPL-2.0
49 * efi_memmap_alloc - Allocate memory for the EFI memory map
62 WARN_ON(data->phys_map || data->size); in efi_memmap_alloc()
64 data->size = num_entries * efi.memmap.desc_size; in efi_memmap_alloc()
65 data->desc_version = efi.memmap.desc_version; in efi_memmap_alloc()
66 data->desc_size = efi.memmap.desc_size; in efi_memmap_alloc()
67 data->flags &= ~(EFI_MEMMAP_SLAB | EFI_MEMMAP_MEMBLOCK); in efi_memmap_alloc()
68 data->flags |= efi.memmap.flags & EFI_MEMMAP_LATE; in efi_memmap_alloc()
71 data->flags |= EFI_MEMMAP_SLAB; in efi_memmap_alloc()
72 data->phys_map = __efi_memmap_alloc_late(data->size); in efi_memmap_alloc()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pwm/ |
| D | microchip,corepwm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Conor Dooley <conor.dooley@microchip.com>
16 https://www.microsemi.com/existing-parts/parts/152118
19 - $ref: pwm.yaml#
24 - const: microchip,corepwm-rtl-v4
32 "#pwm-cells":
37 microchip,sync-update-mask:
48 Each bit of "microchip,sync-update-mask" corresponds to a PWM channel & represents
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/ |
| D | reg-file-data-sampling.rst | 6 only affects Intel Atom parts(also branded as E-cores). RFDS may allow
9 ability to choose which data is inferred. CVE-2023-28746 is assigned to RFDS.
32 As an exception to this table, Intel Xeon E family parts ALDERLAKE(06_97H) and
37 affected and unaffected parts, but it is deemed not worth adding complexity as
38 the reporting is fixed automatically when these parts enumerate RFDS_NO.
51 -----------------
54 at C-state transitions.
57 ----------------------------------
58 Newer processors and microcode update on existing affected processors added new
62 - Bit 27 - RFDS_NO - When set, processor is not affected by RFDS.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | reg-file-data-sampling.rst | 6 only affects Intel Atom parts(also branded as E-cores). RFDS may allow
9 ability to choose which data is inferred. CVE-2023-28746 is assigned to RFDS.
32 As an exception to this table, Intel Xeon E family parts ALDERLAKE(06_97H) and
37 affected and unaffected parts, but it is deemed not worth adding complexity as
38 the reporting is fixed automatically when these parts enumerate RFDS_NO.
51 -----------------
54 at C-state transitions.
57 ----------------------------------
58 Newer processors and microcode update on existing affected processors added new
62 - Bit 27 - RFDS_NO - When set, processor is not affected by RFDS.
[all …]
|
| /kernel/linux/linux-6.6/drivers/staging/wlan-ng/ |
| D | TODO | 1 To-do list:
4 at https://www.kernel.org/doc/html/latest/process/coding-style.html.
8 * Use in-kernel API and remove unnecessary wrappers where possible.
10 * Remove the HAL layer and migrate its functionality into the relevant parts of
16 existing kernel APIs.
|
| /kernel/linux/linux-6.6/drivers/staging/rtl8192u/ |
| D | TODO | 1 To-do list:
4 at https://www.kernel.org/doc/html/latest/process/coding-style.html.
8 * Use in-kernel API and remove unnecessary wrappers where possible.
10 * Remove the HAL layer and migrate its functionality into the relevant parts of
16 existing kernel APIs.
|
| /kernel/linux/linux-6.6/drivers/staging/rtl8192e/ |
| D | TODO | 1 To-do list:
6 at https://www.kernel.org/doc/html/latest/process/coding-style.html.
10 * Use in-kernel API and remove unnecessary wrappers where possible.
12 * Remove the HAL layer and migrate its functionality into the relevant parts of
18 existing kernel APIs.
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/ |
| D | memmap.c | 1 // SPDX-License-Identifier: GPL-2.0
55 * efi_memmap_alloc - Allocate memory for the EFI memory map
69 WARN_ON(data->phys_map || data->size); in efi_memmap_alloc()
71 data->size = num_entries * efi.memmap.desc_size; in efi_memmap_alloc()
72 data->desc_version = efi.memmap.desc_version; in efi_memmap_alloc()
73 data->desc_size = efi.memmap.desc_size; in efi_memmap_alloc()
74 data->flags &= ~(EFI_MEMMAP_SLAB | EFI_MEMMAP_MEMBLOCK); in efi_memmap_alloc()
75 data->flags |= efi.memmap.flags & EFI_MEMMAP_LATE; in efi_memmap_alloc()
78 data->flags |= EFI_MEMMAP_SLAB; in efi_memmap_alloc()
79 data->phys_map = __efi_memmap_alloc_late(data->size); in efi_memmap_alloc()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/ |
| D | unshare.rst | 10 ----------
14 --------
26 -----------
37 outside the confinement of all-or-nothing shared resources of legacy
45 Al Viro in the August of 2000, on the Linux-Kernel mailing list, as part
53 -----------
59 even non-threaded applications if they have a need to disassociate
60 from default shared namespace. The following lists two use-cases
63 2.1 Per-security context namespaces
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/ |
| D | unshare.rst | 10 ----------
14 --------
26 -----------
37 outside the confinement of all-or-nothing shared resources of legacy
45 Al Viro in the August of 2000, on the Linux-Kernel mailing list, as part
53 -----------
59 even non-threaded applications if they have a need to disassociate
60 from default shared namespace. The following lists two use-cases
63 2.1 Per-security context namespaces
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
31 the no-MMU case doesn't support these, behaviour is identical to
39 In the no-MMU case:
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
50 - If the backing device can't or won't permit direct sharing,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
31 the no-MMU case doesn't support these, behaviour is identical to
39 In the no-MMU case:
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
50 - If the backing device can't or won't permit direct sharing,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | dma.rst | 12 though they still must provide DMA-ready buffers (see
13 :doc:`/core-api/dma-api-howto`). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
21 - URBs have an additional "transfer_dma" field, as well as a transfer_flags
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
29 - There's a new "generic DMA API", parts of which are usable by USB device
37 and effects like cache-trashing can impose subtle penalties.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/usb/ |
| D | dma.rst | 12 though they still must provide DMA-ready buffers (see
13 Documentation/core-api/dma-api-howto.rst). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
21 - URBs have an additional "transfer_dma" field, as well as a transfer_flags
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
29 - There's a new "generic DMA API", parts of which are usable by USB device
37 and effects like cache-trashing can impose subtle penalties.
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/sfc/siena/ |
| D | efx.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2005-2006 Fen Systems Ltd.
5 * Copyright 2006-2013 Solarflare Communications Inc.
23 return INDIRECT_CALL_1(tx_queue->efx->type->tx_enqueue, in efx_enqueue_skb()
35 if (channel->rx_pkt_n_frags) in efx_rx_flush_packet()
39 /* Maximum number of TCP segments we support for soft-TSO */
57 return efx->rss_spread > 1; in efx_rss_enabled()
63 * efx_filter_insert_filter - add or replace a filter
67 * existing filter with equal priority
72 * If existing filters have equal match values to the new filter spec,
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/sfc/ |
| D | efx.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2005-2006 Fen Systems Ltd.
5 * Copyright 2006-2013 Solarflare Communications Inc.
28 return INDIRECT_CALL_2(tx_queue->efx->type->tx_enqueue, in efx_enqueue_skb()
41 if (channel->rx_pkt_n_frags) in efx_rx_flush_packet()
42 INDIRECT_CALL_2(channel->efx->type->rx_packet, in efx_rx_flush_packet()
48 if (efx->type->rx_buf_hash_valid) in efx_rx_buf_hash_valid()
49 return INDIRECT_CALL_1(efx->type->rx_buf_hash_valid, in efx_rx_buf_hash_valid()
55 /* Maximum number of TCP segments we support for soft-TSO */
73 return efx->rss_spread > 1; in efx_rss_enabled()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/sfc/ |
| D | efx.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2005-2006 Fen Systems Ltd.
5 * Copyright 2006-2013 Solarflare Communications Inc.
27 return INDIRECT_CALL_2(tx_queue->efx->type->tx_enqueue, in efx_enqueue_skb()
43 if (channel->rx_pkt_n_frags) in efx_rx_flush_packet()
44 INDIRECT_CALL_2(channel->efx->type->rx_packet, in efx_rx_flush_packet()
50 if (efx->type->rx_buf_hash_valid) in efx_rx_buf_hash_valid()
51 return INDIRECT_CALL_1(efx->type->rx_buf_hash_valid, in efx_rx_buf_hash_valid()
57 /* Maximum number of TCP segments we support for soft-TSO */
75 return efx->rss_spread > 1; in efx_rss_enabled()
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ |
| D | drm_aperture.c | 1 // SPDX-License-Identifier: MIT
15 * graphics drivers, such as EFI-GOP or VESA, early during the boot process.
17 * hardware-specific driver. To take over the device the dedicated driver
19 * ownership of DRM framebuffer memory and hand-over between drivers.
27 * .. code-block:: c
75 * .. code-block:: c
83 * return -EINVAL;
84 * base = mem->start;
119 * devm_aperture_acquire_from_firmware - Acquires ownership of a firmware framebuffer
133 * The function fails if the framebuffer range, or parts of it, is currently
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/sfc/falcon/ |
| D | efx.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2005-2006 Fen Systems Ltd.
5 * Copyright 2006-2013 Solarflare Communications Inc.
51 if (channel->rx_pkt_n_frags) in ef4_rx_flush_packet()
63 /* Maximum number of TCP segments we support for soft-TSO */
75 return efx->rss_spread > 1; in ef4_rss_enabled()
83 * ef4_filter_insert_filter - add or replace a filter
87 * existing filter with equal priority
92 * If existing filters have equal match values to the new filter spec,
96 * 1. If the existing filters have lower priority, or @replace_equal
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/sfc/falcon/ |
| D | efx.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Copyright 2005-2006 Fen Systems Ltd.
5 * Copyright 2006-2013 Solarflare Communications Inc.
51 if (channel->rx_pkt_n_frags) in ef4_rx_flush_packet()
63 /* Maximum number of TCP segments we support for soft-TSO */
75 return efx->rss_spread > 1; in ef4_rss_enabled()
83 * ef4_filter_insert_filter - add or replace a filter
87 * existing filter with equal priority
92 * If existing filters have equal match values to the new filter spec,
96 * 1. If the existing filters have lower priority, or @replace_equal
[all …]
|
| /kernel/linux/linux-6.6/Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 54 * Remove in-order completion assumptions from DRM scheduler
75 * -1k to -1 Low priority
84 ----------------
86 * https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priori…
87 * https://spec.oneapi.com/level-zero/latest/core/api.html#ze-command-queue-priority-t
91 The existing bonding uAPI is completely broken with GuC submission because
102 The new parallel submission uAPI consists of 3 parts:
110 ------------------------------
112 (e.g. split-frame on gen11+). The logical mapping of engine instances can change
114 logical mapping with the existing query engine info IOCTL. Also the GuC
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
60 * Double-channel
63 dimms, accessed at the same time. E. g. if the DIMM is 64 bits-wide (72
67 * Chip-select row
70 accessed. Common chip-select rows for single channel are 64 bits, for
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/eeprom/ |
| D | at25.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
10 - Christian Eggers <ceggers@arri.de>
14 pattern: "^eeprom@[0-9a-f]{1,2}$"
18 # 'vendor' and 'model' parts of the first are the actual chip and the second
19 # item is fixed to "atmel,at25". Some existing bindings only have the
24 - items:
25 - enum:
26 - anvo,anv32e61w
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/tests/attr/ |
| D | README | 12 The attr tests consist of following parts:
15 ------------
18 defined. It must contain name of existing directory with access
26 -------------
31 -----------
35 perf record kill (test-record-basic)
36 perf record -b kill (test-record-branch-any)
37 perf record -j any kill (test-record-branch-filter-any)
38 perf record -j any_call kill (test-record-branch-filter-any_call)
39 perf record -j any_ret kill (test-record-branch-filter-any_ret)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/eeprom/ |
| D | at25.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christian Eggers <ceggers@arri.de>
15 - pattern: "^eeprom@[0-9a-f]{1,2}$"
16 - pattern: "^fram@[0-9a-f]{1,2}$"
20 # 'vendor' and 'model' parts of the first are the actual chip and the second
21 # item is fixed to "atmel,at25". Some existing bindings only have the
26 - items:
27 - enum:
[all …]
|