| /linux-6.8/Documentation/devicetree/bindings/nvmem/layouts/ |
| D | fixed-layout.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-layout.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM layout for fixed NVMEM cells
10 Many NVMEM devices have hardcoded cells layout (offset and size of defined
13 This binding allows defining such NVMEM layout with its cells. It can be used
17 - Rafał Miłecki <rafal@milecki.pl>
21 const: fixed-layout
23 "#address-cells":
[all …]
|
| D | nvmem-layout.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
11 - Michael Walle <michael@walle.cc>
12 - Miquel Raynal <miquel.raynal@bootlin.com>
18 perform their parsing. The nvmem-layout container is here to describe these.
21 - $ref: fixed-layout.yaml
22 - $ref: kontron,sl28-vpd.yaml
[all …]
|
| /linux-6.8/drivers/nvmem/ |
| D | layouts.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * NVMEM layout bus handling
10 #include <linux/dma-mapping.h>
11 #include <linux/nvmem-consumer.h>
12 #include <linux/nvmem-provider.h>
31 struct nvmem_layout_driver *drv = to_nvmem_layout_driver(dev->driver); in nvmem_layout_bus_probe()
32 struct nvmem_layout *layout = to_nvmem_layout_device(dev); in nvmem_layout_bus_probe() local
34 if (!drv->probe || !drv->remove) in nvmem_layout_bus_probe()
35 return -EINVAL; in nvmem_layout_bus_probe()
37 return drv->probe(layout); in nvmem_layout_bus_probe()
[all …]
|
| /linux-6.8/include/linux/ |
| D | nvmem-provider.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
36 #define NVMEM_DEVID_NONE (-1)
37 #define NVMEM_DEVID_AUTO (-2)
40 * struct nvmem_keepout - NVMEM register keepout range.
53 * struct nvmem_cell_info - NVMEM cell description
78 * struct nvmem_config - NVMEM device configuration
84 * @cells: Optional array of pre-defined NVMEM cells.
86 * @add_legacy_fixed_of_cells: Read fixed NVMEM cells from old OF syntax.
92 * @read_only: Device is read-only.
[all …]
|
| /linux-6.8/Documentation/arch/arm64/ |
| D | memory.rst | 2 Memory Layout on AArch64 Linux
7 This document describes the virtual memory layout used by the AArch64
12 with the 4KB page configuration, allowing 39-bit (512GB) or 48-bit
14 64KB pages, only 2 levels of translation tables, allowing 42-bit (4TB)
15 virtual address, are used but the memory layout is the same.
24 mappings while the user pgd contains only user (non-global) mappings.
29 AArch64 Linux memory layout with 4KB pages + 4 levels (48-bit)::
32 -----------------------------------------------------------------------
38 fffffbfff0000000 fffffbfffdffffff 224MB fixed mappings (top down)
46 AArch64 Linux memory layout with 64KB pages + 3 levels (52-bit with HW support)::
[all …]
|
| /linux-6.8/Documentation/devicetree/bindings/nvmem/ |
| D | nvmem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
23 "#address-cells":
26 "#size-cells":
29 read-only:
34 wp-gpios:
36 GPIO to which the write-protect pin of the chip is connected.
37 The write-protect GPIO is asserted, when it's driven high
[all …]
|
| D | nvmem-deprecated-cells.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/nvmem-deprecated-cells.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM old syntax for fixed cells
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
13 Before introducing NVMEM layouts all NVMEM (fixed) cells were defined
14 as direct device subnodes. That syntax was replaced by "fixed-layout"
18 "@[0-9a-f]+(,[0-7])?$":
21 - $ref: layouts/fixed-cell.yaml
[all …]
|
| /linux-6.8/Documentation/driver-api/ |
| D | ioctl.rst | 18 the ioctl system call. While this can be any 32-bit number that uniquely
22 ``include/uapi/asm-generic/ioctl.h`` provides four macros for defining
36 An 8-bit number, often a character literal, specific to a subsystem
37 or driver, and listed in Documentation/userspace-api/ioctl/ioctl-number.rst
40 An 8-bit number identifying the specific command, unique for a give
45 encodes the ``sizeof(data_type)`` value in a 13-bit or 14-bit integer,
74 handler returns either -ENOTTY or -ENOIOCTLCMD, which also results in
75 -ENOTTY being returned from the system call. Some subsystems return
76 -ENOSYS or -EINVAL here for historic reasons, but this is wrong.
79 -ENOIOCTLCMD in order to use the fallback conversion into native
[all …]
|
| /linux-6.8/drivers/gpu/drm/imagination/ |
| D | pvr_rogue_fwif_stream.h | 1 /* SPDX-License-Identifier: GPL-2.0-only OR MIT */
12 * A command stream has the following layout :
13 * - A 64-bit header containing:
16 * - The main stream data.
17 * - The extension stream (optional), which is composed of:
21 * The main stream provides the base command data. This has a fixed layout based on the features
51 * Stream extension header - Geometry 0
60 * Stream extension header - Fragment 0
70 * Stream extension header - Compute 0
|
| /linux-6.8/drivers/gpu/drm/nouveau/dispnv50/ |
| D | wndwc57e.c | 35 struct nvif_push *push = wndw->wndw.push; in wndwc57e_image_set()
42 NVVAL(NVC57E, SET_PRESENT_CONTROL, MIN_PRESENT_INTERVAL, asyw->image.interval) | in wndwc57e_image_set()
43 NVVAL(NVC57E, SET_PRESENT_CONTROL, BEGIN_MODE, asyw->image.mode) | in wndwc57e_image_set()
47 NVVAL(NVC57E, SET_SIZE, WIDTH, asyw->image.w) | in wndwc57e_image_set()
48 NVVAL(NVC57E, SET_SIZE, HEIGHT, asyw->image.h), in wndwc57e_image_set()
51 NVVAL(NVC57E, SET_STORAGE, BLOCK_HEIGHT, asyw->image.blockh) | in wndwc57e_image_set()
52 NVVAL(NVC57E, SET_STORAGE, MEMORY_LAYOUT, asyw->image.layout), in wndwc57e_image_set()
55 NVVAL(NVC57E, SET_PARAMS, FORMAT, asyw->image.format) | in wndwc57e_image_set()
61 NVVAL(NVC57E, SET_PLANAR_STORAGE, PITCH, asyw->image.blocks[0]) | in wndwc57e_image_set()
62 NVVAL(NVC57E, SET_PLANAR_STORAGE, PITCH, asyw->image.pitch[0] >> 6)); in wndwc57e_image_set()
[all …]
|
| /linux-6.8/Documentation/arch/arm/ |
| D | memory.rst | 2 Kernel Memory Layout on ARM Linux
9 This document describes the virtual memory layout which the Linux
39 in proc-xscale.S to flush the whole data
53 ff800000 ffbfffff Permanent, fixed read-only mapping of the
59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space.
68 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
72 PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
76 MODULES_VADDR MODULES_END-1 Kernel module space
80 TASK_SIZE MODULES_VADDR-1 KASAn shadow memory when KASan is in use.
85 00001000 TASK_SIZE-1 User space mappings
[all …]
|
| /linux-6.8/Documentation/devicetree/bindings/pwm/ |
| D | pwm-fsl-ftm.txt | 8 SoC | FTM-PWM endianness
9 --------+-------------------
19 - compatible : should be "fsl,<soc>-ftm-pwm" and one of the following
21 - "fsl,vf610-ftm-pwm" for PWM compatible with the one integrated on VF610
22 - "fsl,imx8qm-ftm-pwm" for PWM compatible with the one integrated on i.MX8QM
23 - reg: Physical base address and length of the controller's registers
24 - #pwm-cells: Should be 3. See pwm.yaml in this directory for a description of
26 - clock-names: Should include the following module clock source entries:
29 "ftm_fix" (fixed counter clock),
30 "ftm_cnt_clk_en" (external and fixed counter clock enable/disable).
[all …]
|
| /linux-6.8/Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Layout chapter
4 ------
6 The layout of a standard block group is approximately as follows (each
9 .. list-table::
11 :header-rows: 1
13 * - Group 0 Padding
14 - ext4 Super Block
15 - Group Descriptors
16 - Reserved GDT Blocks
[all …]
|
| /linux-6.8/Documentation/networking/ |
| D | xsk-tx-metadata.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 via :doc:`af_xdp`. Refer to :doc:`xdp-rx-metadata` on how to access similar
16 every socket that shares the same umem. The metadata layout is a fixed UAPI,
22 ``xdp_desc->addr`` in the umem frame. Within a frame, the metadata
23 layout is as follows::
27 +-----------------+---------+----------------------------+
29 +-----------------+---------+----------------------------+
32 xdp_desc->addr
36 use ``xdp_desc->addr - tx_metadata_len`` to locate
43 - ``XDP_TXMD_FLAGS_TIMESTAMP``: requests the device to put transmission
[all …]
|
| D | xdp-rx-metadata.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 .. kernel-doc:: net/core/xdp.c
25 .. kernel-doc:: net/core/xdp.c
28 .. kernel-doc:: net/core/xdp.c
35 metadata available in which case the driver returns ``-ENODATA``.
38 implemented, the default ones that return ``-EOPNOTSUPP`` will be used
42 Within an XDP frame, the metadata layout (accessed via ``xdp_buff``) is
45 +----------+-----------------+------+
47 +----------+-----------------+------+
50 xdp_buff->data_meta xdp_buff->data
[all …]
|
| /linux-6.8/drivers/staging/pi433/ |
| D | pi433_if.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
13 * Copyright (C) 2016 Wolf-Entwicklungen
14 * Marcus Wolf <linux@wolf-entwicklungen.de>
23 /*---------------------------------------------------------------------------*/
49 * NOTE: struct layout is the same in 64bit and 32bit userspace.
97 * NOTE: struct layout is the same in 64bit and 32bit userspace.
124 /* only operational, if sync on and fixed length or length byte is used */
|
| /linux-6.8/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
6 NVRAM partition, and the remainder in-between for one to two firmware partitions
7 at fixed offsets. A valid firmware partition is identified by the ImageTag
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
17 compatible = "cfi-flash";
19 bank-width = <2>;
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
|
| D | brcm,bcm963xx-imagetag.txt | 5 partitions or non standard bootloader partition sizes. For these a mixed layout
12 - compatible : must be "brcm,bcm963xx-imagetag"
17 compatible = "cfi-flash";
19 bank-width = <2>;
22 compatible = "fixed-partitions";
23 #address-cells = <1>;
24 #size-cells = <1>;
28 read-only;
33 compatible = "brcm,bcm963xx-imagetag";
38 read-only;
|
| /linux-6.8/sound/aoa/soundbus/i2sbus/ |
| D | core.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright 2006-2008 Johannes Berg <johannes@sipsolutions.net>
12 #include <linux/dma-mapping.h>
32 " no layout-id property is present");
46 r->size = (numcmds + 3) * sizeof(struct dbdma_cmd); in alloc_dbdma_descriptor_ring()
47 /* We use the PCI APIs for now until the generic one gets fixed in alloc_dbdma_descriptor_ring()
48 * enough or until we get some macio-specific versions in alloc_dbdma_descriptor_ring()
50 r->space = dma_alloc_coherent(&macio_get_pci_dev(i2sdev->macio)->dev, in alloc_dbdma_descriptor_ring()
51 r->size, &r->bus_addr, GFP_KERNEL); in alloc_dbdma_descriptor_ring()
52 if (!r->space) in alloc_dbdma_descriptor_ring()
[all …]
|
| /linux-6.8/drivers/gpu/drm/xe/ |
| D | xe_wopcm.c | 1 // SPDX-License-Identifier: MIT
16 * DOC: Write Once Protected Content Memory (WOPCM) Layout
18 * The layout of the WOPCM will be fixed after writing to GuC WOPCM size and
32 * | Size +--------------------+
34 * | | +--------------------+
36 * | | +------------------- +
40 * | +------------------- + <== HuC Firmware Top
94 size = wopcm_size - ctx_rsvd; in __check_layout()
96 guc_wopcm_size > size - guc_wopcm_base)) { in __check_layout()
97 drm_err(&xe->drm, in __check_layout()
[all …]
|
| /linux-6.8/tools/perf/Documentation/ |
| D | intel-hybrid.txt | 2 --------------------
17 0-15
20 16-23
22 It indicates cpu0-cpu15 are core cpus and cpu16-cpu23 are atom cpus.
24 As before, use perf-list to list the symbolic event.
29 [Fixed Counter: Counts the number of instructions retired. Unit: cpu_atom]
31 [Number of instructions retired. Fixed Counter - architectural event. Unit: cpu_core]
47 perf stat -e cpu_core/cycles/
56 For hardware events, they have pre-defined configs (e.g. 0 for cycles).
66 The new attr.config layout for PERF_TYPE_HARDWARE:
[all …]
|
| /linux-6.8/Documentation/fb/ |
| D | api.rst | 9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
24 Device and driver capabilities are reported in the fixed screen information
36 - FB_CAP_FOURCC
40 specifying color components layout.
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
58 - FB_TYPE_PACKED_PIXELS
64 Padding at end of lines may be present and is then reported through the fixed
[all …]
|
| /linux-6.8/drivers/md/ |
| D | raid5.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
31 * Empty -> Want - on read or write to get old data for parity calc
32 * Empty -> Dirty - on compute_parity to satisfy write/sync request.
33 * Empty -> Clean - on compute_block when computing a block for failed drive
34 * Want -> Empty - on failed read
35 * Want -> Clean - on successful completion of read request
36 * Dirty -> Clean - on successful completion of write request
37 * Dirty -> Clean - on failed write
38 * Clean -> Dirty - on compute_parity to satisfy write/sync (RECONSTRUCT or RMW)
40 * The Want->Empty, Want->Clean, Dirty->Clean, transitions
[all …]
|
| /linux-6.8/include/uapi/drm/ |
| D | drm_fourcc.h | 39 * further describe the buffer's format - for example tiling or compression.
42 * ----------------
46 * format and data layout of the buffer, and should be the only way to describe
49 * Having multiple fourcc:modifier pairs which describe the same layout should
56 * vendor-namespaced, and as such the relationship between a fourcc code and a
58 * may preserve meaning - such as number of planes - from the fourcc code,
61 * Modifiers must uniquely encode buffer layout. In other words, a buffer must
64 * a modifier: a buffer may match a 64-pixel aligned modifier and a 32-pixel
76 * - Kernel and user-space drivers: for drivers it's important that modifiers
80 * - Higher-level programs interfacing with KMS/GBM/EGL/Vulkan/etc: these users
[all …]
|
| /linux-6.8/arch/xtensa/include/asm/ |
| D | kmem_layout.h | 2 * Kernel virtual memory layout definitions.
20 * Fixed TLB translations in the processor.
63 #if XCHAL_KSEG_PADDR & (XCHAL_KSEG_ALIGNMENT - 1)
|