linux-kernel - [PATCH 1/7] Documentation: of: add type property

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87eg7nxr00.wl%kuninori.morimoto.gx@renesas.com>
Date:	Fri, 24 Jun 2016 02:32:12 +0000
From:	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:	Rob Herring <robh+dt@...nel.org>, Mark Brown <broonie@...aro.org>,
	Mark Brown <broonie@...nel.org>,
	Laurent <laurent.pinchart@...asonboard.com>,
	Guennadi <g.liakhovetski@....de>,
	Grant Likely <grant.likely@...aro.org>,
	Frank Rowand <frowand.list@...il.com>
CC:	Linux-Kernel <linux-kernel@...r.kernel.org>,
	Linux-DT <devicetree@...r.kernel.org>,
	Linux-ALSA <alsa-devel@...a-project.org>
Subject: [PATCH 1/7] Documentation: of: add type property


From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>

OF graph is used mainly from V4L2, but ALSA needs to use it too.
Then, ALSA needs to know each port/endpoint type, otherwise it
can't detect ALSA port/endpoint correctly.
This patch enables to use type property on OF graph.

Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
---
 Documentation/devicetree/bindings/graph.txt | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/Documentation/devicetree/bindings/graph.txt b/Documentation/devicetree/bindings/graph.txt
index fcb1c6a..b5b9040 100644
--- a/Documentation/devicetree/bindings/graph.txt
+++ b/Documentation/devicetree/bindings/graph.txt
@@ -110,6 +110,32 @@ device-2 {
         };
 };
 
+port / endpoint type
+--------------------
+
+Each ports / port / endpoint can have its type if needed.
+child node can take over parent node type. below example indicates
+device0 type is "typeA" && "typeB",
+device1 type is "typeA" && "typeB" && "typeC".
+
+device {
+	ports {
+		type = "typeA";
+
+		port@0 {
+			type = "typeB";
+
+			device0: endpoint@0 {
+			};
+
+			device1: endpoint@1 {
+				type = "typeC";
+			};
+		};
+		...
+	};
+};
+
 
 Required properties
 -------------------
-- 
1.9.1