From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
Rob Clark <robdclark@chromium.org>
Subject: [PATCH 0/3] drm/msm: few small cleanups
Date: Sun, 30 Jun 2019 06:14:40 -0700 [thread overview]
Message-ID: <20190630131445.25712-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
2 and 3 are some early prep-work to deal with bootloader enabled
displays, where we want to avoid runpm get/put cycles until we know
that we won't -EPROBE_DEFER. (Otherwise, it will kill the display,
and it's not terribly nice to kill efifb and leave the user with no
good way to debug what dependency they are missing.)
Rob Clark (3):
drm/msm: don't open-code governor name
drm/msm/dpu: remove dpu_mdss:hwversion
drm/msm/dsi: make sure we have panel or bridge earlier
drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 5 ----
drivers/gpu/drm/msm/dsi/dsi.h | 2 +-
drivers/gpu/drm/msm/dsi/dsi_host.c | 30 ++++++++++++------------
drivers/gpu/drm/msm/dsi/dsi_manager.c | 9 +++----
drivers/gpu/drm/msm/msm_gpu.c | 2 +-
5 files changed, 20 insertions(+), 28 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-30 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 13:14 Rob Clark [this message]
2019-06-30 13:14 ` [PATCH 1/3] drm/msm: don't open-code governor name Rob Clark
2019-07-11 18:46 ` Jordan Crouse
2019-06-30 13:14 ` [PATCH 2/3] drm/msm/dpu: remove dpu_mdss:hwversion Rob Clark
2019-07-11 18:47 ` [Freedreno] " Jordan Crouse
2019-06-30 13:14 ` [PATCH 3/3] drm/msm/dsi: make sure we have panel or bridge earlier Rob Clark
2019-07-02 20:30 ` [Freedreno] " Jeffrey Hugo
2019-07-02 21:29 ` Jeffrey Hugo
2019-07-04 6:39 ` Andrzej Hajda
2019-07-04 14:00 ` Rob Clark
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=20190630131445.25712-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@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).