| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 13 Feb 2020 17:39:55 +0100
From: Thierry Reding <thierry.reding@...il.com>
To: Arnd Bergmann <arnd@...db.de>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Rob Herring <robh+dt@...nel.org>
Cc: Joerg Roedel <joro@...tes.org>, Olof Johansson <olof@...om.net>,
linux-tegra@...r.kernel.org, iommu@...ts.linux-foundation.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [PATCH v4 1/5] dt-bindings: Add memory controller bindings
From: Thierry Reding <treding@...dia.com>
Add the DT schema for memory controller and consumer bindings.
Signed-off-by: Thierry Reding <treding@...dia.com>
---
.../bindings/memory-controllers/consumer.yaml | 14 ++++++++
.../memory-controllers/memory-controller.yaml | 32 +++++++++++++++++++
2 files changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/consumer.yaml
create mode 100644 Documentation/devicetree/bindings/memory-controllers/memory-controller.yaml
diff --git a/Documentation/devicetree/bindings/memory-controllers/consumer.yaml b/Documentation/devicetree/bindings/memory-controllers/consumer.yaml
new file mode 100644
index 000000000000..7b71a6110c51
--- /dev/null
+++ b/Documentation/devicetree/bindings/memory-controllers/consumer.yaml
@@ -0,0 +1,14 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/memory-controllers/consumer.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common memory controller consumer binding
+
+maintainers:
+ - Thierry Reding <thierry.reding@...il.com>
+
+properties:
+ memory-controller:
+ $ref: /schemas/types.yaml#/definitions/phandle-array
diff --git a/Documentation/devicetree/bindings/memory-controllers/memory-controller.yaml b/Documentation/devicetree/bindings/memory-controllers/memory-controller.yaml
new file mode 100644
index 000000000000..26257a666c3c
--- /dev/null
+++ b/Documentation/devicetree/bindings/memory-controllers/memory-controller.yaml
@@ -0,0 +1,32 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/memory-controllers/memory-controller.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common memory controller binding
+
+maintainers:
+ - Thierry Reding <thierry.reding@...il.com>
+
+description: |
+ The memory access hierarchy in a modern device can be fairly complicated.
+ Accesses to system memory typically end up going through a memory controller
+ that ensures that data is stored. Along the way, these accesses can undergo
+ classification and be prioritized and/or arbitrated.
+
+ The interconnect bindings (see ../interconnect/interconnect.txt) provides a
+ way of describing the data paths between devices and system memory. However
+ these interconnect paths, in order to be most flexible, describe the paths
+ in a very fine-grained way, so situations can arise where it is no longer
+ possible to derive a unique memory parent for any given device.
+
+ In order to remove such potential ambiguities, a memory controller can be
+ specified in device tree. A memory controller specified in this way will be
+ used as the DMA parent for a given device. The memory controller defines a
+ memory bus via the "dma-ranges" property, which will in turn be used to set
+ the range of memory accessible to DMA children of the memory controller.
+
+properties:
+ "#memory-controller-cells": true
+ dma-ranges: true
--
2.24.1
Powered by blists - more mailing lists