From: Charan Teja Kalla <charan.kalla@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
robin.clark@oss.qualcomm.com, will@kernel.org,
robin.murphy@arm.com, joro@8bytes.org,
dmitry.baryshkov@oss.qualcomm.com
Cc: iommu@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bibek.patro@oss.qualcomm.com
Subject: Re: [PATCH] iommu/arm-smmu: add actlr settings for mdss and fastrpc
Date: Tue, 11 Nov 2025 19:32:31 +0530 [thread overview]
Message-ID: <c4b1df46-e4b6-4d95-971c-7aaf33bd35f1@oss.qualcomm.com> (raw)
In-Reply-To: <eb596f7a-e13b-4edd-8ee7-05424ea3d9e5@oss.qualcomm.com>
On 11/5/2025 2:44 PM, Konrad Dybcio wrote:
>> + { .compatible = "qcom,fastrpc-compute-cb",
>> + .data = (const void *) (PREFETCH_DEEP | CPRE | CMTLB) },
> This will be globally applied to all smmu-v2 targets with fastrpc,
> starting from MSM8996 ending at Kaanapali and everything inbetween
>
> Are these settings always valid?
Oops, you are correct...this settings are not always applicable it seems.
Example: lpass compute and cdsp compute node uses the
"qcom,fastrpc-compute-cb", but it is for the later that ACTLR settings
are valid.
Then for these cases, should we be extending the actlr match array with
additional compatible string and then add them in all the device nodes
that require actlr setting? example:
@@ -3119,7 +3119,8 @@ fastrpc {
compute-cb@1 {
- compatible = "qcom,fastrpc-compute-cb";
+ compatible = "qcom,fastrpc-compute-cb",
+ "qcom,fastrpc-compute-cb-actlr";
--- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
+++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
@@ -49,7 +49,7 @@ static const struct of_device_id
qcom_smmu_actlr_client_of_match[] = {
+ { .compatible = "qcom,fastrpc-compute-cb-actlr",
.data = (const void *) (PREFETCH_DEEP | CPRE |
CMTLB) },
{ }
or any other better way, please lmk.
Thanks,
Charan
next prev parent reply other threads:[~2025-11-11 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 7:53 [PATCH] iommu/arm-smmu: add actlr settings for mdss and fastrpc Charan Teja Kalla
2025-11-05 9:14 ` Konrad Dybcio
2025-11-11 7:56 ` Charan Teja Kalla
2025-11-11 14:02 ` Charan Teja Kalla [this message]
2025-11-12 14:02 ` Konrad Dybcio
2025-11-27 11:14 ` Bibek Kumar Patro
2025-12-18 12:02 ` Konrad Dybcio
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=c4b1df46-e4b6-4d95-971c-7aaf33bd35f1@oss.qualcomm.com \
--to=charan.kalla@oss.qualcomm.com \
--cc=bibek.patro@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--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