From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <abhinavk@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org
Subject: [PATCH v3 0/4] drm/msm/dpu: always use mdp device to scale bandwidth
Date: Tue, 3 Aug 2021 13:16:55 +0300 [thread overview]
Message-ID: <20210803101657.1072358-1-dmitry.baryshkov@linaro.org> (raw)
In 5.13 the DPU driver was changed to vote on the bus bandwidth for all
the soc families, however suggested [1] dts changes were for some reason
not merged at that time. Let's merge them now.
If the bootloader does not setup the bus vote, clock might not be
enabled before the driver votes on the MDP bus bandwidth. Originally bus
votes were static and happened in MDSS hadling code, while now they are
dynamic and are moved to the MDP handling code, thus bus clocks also
should belong to the MDP device.
[1] https://lore.kernel.org/linux-arm-msm/04b4612dfd3f651ead068725409211a0@codeaurora.org/
Changes since v2:
- Dropped merged patches
- Rephrased commit message for sm8250.
Changes since v1:
- Add dts changes as requested by Kalyan Thota
----------------------------------------------------------------
Dmitry Baryshkov (2):
arm64: dts: sdm845: move bus clock to mdp node for sdm845 target
arm64: dts: sm8250: remove bus clock from the mdss node for sm8250 target
arch/arm64/boot/dts/qcom/sdm845.dtsi | 8 ++++----
arch/arm64/boot/dts/qcom/sm8250.dtsi | 3 +--
2 files changed, 5 insertions(+), 6 deletions(-)
next reply other threads:[~2021-08-03 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 10:16 Dmitry Baryshkov [this message]
2021-08-03 10:16 ` [PATCH v3 1/2] arm64: dts: sdm845: move bus clock to mdp node for sdm845 target Dmitry Baryshkov
2021-08-03 10:16 ` [PATCH v3 2/2] arm64: dts: sm8250: remove bus clock from the mdss node for sm8250 target 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=20210803101657.1072358-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=abhinavk@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.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.