From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Rob Clark <robdclark@gmail.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, freedreno@lists.freedesktop.org,
stable@kernel.org
Subject: Re: [PATCH v2 0/2] arm64: dts: qcom: sm8[56]50: correct MDSS interconnects
Date: Thu, 26 Dec 2024 22:15:20 -0600 [thread overview]
Message-ID: <173527291942.1467503.6964791268697075537.b4-ty@kernel.org> (raw)
In-Reply-To: <20241026-fix-sm8x50-mdp-icc-v2-0-fd8ddf755acc@linaro.org>
On Sat, 26 Oct 2024 20:59:39 +0300, Dmitry Baryshkov wrote:
> Both SM8550 and SM8650 misuse mdp1-mem interconnect path for the
> LLCC->EBI path, while it should only be used for the MDP->EBI paths.
>
> This kind of misuse can result in bandwidth underflows, possibly
> degrading picture quality as the required memory bandwidth is divided
> between all mdpN-mem paths (and LLCC-EBI should not be a part of such
> division).
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: sm8550: correct MDSS interconnects
commit: b8591df49cde459e3b84cdc0517d7bf92053d244
[2/2] arm64: dts: qcom: sm8650: correct MDSS interconnects
commit: 9fa33cbca3d2842f1f47ed4e5f6574e611dae32b
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-12-27 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 17:59 Dmitry Baryshkov
2024-10-26 17:59 ` [PATCH v2 1/2] arm64: dts: qcom: sm8550: " Dmitry Baryshkov
2024-12-02 14:39 ` Konrad Dybcio
2024-10-26 17:59 ` [PATCH v2 2/2] arm64: dts: qcom: sm8650: " Dmitry Baryshkov
2024-12-30 9:42 ` Neil Armstrong
2024-12-27 4:15 ` Bjorn Andersson [this message]
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=173527291942.1467503.6964791268697075537.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=stable@kernel.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®