On Wed, Dec 9, 2015 at 3:58 AM, Andrzej Hajda <a.hajda@xxxxxxxxxxx> wrote:
> Hi Rob,
>
> Thanks for review.
>
>
> On 12/09/2015 04:47 AM, Rob Herring wrote:
>> On Tue, Dec 08, 2015 at 02:49:05PM +0100, Andrzej Hajda wrote:
>>> SiI8620 transmitter converts eTMDS/HDMI signal to MHL 3.0. It is controlled
>>> via I2C bus.
>>>
>>> Signed-off-by: Andrzej Hajda <a.hajda@xxxxxxxxxxx>
>>> ---
>>> .../bindings/video/bridge/sil-sii8620.txt | 34 ++++++++++++++++++++++
>>> 1 file changed, 34 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/video/bridge/sil-sii8620.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/video/bridge/sil-sii8620.txt b/Documentation/devicetree/bindings/video/bridge/sil-sii8620.txt
[...]
>>> + port {
>>> + mhl_to_hdmi: endpoint {
>>> + remote-endpoint = <&hdmi_to_mhl>;
>>> + };
>>> + };
>> I'd like to see this have a port to a connector node, too. Possibly
>> that can come later.
>
> MHL standard is connector agnostic, usually MHL wires are routed
> via multi-function microUSB connector, which can serve also for
> USB/charging/UART....
> There is additional logic to determine which cable is currently
> connected, usually
> implemented by extcon driver.
> I am not sure if/how it should be represented in DT. What do you think
> about it?
Probably all the more reason to have a connector defined, but for
muxed connectors I'm not sure how we should handle them and having
both drm connectors and extcon connectors is a problem. Like I said,
it can come later.
Rob
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
