From: Sam Ravnborg <sam@ravnborg.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org,
Jernej Skrabec <jernej.skrabec@siol.net>,
Neil Armstrong <narmstrong@baylibre.com>,
David Airlie <airlied@linux.ie>, Jonas Karlman <jonas@kwiboo.se>,
Andrzej Hajda <a.hajda@samsung.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH v4 0/2] Add LT9611UXC DSI to HDMI bridge support
Date: Sat, 7 Nov 2020 12:05:26 +0100 [thread overview]
Message-ID: <20201107110526.GA912360@ravnborg.org> (raw)
In-Reply-To: <20201102011435.1100930-1-dmitry.baryshkov@linaro.org>
Hi Dmitry
On Mon, Nov 02, 2020 at 04:14:33AM +0300, Dmitry Baryshkov wrote:
> Hi,
>
> This series adds support for Lontium LT9611UXC bridge chip which takes
> MIPI DSI as input and provides HDMI signal as output.
>
> The chip can be found in Qualcomm RB5 platform [1], [2].
>
> [1] https://www.qualcomm.com/products/qualcomm-robotics-rb5-platform
> [2] https://www.thundercomm.com/app_en/product/1590131656070623
>
> Changes since v3:
> - Support for firmware upgrades
> - Simplified modes table to include only used fields (w, h, refresh)
> - Added more entries to display modes table, as more modes are
> supported by the firmware
> - Wait for EDID to be available from the hardware before reading it
> - Do not store EDID in the interim buffer, lowering the size of
> per-device struct
Thanks, driver is now applied to drm-misc-next.
Sam
prev parent reply other threads:[~2020-11-07 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 1:14 [PATCH v4 0/2] Add LT9611UXC DSI to HDMI bridge support Dmitry Baryshkov
2020-11-02 1:14 ` [PATCH v4 1/2] dt-bindings: display: bridge: Add documentation for LT9611UXC Dmitry Baryshkov
2020-11-02 1:14 ` [PATCH v4 2/2] drm: bridge: add support for lontium LT9611UXC bridge Dmitry Baryshkov
2020-11-07 11:05 ` Sam Ravnborg [this message]
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=20201107110526.GA912360@ravnborg.org \
--to=sam@ravnborg.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-arm-msm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.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).