From: Konrad Dybcio <konradybcio@kernel.org>
To: Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Matthias Kaehlcke <mka@chromium.org>,
Sravanthi Kollukuduru <skolluku@codeaurora.org>,
Rajesh Yadav <ryadav@codeaurora.org>,
Chandan Uddaraju <chandanu@codeaurora.org>,
Jeykumar Sankaran <jsanka@codeaurora.org>,
Vara Reddy <quic_varar@quicinc.com>,
Stephen Boyd <swboyd@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Archit Taneja <architt@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Tanmay Shah <tanmay@codeaurora.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: [PATCH 0/3] Remove brownout risks from DPU
Date: Tue, 28 Jul 2026 15:20:44 +0200 [thread overview]
Message-ID: <20260728-topic-dpu_power-v1-0-e7783b859a70@oss.qualcomm.com> (raw)
Things generally run better when plugged in. That also happens to hold
for clocks. To ensure that is the case, remove calls that drop the
performance state votes while the clocks are still running.
This helps Glymur devices not crash upon resume when a display
(incl. the internal one) is plugged in.
The DSI patch is compile-tested only.
Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
---
Konrad Dybcio (3):
drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0)
drm/msm/dp: Drop dev_pm_opp_set_rate(0)
drm/msm/dsi: Drop dev_pm_opp_set_rate(0)
drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c | 4 ++++
drivers/gpu/drm/msm/dp/dp_ctrl.c | 6 +-----
drivers/gpu/drm/msm/dsi/dsi_host.c | 2 --
3 files changed, 5 insertions(+), 7 deletions(-)
---
base-commit: 0d33d21e47d9dc66f91e44da3fc9220c74d93df7
change-id: 20260728-topic-dpu_power-23f5913b1194
Best regards,
--
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
next reply other threads:[~2026-07-28 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 13:20 Konrad Dybcio [this message]
2026-07-28 13:20 ` [PATCH 1/3] drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0) Konrad Dybcio
2026-07-28 13:57 ` Dmitry Baryshkov
2026-07-28 16:40 ` Konrad Dybcio
2026-07-28 13:20 ` [PATCH 2/3] drm/msm/dp: Drop dev_pm_opp_set_rate(0) Konrad Dybcio
2026-07-28 13:56 ` Dmitry Baryshkov
2026-07-28 13:20 ` [PATCH 3/3] drm/msm/dsi: " Konrad Dybcio
2026-07-28 13:55 ` 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=20260728-topic-dpu_power-v1-0-e7783b859a70@oss.qualcomm.com \
--to=konradybcio@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=architt@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=groeck@chromium.org \
--cc=jesszhan0024@gmail.com \
--cc=jsanka@codeaurora.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mka@chromium.org \
--cc=quic_khsieh@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_varar@quicinc.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=ryadav@codeaurora.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=skolluku@codeaurora.org \
--cc=swboyd@chromium.org \
--cc=tanmay@codeaurora.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
all inboxes | Powered by JetHome®