From: Bibek Kumar Patro <quic_bibekkum@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <will@kernel.org>,
<robin.murphy@arm.com>, <joro@8bytes.org>,
<dmitry.baryshkov@linaro.org>, <a39.skl@gmail.com>,
<quic_saipraka@quicinc.com>, <quic_pkondeti@quicinc.com>,
<quic_molvera@quicinc.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>,
<qipl.kernel.upstream@quicinc.com>
Subject: Re: [PATCH 2/3] iommu/arm-smmu: add ACTLR data and support for SM8550
Date: Mon, 6 Nov 2023 11:56:42 +0530 [thread overview]
Message-ID: <5fb7b0ac-8cd5-4fa2-ad0f-ddce5588e805@quicinc.com> (raw)
In-Reply-To: <27b4a561-a2af-47a4-912e-6ee6961f0f6b@linaro.org>
On 11/4/2023 4:59 PM, Konrad Dybcio wrote:
>
>
> On 11/3/23 22:51, Bibek Kumar Patro wrote:
>> Add ACTLR data table for SM8550 along with support for
>> same including SM8550 specific implementation operations.
>>
>> Signed-off-by: Bibek Kumar Patro <quic_bibekkum@quicinc.com>
>> ---
>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 85 +++++++++++++++++++++-
>> 1 file changed, 81 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> index 68c1f4908473..590b7c285299 100644
>> --- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> +++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> @@ -25,6 +25,64 @@ struct actlr_data {
>> u32 actlr;
>> };
>>
>> +static const struct actlr_data sm8550_apps_actlr_data[] = {
> I assume this data will be different for each SoC.. perhaps
> moving this to a separate file (not sure if dt makes sense if
> it's hardcoded per platform) makes sense.
>
Yes, this data will be different for each SoC.
Right, adding these properties in dt won't be a right thing
since this is a register setting and not a hardware defining property.
As per my understanding passing register content via device tree is
highly discouraged, so hosting this data inside the driver.
For reference, adding the RFC link archiving this discussion:
https://lore.kernel.org/all/a01e7e60-6ead-4a9e-ba90-22a8a6bbd03f@quicinc.com/#t
If my recollection is correct, some drivers like llcc is also
following similar implementation
drivers/phy/qualcomm/phy-qcom-qmp-combo.c
drivers/soc/qcom/llcc-qcom.c
> This will also assume that these can not differ between firmware
> versions.
>
Right, these won't differ between firmware versions.
Thanks & regards,
Bibek
> Konrad
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-06 6:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 21:51 [PATCH 0/3] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs Bibek Kumar Patro
2023-11-03 21:51 ` [PATCH 1/3] iommu/arm-smmu: introduction of ACTLR for custom prefetcher settings Bibek Kumar Patro
2023-11-03 22:03 ` Dmitry Baryshkov
2023-11-06 6:12 ` Bibek Kumar Patro
2023-11-14 10:20 ` Bibek Kumar Patro
2023-11-14 10:36 ` Dmitry Baryshkov
2023-11-03 21:51 ` [PATCH 2/3] iommu/arm-smmu: add ACTLR data and support for SM8550 Bibek Kumar Patro
2023-11-03 22:01 ` Dmitry Baryshkov
2023-11-03 22:38 ` Bibek Kumar Patro
2023-11-03 22:41 ` Dmitry Baryshkov
2023-11-06 6:09 ` Bibek Kumar Patro
2023-11-06 9:05 ` Dmitry Baryshkov
2023-11-06 12:09 ` Bibek Kumar Patro
2023-11-10 9:55 ` Pratyush Brahma
2023-11-04 11:29 ` Konrad Dybcio
2023-11-06 6:26 ` Bibek Kumar Patro [this message]
2023-11-04 15:29 ` kernel test robot
2023-11-03 21:51 ` [PATCH 3/3] iommu/arm-smmu: re-enable context caching in smmu reset operation Bibek Kumar Patro
2023-11-03 21:58 ` Dmitry Baryshkov
2023-11-03 22:06 ` Bibek Kumar Patro
2023-11-03 22:23 ` Dmitry Baryshkov
2023-11-03 22:42 ` Bibek Kumar Patro
2023-11-04 11:30 ` Konrad Dybcio
2023-11-06 6:28 ` Bibek Kumar Patro
2023-11-03 22:44 ` [PATCH 0/3] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs Dmitry Baryshkov
2023-11-06 6:39 ` Bibek Kumar Patro
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=5fb7b0ac-8cd5-4fa2-ad0f-ddce5588e805@quicinc.com \
--to=quic_bibekkum@quicinc.com \
--cc=a39.skl@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qipl.kernel.upstream@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_saipraka@quicinc.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