a13de74e47
Including: - Consolidate iommu_map/unmap functions. There have been blocking and atomic variants so far, but that was problematic as this approach does not scale with required new variants which just differ in the GFP flags used. So Jason consolidated this back into single functions that take a GFP parameter. This has the potential to cause conflicts with other trees, as they introduce new call-sites for the changed functions. I offered them to pull in the branch containing these changes and resolve it, but I am not sure everyone did that. The conflicts this caused with upstream up to v6.2-rc8 are resolved in the final merge commit. - Retire the detach_dev() call-back in iommu_ops - Arm SMMU updates from Will: - Device-tree binding updates: * Cater for three power domains on SM6375 * Document existing compatible strings for Qualcomm SoCs * Tighten up clocks description for platform-specific compatible strings - Enable Qualcomm workarounds for some additional platforms that need them - Intel VT-d updates from Lu Baolu: - Add Intel IOMMU performance monitoring support - Set No Execute Enable bit in PASID table entry - Two performance optimizations - Fix PASID directory pointer coherency - Fix missed rollbacks in error path - Cleanups - Apple t8110 DART support - Exynos IOMMU: - Implement better fault handling - Error handling fixes - Renesas IPMMU: - Add device tree bindings for r8a779g0 - AMD IOMMU: - Various fixes for handling on SNP-enabled systems and handling of faults with unknown request-ids - Cleanups and other small fixes - Various other smaller fixes and cleanups -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEr9jSbILcajRFYWYyK/BELZcBGuMFAmP0hDwACgkQK/BELZcB GuM43RAA0YieShO+X0h6TFGfbK0zVoPd91giZehWBv9rHK7pP4iY8UEtBLBWGx/t CId4t98mmKmC212zz8QxrwAEzyTIRY+2t1yrpG2aVkoTYk8inMb07TU37wganh3O T0QccXN+9b2BS4k8yro5f3uX0d/C1JQVcMowwr53VMb/e73huqP1VTbz06/CIWMH DUhVRCzmNhSvoUOT5n7g6+ZDH+pot8WPZbtHV7FowEsmPCRc7Fj8kXyI9FEwKwrZ hIV5Y+6Lej8nQScgbO8MfblJym3VrBoSoM4GY2w0L0rjQw6m+Xtea5rT0W39YVWy YpiscLTL8TIMPP9zK1dXVygTaABK4J2iWmheHPkpKXIhK0iuH3Dke0Do5p6DNITj 7J2YlaNEB480D5hvNBKsbbGHavgGPT8m529Sz0R7mSC7omRzqiG5Vsb46IXL+2bc 92ojjYNfXb6OCtagIr2LMBLZRL2JCODqF1dUmyZfA8GKOHLP5kZXoMM+sZbQ2aUL 1LOxRZVx+tlb9V4VaH1ZSs/6eM+HLDzjtHeu3PoWYf6mW4AEt4S/yl9SKAkGdBqt jCUErmYB1nU/eefqG1jhWRpQeJabcT3Oe30NZru1pfMoREThhjbAACw1JxWtoe1X ipGpV6lAP7tQUGuRk3/9O1lNqElJuNwC5lVTjS4FJ38vYQhQbao= =ZaZV -----END PGP SIGNATURE----- Merge tag 'iommu-updates-v6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu Pull iommu updates from Joerg Roedel: - Consolidate iommu_map/unmap functions. There have been blocking and atomic variants so far, but that was problematic as this approach does not scale with required new variants which just differ in the GFP flags used. So Jason consolidated this back into single functions that take a GFP parameter. - Retire the detach_dev() call-back in iommu_ops - Arm SMMU updates from Will: - Device-tree binding updates: - Cater for three power domains on SM6375 - Document existing compatible strings for Qualcomm SoCs - Tighten up clocks description for platform-specific compatible strings - Enable Qualcomm workarounds for some additional platforms that need them - Intel VT-d updates from Lu Baolu: - Add Intel IOMMU performance monitoring support - Set No Execute Enable bit in PASID table entry - Two performance optimizations - Fix PASID directory pointer coherency - Fix missed rollbacks in error path - Cleanups - Apple t8110 DART support - Exynos IOMMU: - Implement better fault handling - Error handling fixes - Renesas IPMMU: - Add device tree bindings for r8a779g0 - AMD IOMMU: - Various fixes for handling on SNP-enabled systems and handling of faults with unknown request-ids - Cleanups and other small fixes - Various other smaller fixes and cleanups * tag 'iommu-updates-v6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu: (71 commits) iommu/amd: Skip attach device domain is same as new domain iommu: Attach device group to old domain in error path iommu/vt-d: Allow to use flush-queue when first level is default iommu/vt-d: Fix PASID directory pointer coherency iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode iommu/vt-d: Fix error handling in sva enable/disable paths iommu/amd: Improve page fault error reporting iommu/amd: Do not identity map v2 capable device when snp is enabled iommu: Fix error unwind in iommu_group_alloc() iommu/of: mark an unused function as __maybe_unused iommu: dart: DART_T8110_ERROR range should be 0 to 5 iommu/vt-d: Enable IOMMU perfmon support iommu/vt-d: Add IOMMU perfmon overflow handler support iommu/vt-d: Support cpumask for IOMMU perfmon iommu/vt-d: Add IOMMU perfmon support iommu/vt-d: Support Enhanced Command Interface iommu/vt-d: Retrieve IOMMU perfmon capability information iommu/vt-d: Support size of the register set in DRHD iommu/vt-d: Set No Execute Enable bit in PASID table entry iommu/vt-d: Remove sva from intel_svm_dev ...
182 lines
5.4 KiB
YAML
182 lines
5.4 KiB
YAML
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/reserved-memory/reserved-memory.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: /reserved-memory Child Node Common
|
|
|
|
maintainers:
|
|
- devicetree-spec@vger.kernel.org
|
|
|
|
description: >
|
|
Reserved memory is specified as a node under the /reserved-memory node. The
|
|
operating system shall exclude reserved memory from normal usage one can
|
|
create child nodes describing particular reserved (excluded from normal use)
|
|
memory regions. Such memory regions are usually designed for the special
|
|
usage by various device drivers.
|
|
|
|
Each child of the reserved-memory node specifies one or more regions
|
|
of reserved memory. Each child node may either use a 'reg' property to
|
|
specify a specific range of reserved memory, or a 'size' property with
|
|
optional constraints to request a dynamically allocated block of
|
|
memory.
|
|
|
|
Following the generic-names recommended practice, node names should
|
|
reflect the purpose of the node (ie. "framebuffer" or "dma-pool").
|
|
Unit address (@<address>) should be appended to the name if the node
|
|
is a static allocation.
|
|
|
|
properties:
|
|
reg: true
|
|
|
|
size:
|
|
oneOf:
|
|
- $ref: /schemas/types.yaml#/definitions/uint32
|
|
- $ref: /schemas/types.yaml#/definitions/uint64
|
|
description: >
|
|
Length based on parent's \#size-cells. Size in bytes of memory to
|
|
reserve.
|
|
|
|
alignment:
|
|
oneOf:
|
|
- $ref: /schemas/types.yaml#/definitions/uint32
|
|
- $ref: /schemas/types.yaml#/definitions/uint64
|
|
description: >
|
|
Length based on parent's \#size-cells. Address boundary for
|
|
alignment of allocation.
|
|
|
|
alloc-ranges:
|
|
$ref: /schemas/types.yaml#/definitions/uint32-array
|
|
description: >
|
|
Address and Length pairs. Specifies regions of memory that are
|
|
acceptable to allocate from.
|
|
|
|
iommu-addresses:
|
|
$ref: /schemas/types.yaml#/definitions/phandle-array
|
|
description: >
|
|
A list of phandle and specifier pairs that describe static IO virtual
|
|
address space mappings and carveouts associated with a given reserved
|
|
memory region. The phandle in the first cell refers to the device for
|
|
which the mapping or carveout is to be created.
|
|
|
|
The specifier consists of an address/size pair and denotes the IO
|
|
virtual address range of the region for the given device. The exact
|
|
format depends on the values of the "#address-cells" and "#size-cells"
|
|
properties of the device referenced via the phandle.
|
|
|
|
When used in combination with a "reg" property, an IOVA mapping is to
|
|
be established for this memory region. One example where this can be
|
|
useful is to create an identity mapping for physical memory that the
|
|
firmware has configured some hardware to access (such as a bootsplash
|
|
framebuffer).
|
|
|
|
If no "reg" property is specified, the "iommu-addresses" property
|
|
defines carveout regions in the IOVA space for the given device. This
|
|
can be useful if a certain memory region should not be mapped through
|
|
the IOMMU.
|
|
|
|
no-map:
|
|
type: boolean
|
|
description: >
|
|
Indicates the operating system must not create a virtual mapping
|
|
of the region as part of its standard mapping of system memory,
|
|
nor permit speculative access to it under any circumstances other
|
|
than under the control of the device driver using the region.
|
|
|
|
reusable:
|
|
type: boolean
|
|
description: >
|
|
The operating system can use the memory in this region with the
|
|
limitation that the device driver(s) owning the region need to be
|
|
able to reclaim it back. Typically that means that the operating
|
|
system can use that region to store volatile or cached data that
|
|
can be otherwise regenerated or migrated elsewhere.
|
|
|
|
allOf:
|
|
- if:
|
|
required:
|
|
- no-map
|
|
|
|
then:
|
|
not:
|
|
required:
|
|
- reusable
|
|
|
|
- if:
|
|
required:
|
|
- reusable
|
|
|
|
then:
|
|
not:
|
|
required:
|
|
- no-map
|
|
|
|
oneOf:
|
|
- oneOf:
|
|
- required:
|
|
- reg
|
|
|
|
- required:
|
|
- size
|
|
|
|
- oneOf:
|
|
# IOMMU reservations
|
|
- required:
|
|
- iommu-addresses
|
|
|
|
# IOMMU mappings
|
|
- required:
|
|
- reg
|
|
- iommu-addresses
|
|
|
|
additionalProperties: true
|
|
|
|
examples:
|
|
- |
|
|
/ {
|
|
compatible = "foo";
|
|
model = "foo";
|
|
|
|
#address-cells = <2>;
|
|
#size-cells = <2>;
|
|
|
|
reserved-memory {
|
|
#address-cells = <2>;
|
|
#size-cells = <2>;
|
|
ranges;
|
|
|
|
adsp_resv: reservation-adsp {
|
|
/*
|
|
* Restrict IOVA mappings for ADSP buffers to the 512 MiB region
|
|
* from 0x40000000 - 0x5fffffff. Anything outside is reserved by
|
|
* the ADSP for I/O memory and private memory allocations.
|
|
*/
|
|
iommu-addresses = <&adsp 0x0 0x00000000 0x00 0x40000000>,
|
|
<&adsp 0x0 0x60000000 0xff 0xa0000000>;
|
|
};
|
|
|
|
fb: framebuffer@90000000 {
|
|
reg = <0x0 0x90000000 0x0 0x00800000>;
|
|
iommu-addresses = <&dc0 0x0 0x90000000 0x0 0x00800000>;
|
|
};
|
|
};
|
|
|
|
bus@0 {
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
ranges = <0x0 0x0 0x0 0x40000000>;
|
|
|
|
adsp: adsp@2990000 {
|
|
reg = <0x2990000 0x2000>;
|
|
memory-region = <&adsp_resv>;
|
|
};
|
|
|
|
dc0: display@15200000 {
|
|
reg = <0x15200000 0x10000>;
|
|
memory-region = <&fb>;
|
|
};
|
|
};
|
|
};
|
|
...
|