Commit 9181b5bb authored by Chen-Yu Tsai's avatar Chen-Yu Tsai Committed by Maxime Ripard

dt-bindings: display: sunxi: Improve endpoint ID scheme readability

The explanation for the endpoint ID numbering scheme is convoluted
and hard to understand.

This patch aims to improve the readability of it by combining the
existing two paragraphs, while also providing a diagram example,
and how endpoints should be numbered based on that example.
Signed-off-by: default avatarChen-Yu Tsai <wens@csie.org>
Signed-off-by: default avatarMaxime Ripard <maxime.ripard@free-electrons.com>
parent 9cbcbdba
...@@ -4,15 +4,33 @@ Allwinner A10 Display Pipeline ...@@ -4,15 +4,33 @@ Allwinner A10 Display Pipeline
The Allwinner A10 Display pipeline is composed of several components The Allwinner A10 Display pipeline is composed of several components
that are going to be documented below: that are going to be documented below:
For the input port of all components up to the TCON in the display For all connections between components up to the TCONs in the display
pipeline, if there are multiple components, the local endpoint IDs pipeline, when there are multiple components of the same type at the
must correspond to the index of the upstream block. For example, if same depth, the local endpoint ID must be the same as the remote
the remote endpoint is Frontend 1, then the local endpoint ID must component's index. For example, if the remote endpoint is Frontend 1,
be 1. then the local endpoint ID must be 1.
Conversely, for the output ports of the same group, the remote endpoint Frontend 0 [0] ------- [0] Backend 0 [0] ------- [0] TCON 0
ID must be the index of the local hardware block. If the local backend [1] -- -- [1] [1] -- -- [1]
is backend 1, then the remote endpoint ID must be 1. \ / \ /
X X
/ \ / \
[0] -- -- [0] [0] -- -- [0]
Frontend 1 [1] ------- [1] Backend 1 [1] ------- [1] TCON 1
For a two pipeline system such as the one depicted above, the lines
represent the connections between the components, while the numbers
within the square brackets corresponds to the ID of the local endpoint.
The same rule also applies to DE 2.0 mixer-TCON connections:
Mixer 0 [0] ----------- [0] TCON 0
[1] ---- ---- [1]
\ /
X
/ \
[0] ---- ---- [0]
Mixer 1 [1] ----------- [1] TCON 1
HDMI Encoder HDMI Encoder
------------ ------------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment