From: Marek Vasut <marex@denx.de>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Claudius Heine <ch@denx.de>,
Douglas Anderson <dianders@chromium.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Stephen Boyd <swboyd@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH V2 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 bindings
Date: Thu, 22 Apr 2021 18:22:15 +0200 [thread overview]
Message-ID: <eadb679b-4fb0-505f-8f56-242fa3ebd1b5@denx.de> (raw)
In-Reply-To: <CAMty3ZB9iHY6-YV7JRrhekR_7yA=m2dgwR=5a+D3=h4hAMi7WQ@mail.gmail.com>
On 4/22/21 10:43 AM, Jagan Teki wrote:
[...]
>> diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
>> new file mode 100644
>> index 000000000000..42d11b46a1eb
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
>> @@ -0,0 +1,134 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/display/bridge/ti,sn65dsi83.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: SN65DSI83 and SN65DSI84 DSI to LVDS bridge chip
>
> Can it possible to wait for my v4 to have dual-link LVDS supported
> which is quite discussing points on previous versions?
This driver already has the dual-link LVDS support on DSI84 and it is
tested on real hardware. So is the single-link LVDS on DSI83, on
multiple hardware instances.
In addition to that, this driver has proper regmap support and constant
time calculation of DSI83/84 clock register settings.
Note that I did wait for your v4 for over two weeks already, it just
didn't materialize, so I determined it might be a good idea to restart
work on this driver instead.
Maybe you can test this driver and check what is missing for your usecase?
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-22 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2021-04-21 22:56 ` [PATCH V2 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 bindings Laurent Pinchart
2021-04-22 8:38 ` Neil Armstrong
2021-04-22 16:16 ` Marek Vasut
2021-04-22 8:43 ` Jagan Teki
2021-04-22 16:22 ` Marek Vasut [this message]
2021-04-28 7:56 ` Frieder Schrempf
2021-04-28 14:19 ` Marek Vasut
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=eadb679b-4fb0-505f-8f56-242fa3ebd1b5@denx.de \
--to=marex@denx.de \
--cc=ch@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=swboyd@chromium.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).