From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: Stephen Boyd <swboyd@chromium.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org
Subject: [RFC PATCH 0/2] drm/msm/mdp4: rework LVDS/LCDC panel support
Date: Thu, 16 Jun 2022 12:03:19 +0300 [thread overview]
Message-ID: <20220616090321.433249-1-dmitry.baryshkov@linaro.org> (raw)
MDP4 uses custom code to handle LVDS panel. It predates handling
EPROBE_DEFER, it tries to work when the panel device is not available,
etc. Switch MDP4 LCDC code to use drm_panel_bridge/drm_bridge_connector
to follow contemporary DRM practices.
Note, this code has been compile-tested only. Testing on the real device
is still pending (and will be performed before the merge).
Dmitry Baryshkov (2):
drm/msm/mdp4: move move_valid callback to lcdc_encoder
drm/msm/mdp4: switch LVDS to use drm_bridge/_connector
drivers/gpu/drm/msm/Makefile | 1 -
drivers/gpu/drm/msm/disp/mdp4/mdp4_kms.c | 32 ++++-
drivers/gpu/drm/msm/disp/mdp4/mdp4_kms.h | 7 +-
.../gpu/drm/msm/disp/mdp4/mdp4_lcdc_encoder.c | 46 +++----
.../drm/msm/disp/mdp4/mdp4_lvds_connector.c | 120 ------------------
5 files changed, 47 insertions(+), 159 deletions(-)
delete mode 100644 drivers/gpu/drm/msm/disp/mdp4/mdp4_lvds_connector.c
--
2.35.1
next reply other threads:[~2022-06-16 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 9:03 Dmitry Baryshkov [this message]
2022-06-16 9:03 ` [RFC PATCH 1/2] drm/msm/mdp4: move move_valid callback to lcdc_encoder Dmitry Baryshkov
2022-06-16 9:03 ` [RFC PATCH 2/2] drm/msm/mdp4: switch LVDS to use drm_bridge/_connector Dmitry Baryshkov
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=20220616090321.433249-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--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