From: Felix Radensky <felix.r@variscite.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH V2 2/2] drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 driver
Date: Tue, 27 Apr 2021 12:15:13 +0000 [thread overview]
Message-ID: <VE1PR08MB56936A6ECD4335F815F2CCC0F3419@VE1PR08MB5693.eurprd08.prod.outlook.com> (raw)
Hi Marek,
SN65DSI84 also supports single-link LVDS. We have quite a few customers using SN65DSI84 on Variscite SOMs with low resolution single-channel LVDS panels. I think having a DTS binding to indicate the number of links used by SN65DSI84 is more flexible than forcing dual-link mode on all SN65DSI84 users.
Setting "ti,sn65dsi83" compatible when actually SN65DSI84 is used by the board is a bit misleading.
There are also some bridge properties that are currently not supported by the driver and not reflected in the DTS bindings, e.g. RGB666 vs RGB888, Output Format 1 vs Output Format 2. Do you have any plans to support them ?
Thanks a lot for working on this driver, your efforts are much appreciated.
Felix.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2021-04-27 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 12:15 Felix Radensky [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-21 22:31 [PATCH V2 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 bindings Marek Vasut
2021-04-21 22:31 ` [PATCH V2 2/2] drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 driver Marek Vasut
2021-04-23 16:03 ` Loic Poulain
2021-04-28 7:51 ` Frieder Schrempf
2021-04-28 8:13 ` Frieder Schrempf
2021-04-28 9:26 ` Loic Poulain
2021-04-28 9:24 ` Neil Armstrong
2021-04-28 9:49 ` Jagan Teki
2021-04-28 14:18 ` Marek Vasut
2021-04-28 14:16 ` Marek Vasut
2021-04-29 16:27 ` Frieder Schrempf
2021-04-30 8:34 ` Neil Armstrong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VE1PR08MB56936A6ECD4335F815F2CCC0F3419@VE1PR08MB5693.eurprd08.prod.outlook.com \
--to=felix.r@variscite.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).