[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-b0ca2ee2-259a-4a1e-86ee-63b093202060-1596451368067@3c-app-gmx-bap36>
Date: Mon, 3 Aug 2020 12:42:48 +0200
From: Frank Wunderlich <frank-w@...lic-files.de>
To: Chun-Kuang Hu <chunkuang.hu@...nel.org>
Cc: Chun-Kuang Hu <chunkuang.hu@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
David Airlie <airlied@...ux.ie>,
linux-kernel <linux-kernel@...r.kernel.org>,
DRI Development <dri-devel@...ts.freedesktop.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
Daniel Vetter <daniel@...ll.ch>,
Matthias Brugger <matthias.bgg@...il.com>,
Bibby Hsieh <bibby.hsieh@...iatek.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Aw: Re: Re: [PATCH v2 1/5] drm/mediatek: config component output by
device node port
Hi
> Gesendet: Montag, 03. August 2020 um 01:47 Uhr
> Von: "Chun-Kuang Hu" <chunkuang.hu@...nel.org>
> Now I just care about the bls to dpi. So in mediatek,disp.txt, you
> just need to add a Optional properties - port (input and output), and
> modify mediatek,dpi.txt for its input port.
you mean something like this is enough:
Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
for details.
+Optional properties:
+- port (input and output) see ../../media/video-interfaces.txt
+
Examples:
Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.txt:
Optional properties:
- pinctrl-names: Contain "default" and "sleep".
+- port: Input port node with endpoint definition, this can be connected to <chipid>-disp-pwm
Example:
should i link to pwm/pwm-mtk-disp.txt in doc?
regards Frank
Powered by blists - more mailing lists