From: Rob Clark <robdclark@gmail.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
freedreno <freedreno@lists.freedesktop.org>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject:
Date: Wed, 7 Feb 2024 11:54:02 -0800 [thread overview]
Message-ID: <CAF6AEGvmW88vi3Ar6yw81t9X-MOL24NdqyZYjduMBfJoBNq5-A@mail.gmail.com> (raw)
Hi Dave,
A few fixes for v6.8, description below
The following changes since commit d4ca26ac4be0d9aea7005c40df75e6775749671b:
drm/msm/dp: call dp_display_get_next_bridge() during probe
(2023-12-14 09:27:46 +0200)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/msm.git tags/drm-msm-fixes-2024-02-07
for you to fetch changes up to 8d35217149daa33358c284aca6a56d5ab92cfc6c:
drm/msm/mdss: specify cfg bandwidth for SDM670 (2024-01-25 14:36:04 -0800)
----------------------------------------------------------------
Fixes for v6.8-rc4
DPU:
- fix for kernel doc warnings and smatch warnings in dpu_encoder
- fix for smatch warning in dpu_encoder
- fix the bus bandwidth value for SDM670
DP:
- fixes to handle unknown bpc case correctly for DP. The current code was
spilling over into other bits of DP configuration register, had to be
fixed to avoid the extra shifts which were causing the spill over
- fix for MISC0 programming in DP driver to program the correct
colorimetry value
GPU:
- dmabuf vmap fix
- a610 UBWC corruption fix (incorrect hbb)
- revert a commit that was making GPU recovery unreliable
----------------------------------------------------------------
Abhinav Kumar (1):
drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup
Dmitry Baryshkov (1):
drm/msm/mdss: specify cfg bandwidth for SDM670
Kuogee Hsieh (2):
drm/msms/dp: fixed link clock divider bits be over written in
BPC unknown case
drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case
Randy Dunlap (1):
drm/msm/dpu: fix kernel-doc warnings
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 8 ++------
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 3 ++-
drivers/gpu/drm/msm/dp/dp_ctrl.c | 5 -----
drivers/gpu/drm/msm/dp/dp_link.c | 22 ++++++++++++++--------
drivers/gpu/drm/msm/dp/dp_reg.h | 3 +++
drivers/gpu/drm/msm/msm_mdss.c | 1 +
6 files changed, 22 insertions(+), 20 deletions(-)
reply other threads:[~2024-02-07 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAF6AEGvmW88vi3Ar6yw81t9X-MOL24NdqyZYjduMBfJoBNq5-A@mail.gmail.com \
--to=robdclark@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.