From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Charan Teja Kalla <charan.kalla@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: robin.clark@oss.qualcomm.com, will@kernel.org,
robin.murphy@arm.com, joro@8bytes.org, iommu@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] iommu/arm-smmu: add actlr settings for mdss on sa8775p platform
Date: Thu, 20 Nov 2025 13:33:29 +0100 [thread overview]
Message-ID: <09b933ab-eba4-47c2-a667-370dbeda2749@oss.qualcomm.com> (raw)
In-Reply-To: <50bd3be1-63dd-4bf5-915a-02d923fb0376@oss.qualcomm.com>
On 11/19/25 7:06 PM, Charan Teja Kalla wrote:
>
>
> On 11/18/2025 11:33 PM, Dmitry Baryshkov wrote:
>>> Add ACTLR settings for the mdss device on Qualcomm SA8775P platform.
>>> This is achieved by adding compatibility string for mdss in the actlr
>>> client of match table.
>>>
>>> Signed-off-by: Charan Teja Kalla <charan.kalla@oss.qualcomm.com>
>>> ---
>>>
>>> Changed from V1:
>>> 1) Added actlr setting only for MDSS and dropped for fastrpc. -- konrad
>>> 2) ACTLR table is updated per alphanumeric order -- konrad
>>> https://lore.kernel.org/all/20251105075307.1658329-1-
>>> charan.kalla@oss.qualcomm.com/
>>>
>>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>>> index 62874b18f645..0b400e22cb00 100644
>>> --- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>>> +++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>>> @@ -41,6 +41,8 @@ static const struct of_device_id qcom_smmu_actlr_client_of_match[] = {
>>> .data = (const void *) (PREFETCH_DEEP | CPRE | CMTLB) },
>>> { .compatible = "qcom,fastrpc",
>>> .data = (const void *) (PREFETCH_DEEP | CPRE | CMTLB) },
>>> + { .compatible = "qcom,sa8775p-mdss",
>>> + .data = (const void *) (PREFETCH_DEFAULT | CMTLB) },
>> What's the difference from SC7280? Why don't we need to set CPRE?
>
> Sorry, I'm really not sure If your question imply to talk about the IP
> level difference compared to SC7280 for mdss?
"SC7280 has MDSS, SA8775P also has (a slightly different) MDSS, is there
a reason these two have different settings"
> Regarding why don't we need CPRE -- these are QoS settings that does
> control how well hw behaves i.e., related to performance settings not
> the functional ones. I guess, these settings are derived from factors
> like how many masters are sharing a TBU, how crucial are masters using
> that TBU(like important ones may be allowed to +7 or +15 and may be
> others upto only +1 prefetch).
And this is a good answer
Perhaps you could reword it a little and put in the commit message to
make it clear in case anyone has the same question in a year or so
Konrad
next prev parent reply other threads:[~2025-11-20 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 17:18 Charan Teja Kalla
2025-11-18 18:03 ` Dmitry Baryshkov
2025-11-19 18:06 ` Charan Teja Kalla
2025-11-20 12:33 ` Konrad Dybcio [this message]
2025-11-21 16:40 ` 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=09b933ab-eba4-47c2-a667-370dbeda2749@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=charan.kalla@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=will@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®