On Fri, Sep 17, 2021 at 02:59:42PM +0200, Alexandre Bailon wrote:
quoted hunk ↗ jump to hunk
This adds the device tree bindings for the APU DRM driver.
Signed-off-by: Alexandre Bailon <redacted>
---
.../devicetree/bindings/gpu/mtk,apu-drm.yaml | 38 +++++++++++++++++++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpu/mtk,apu-drm.yaml
diff --git a/Documentation/devicetree/bindings/gpu/mtk,apu-drm.yaml b/Documentation/devicetree/bindings/gpu/mtk,apu-drm.yaml
new file mode 100644
index 0000000000000..6f432d3ea478c
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpu/mtk,apu-drm.yaml
@@ -0,0 +1,38 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/gpu/mediatek,apu-drm.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: AI Processor Unit DRM
DRM is a linux thing, not h/w.
+
+properties:
+ compatible:
+ const: mediatek,apu-drm
+
+ remoteproc:
So is remoteproc.
Why don't you have the remoteproc driver create the DRM device?
+ maxItems: 2
+ description:
+ Handle to remoteproc devices controlling the APU
+
+ iova:
+ maxItems: 1
+ description:
+ Address and size of virtual memory that could used by the APU
Why does this need to be in DT? If you need to reserve certain VAs, then
this discussion[1] might be of interest.
Rob
[1] https://lore.kernel.org/all/YUIPCxnyRutMS47%2F@orome.fritz.box/ (local)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel