| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | nvmem-provider.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
35 #define NVMEM_DEVID_NONE (-1)
36 #define NVMEM_DEVID_AUTO (-2)
39 * struct nvmem_keepout - NVMEM register keepout range.
52 * struct nvmem_cell_info - NVMEM cell description
77 * struct nvmem_config - NVMEM device configuration
83 * @cells: Optional array of pre-defined NVMEM cells.
85 * @add_legacy_fixed_of_cells: Read fixed NVMEM cells from old OF syntax.
91 * @read_only: Device is read-only.
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/mm/ |
| D | mmap.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * flexible mmap layout support
5 * Copyright 2003-2004 Red Hat Inc., Durham, North Carolina.
16 #include <linux/elf-randomize.h>
30 if (current->personality & ADDR_COMPAT_LAYOUT) in mmap_is_legacy()
33 if (rlim_stack->rlim_cur == RLIM_INFINITY) in mmap_is_legacy()
55 if (!(current->flags & PF_RANDOMIZE)) in stack_maxrandom_size()
68 unsigned long gap = rlim_stack->rlim_cur; in mmap_base()
80 return PAGE_ALIGN(DEFAULT_MAP_WINDOW - gap - rnd); in mmap_base()
94 struct mm_struct *mm = current->mm; in radix__arch_get_unmapped_area()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/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 -----------------------------------------------------------------------
40 fffffdfffe5f9000 fffffdfffe9fffff 4124KB fixed mappings
48 AArch64 Linux memory layout with 64KB pages + 3 levels (52-bit with HW support)::
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 :doc:`../userspace-api/ioctl/ioctl-number`
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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/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 …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/dispnv50/ |
| D | wndwc57e.c | 37 struct nvif_push *push = wndw->wndw.push; in wndwc57e_image_set()
44 NVVAL(NVC57E, SET_PRESENT_CONTROL, MIN_PRESENT_INTERVAL, asyw->image.interval) | in wndwc57e_image_set()
45 NVVAL(NVC57E, SET_PRESENT_CONTROL, BEGIN_MODE, asyw->image.mode) | in wndwc57e_image_set()
49 NVVAL(NVC57E, SET_SIZE, WIDTH, asyw->image.w) | in wndwc57e_image_set()
50 NVVAL(NVC57E, SET_SIZE, HEIGHT, asyw->image.h), in wndwc57e_image_set()
53 NVVAL(NVC57E, SET_STORAGE, BLOCK_HEIGHT, asyw->image.blockh) | in wndwc57e_image_set()
54 NVVAL(NVC57E, SET_STORAGE, MEMORY_LAYOUT, asyw->image.layout), in wndwc57e_image_set()
57 NVVAL(NVC57E, SET_PARAMS, FORMAT, asyw->image.format) | in wndwc57e_image_set()
63 NVVAL(NVC57E, SET_PLANAR_STORAGE, PITCH, asyw->image.blocks[0]) | in wndwc57e_image_set()
64 NVVAL(NVC57E, SET_PLANAR_STORAGE, PITCH, asyw->image.pitch[0] >> 6)); in wndwc57e_image_set()
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 7 Different devices may be partitioned in a different ways. Some may use a fixed
8 flash layout set at production time. Some may use on-flash table that describes
20 hierarchical (multi-level) layouts and should be used if there is some
27 Fixed Partitions
30 Partitions can be represented by sub-nodes of a flash device. This can be used
32 used for what purposes, but which don't use an on-flash partition table such
37 - compatible : (required) must be "fixed-partitions"
45 #address-cells & #size-cells must both be present in the partitions subnode of the
47 <1>: for partitions that require a single 32-bit cell to represent their
49 <2>: for partitions that require two 32-bit cells to represent their
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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;
|
| /kernel/linux/linux-6.6/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;
|
| /kernel/linux/linux-5.10/drivers/staging/pi433/ |
| D | pi433_if.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
15 * HopeRf with a similar interace - e. g. RFM69HCW, RFM12, RFM95, ...
16 * Copyright (C) 2016 Wolf-Entwicklungen
17 * Marcus Wolf <linux@wolf-entwicklungen.de>
26 /*---------------------------------------------------------------------------*/
52 * NOTE: struct layout is the same in 64bit and 32bit userspace.
100 * NOTE: struct layout is the same in 64bit and 32bit userspace.
127 /* only operational, if sync on and fixed length or length byte is used */
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-6.6/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>
31 " no layout-id property is present");
45 r->size = (numcmds + 3) * sizeof(struct dbdma_cmd); in alloc_dbdma_descriptor_ring()
46 /* We use the PCI APIs for now until the generic one gets fixed in alloc_dbdma_descriptor_ring()
47 * enough or until we get some macio-specific versions in alloc_dbdma_descriptor_ring()
49 r->space = dma_alloc_coherent(&macio_get_pci_dev(i2sdev->macio)->dev, in alloc_dbdma_descriptor_ring()
50 r->size, &r->bus_addr, GFP_KERNEL); in alloc_dbdma_descriptor_ring()
51 if (!r->space) in alloc_dbdma_descriptor_ring()
[all …]
|