From: Liu Ying <victor.liu@nxp.com>
To: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com, airlied@gmail.com,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, marex@denx.de,
linux-imx@nxp.com, krzysztof.kozlowski@linaro.org
Subject: [PATCH v3 0/2] drm/bridge: fsl-ldb: Add i.MX93 LDB support
Date: Mon, 23 Jan 2023 10:14:47 +0800 [thread overview]
Message-ID: <20230123021449.969243-1-victor.liu@nxp.com> (raw)
Hi,
This patch set aims to add i.MX93 LVDS Display Bridge(LDB) support in
the existing i.MX8mp LDB DRM bridge driver. Same to i.MX8mp LDB, i.MX93
LDB is controlled by mediamix blk-ctrl through two registers. i.MX93
LDB supports only one LVDS channel(channel 0) while i.MX8mp supports at
most two.
Patch 1/2 adds device tree binding for i.MX93 LDB in the existing
fsl,ldb.yaml.
Patch 2/2 adds i.MX93 LDB support in the existing i.MX8mp LDB DRM bridge
driver.
v2->v3:
* Provide comment on LVDS_CTRL_LVDS_EN bit in patch 2/2 when defining
it's macro. (Marek)
* Add Marek's R-b tag on patch 2/2.
v1->v2:
* Drop redundant "device tree binding" from patch 1/2's subject. (Krzysztof)
* Add Krzysztof's A-b tag on patch 1/2.
Liu Ying (2):
dt-bindings: display: bridge: ldb: Add i.MX93 LDB
drm/bridge: fsl-ldb: Add i.MX93 LDB support
.../bindings/display/bridge/fsl,ldb.yaml | 16 +++++-
drivers/gpu/drm/bridge/fsl-ldb.c | 57 ++++++++++++++++---
2 files changed, 63 insertions(+), 10 deletions(-)
--
2.37.1
next reply other threads:[~2023-01-23 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 2:14 Liu Ying [this message]
2023-01-23 2:14 ` [PATCH v3 1/2] dt-bindings: display: bridge: ldb: Add i.MX93 LDB Liu Ying
2023-01-23 2:14 ` [PATCH v3 2/2] drm/bridge: fsl-ldb: Add i.MX93 LDB support Liu Ying
2023-01-23 8:48 ` [PATCH v3 0/2] " 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=20230123021449.969243-1-victor.liu@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=robert.foss@linaro.org \
--cc=robh+dt@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).