From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@linux.ie>,
Andrzej Hajda <a.hajda@samsung.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Vinod Koul <vkoul@kernel.org>, Sam Ravnborg <sam@ravnborg.org>
Subject: [PATCH v3 0/2] Add LT9611UXC DSI to HDMI bridge support
Date: Wed, 9 Sep 2020 12:28:21 +0300 [thread overview]
Message-ID: <20200909092823.64810-1-dmitry.baryshkov@linaro.org> (raw)
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 v2:
- Squashed connector support into main patch
- Added comment on modes table
- Dropped display timings support, covered by EDID
- Dropped sleep mode support
- Dropped hpd_status reading from ISR handler
- Added "sentinel" comments to empty table entries
Changes since v1:
- Fix whitespaces/indentation
- Support working without DRM_BRIDGE_ATTACH_NO_CONNECTOR
next reply other threads:[~2020-09-09 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 9:28 Dmitry Baryshkov [this message]
2020-09-09 9:28 ` [PATCH v3 1/2] dt-bindings: display: bridge: Add documentation for LT9611UXC Dmitry Baryshkov
2020-09-15 17:14 ` Rob Herring
2020-09-15 17:48 ` Bjorn Andersson
2020-09-09 9:28 ` [PATCH v3 2/2] drm: bridge: add support for lontium LT9611UXC bridge Dmitry Baryshkov
2020-10-17 6:41 ` [PATCH v3 0/2] Add LT9611UXC DSI to HDMI bridge support Sam Ravnborg
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=20200909092823.64810-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-arm-msm@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.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).