On Mon, 26 Aug 2019 18:15:41 +0200 Jernej Škrabec jernej.skrabec@siol.net wrote:
Hi Boris!
Dne ponedeljek, 26. avgust 2019 ob 17:26:46 CEST je Boris Brezillon napisal(a):
Some LVDS encoder might support several input/output bus formats. Add a way to describe the one used on a specific design by adding optional 'data-mapping' properties to the input/output ports.
Signed-off-by: Boris Brezillon boris.brezillon@collabora.com
Changes in v2:
- Make the bus-format negotiation logic more generic
.../display/bridge/lvds-transmitter.txt | 12 ++ drivers/gpu/drm/bridge/lvds-encoder.c | 105 ++++++++++++++++++ 2 files changed, 117 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt b/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt index 60091db5dfa5..db51eab216f7 100644 --- a/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt +++ b/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt @@ -36,6 +36,18 @@ graph bindings specified in Documentation/devicetree/bindings/graph.txt. - Video port 0 for parallel input
- Video port 1 for LVDS output
+Optional port 0 node properties:
+- data-mapping: can be one of the following values
- "rgb-24"
- "rgb-18"
+Optional port 0 node properties:
You probably mean port 1 ^^^ ?
Yes.
Anyway, devicetree doc changes should be separate patch and be send to DT ML (I can't see it in CC).
I'll fix that in v3. In the meantime, I'd really like to have feedback on patches 1 to 16 as this is where core changes are.