Home
last modified time | relevance | path

Searched +full:reserved +full:- +full:memory (Results 1 – 25 of 1252) sorted by relevance

12345678910>>...51

/freebsd/sys/contrib/device-tree/Bindings/reserved-memory/
H A Dreserved-memory.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/reserved-memory.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: /reserved-memory Child Node Common
10 - devicetree-spec@vger.kernel.org
13 Reserved memory is specified as a node under the /reserved-memory node. The
14 operating system shall exclude reserved memory from normal usage one can
15 create child nodes describing particular reserved (excluded from normal use)
16 memory regions. Such memory regions are usually designed for the special
[all …]
H A Dmemory-region.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/memory-region.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Reserved Memory Region
10 - devicetree-spec@vger.kernel.org
13 Regions in the /reserved-memory node may be referenced by other device
14 nodes by adding a memory-region property to the device node.
19 memory-region:
20 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
H A Dxen,shared-memory.txt1 * Xen hypervisor reserved-memory binding
3 Expose one or more memory regions as reserved-memory to the guest
5 to be a shared memory area across multiple virtual machines for
8 For each of these pre-shared memory regions, a range is exposed under
9 the /reserved-memory node as a child node. Each range sub-node is named
10 xen-shmem@<address> and has the following properties:
12 - compatible:
13 compatible = "xen,shared-memory-v1"
15 - reg:
16 the base guest physical address and size of the shared memory region
[all …]
H A Dshared-dma-pool.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: /reserved-memory DMA pool
10 - devicetree-spec@vger.kernel.org
13 - $ref: reserved-memory.yaml
18 - const: shared-dma-pool
20 This indicates a region of memory meant to be used as a shared
25 - const: restricted-dma-pool
[all …]
H A Dqcom,rmtfs-mem.txt1 Qualcomm Remote File System Memory binding
3 This binding describes the Qualcomm remote filesystem memory, which serves the
4 purpose of describing the shared memory region used for remote processors to
7 - compatible:
11 "qcom,rmtfs-mem"
13 - reg:
15 Value type: <prop-encoded-array>
16 Definition: must specify base address and size of the memory region,
17 as described in reserved-memory.txt
19 - size:
[all …]
H A Dframebuffer.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: /reserved-memory framebuffer node
10 - devicetree-spec@vger.kernel.org
13 - $ref: reserved-memory.yaml
19 This indicates a region of memory meant to be used as a framebuffer for
21 the framebuffer from being overwritten and use it as the backing memory
22 for a display device (such as simple-framebuffer).
[all …]
H A Dqcom,cmd-db.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/qcom,cmd-db.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 is stored in a shared memory region and is loaded by the remote processor.
17 remote processor and made available in the shared memory.
20 - Bjorn Andersson <bjorn.andersson@linaro.org>
23 - $ref: reserved-memory.yaml
27 const: qcom,cmd-db
30 - reg
[all …]
H A Dqcom,rmtfs-mem.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved
[all...]
H A Dgoogle,open-dice.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/google,open-dice.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 This binding represents a reserved memory region containing data
13 See https://pigweed.googlesource.com/open-dice/
16 - David Brazdil <dbrazdil@google.com>
19 - $ref: reserved-memory.yaml
23 const: google,open-dice
26 description: page-aligned region of memory containing DICE data
[all …]
H A Dphram.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/phram.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 Specifies that the reserved memory region can be used as an MTD or block
17 - Vincent Whitchurch <vincent.whitchurch@axis.com>
20 - $ref: reserved-memory.yaml
21 - $ref: /schemas/mtd/mtd.yaml
28 description: region of memory that can be used as an MTD/block device
31 - compatible
[all …]
H A Dqcom,cmd-db.txt2 ---------
6 is stored in a shared memory region and is loaded by the remote processor.
11 remote processor and made available in the shared memory.
13 The bindings for Command DB is specified in the reserved-memory section in
17 - compatible:
20 Definition: Should be "qcom,cmd-db"
22 - reg:
26 the Command DB in memory.
30 reserved-memory {
32 reserved-memory@85fe0000 {
[all …]
/freebsd/sys/contrib/device-tree/Bindings/soc/fsl/
H A Dfsl,qman-fqd.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/fsl/fsl,qman-fqd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: QMan Private Memory Nodes
10 - Frank Li <Frank.Li@nxp.com>
13 QMan requires two contiguous range of physical memory used for the backing store
15 This memory is reserved/allocated as a node under the /reserved-memory node.
17 BMan requires a contiguous range of physical memory used for the backing store
18 for BMan Free Buffer Proxy Records (FBPR). This memory is reserved/allocated as
[all …]
H A Dqman.txt3 Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
7 - QMan Node
8 - QMan Private Memory Nodes
9 - Example
13 The Queue Manager is part of the Data-Path Acceleration Architecture (DPAA). QMan
16 flow-level queuing, is also responsible for congestion management functions such
22 - compatible
26 May include "fsl,<SoC>-qman"
28 - reg
30 Value type: <prop-encoded-array>
[all …]
H A Dbman.txt3 Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
7 - BMan Node
8 - BMan Private Memory Node
9 - Example
13 The Buffer Manager is part of the Data-Path Acceleration Architecture (DPAA).
20 - compatible
24 May include "fsl,<SoC>-bman"
26 - reg
28 Value type: <prop-encoded-array>
34 - interrupts
[all …]
/freebsd/sys/contrib/device-tree/Bindings/remoteproc/
H A Dti,davinci-rproc.txt4 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
5 is used to offload some of the processor-intensive tasks or algorithms, for
8 The processor cores in the sub-system usually contain additional sub-modules
9 like L1 and/or L2 caches/SRAMs, an Interrupt Controller, an external memory
15 Each DSP Core sub-system is represented as a single DT node.
18 --------------------
21 - compatible: Should be one of the following,
22 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
24 - reg: Should contain an entry for each value in 'reg-names'.
25 Each entry should have the memory region's start address
[all …]
H A Dti,omap-remoteproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remotepro
[all...]
H A Dti,k3-dsp-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-dsp-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more TI DSP Core sub-systems
14 that are used to offload some of the processor-intensive tasks or algorithms,
17 These processor sub-systems usually contain additional sub-modules like
18 L1 and/or L2 caches/SRAMs, an Interrupt Controller, an external memory
23 Each DSP Core sub-system is represented as a single DT node. Each node has a
[all …]
H A Dti,keystone-rproc.txt5 sub-systems that are used to offload some of the processor-intensive tasks or
8 These processor sub-systems usually contain additional sub-modules like L1
9 and/or L2 caches/SRAMs, an Interrupt Controller, an external memory controller,
15 Each DSP Core sub-system is represented as a single DT node, and should also
22 --------------------
25 - compatible: Should be one of the following,
26 "ti,k2hk-dsp" for DSPs on Keystone 2 66AK2H/K SoCs
27 "ti,k2l-dsp" for DSPs on Keystone 2 66AK2L SoCs
28 "ti,k2e-dsp" for DSPs on Keystone 2 66AK2E SoCs
29 "ti,k2g-dsp" for DSPs on Keystone 2 66AK2G SoCs
[all …]
H A Dti,k3-m4f-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-m4f-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hari Nagalla <hnagalla@ti.com>
11 - Mathieu Poirier <mathieu.poirier@linaro.org>
20 $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
25 - ti,am64-m4fss
27 power-domains:
30 "#address-cells":
[all …]
H A Drenesas,rcar-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/renesas,rcar-rproc.yaml#
5 $schema: http://devicetree.org/meta-schema
[all...]
/freebsd/sys/contrib/device-tree/src/arm64/qcom/
H A Dqcs8550.dtsi1 // SPDX-License-Identifier: BSD-3-Clause
3 * Copyright (c) 2023-2024, Qualcomm Innovation Center, Inc. All rights reserved.
8 /delete-node/ &reserved_memory;
11 reserved_memory: reserved-memory {
12 #address-cells = <2>;
13 #size-cells = <2>;
17 /* These are 3 types of reserved memory regions here:
20 * indicate the firmware related reserved information. Bootloader
24 * table and add reserved memory regions to efi config table. Current
25 * reserved memory region may have reserved region which was not yet
[all …]
/freebsd/sys/contrib/device-tree/src/arm64/ti/
H A Dk3-am68-sk-som.dtsi1 // SPDX-License-Identifier: GPL-2.0-only OR MIT
3 * Copyright (C) 2023-2024 Texas Instruments Incorporated - https://www.ti.com/
6 /dts-v1/;
8 #include "k3-j721s2.dtsi"
9 #include <dt-bindings/gpio/gpio.h>
12 memory@80000000 {
13 device_type = "memory";
14 bootph-all;
20 reserved_memory: reserved-memory {
21 #address-cells = <2>;
[all …]
/freebsd/sys/contrib/device-tree/Bindings/soc/qcom/
H A Dqcom,smem.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Shared Memory Manager
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
14 This binding describes the Qualcomm Shared Memory Manager, a region of
15 reserved-memory used to share data between various subsystems and OSes in
25 memory-region:
27 description: handle to memory reservation for main SMEM memory region.
[all …]
/freebsd/sys/dev/drm2/ttm/
H A Dttm_bo_api.h3 * Copyright (c) 2006-2009 VMware, Inc., Palo Alto, CA., USA
4 * All Rights Reserved.
20 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
28 * Authors: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
67 * @is_iomem: is this io memory ?
89 * @mm_node: Memory manager node.
90 * @size: Requested size of memory region.
91 * @num_pages: Actual size of memory region in pages.
119 * but they cannot be accessed from user-space. For kernel-only use.
152 * pinned in physical memory. If this behaviour is not desired, this member
[all …]
/freebsd/sys/contrib/device-tree/Bindings/media/
H A Damphion,vpu.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Ming Qian <ming.qian@nxp.com>
12 - Shijie Qin <shijie.qin@nxp.com>
14 description: |-
20 pattern: "^vpu@[0-9a-f]+$"
24 - enum:
25 - nxp,imx8qm-vpu
26 - nxp,imx8qxp-vpu
[all …]

12345678910>>...51