From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Jordan Crouse <jordan@cosmicpenguin.net>,
Jordan Crouse <jcrouse@codeaurora.org>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Rob Clark <robdclark@gmail.com>,
Akhil P Oommen <akhilpo@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] iommu/arm-smmu-qcom: Move the adreno smmu specific impl earlier
Date: Fri, 26 Feb 2021 13:36:33 +0530 [thread overview]
Message-ID: <22bbfd6bb27491adeed18f5d24c42b70@codeaurora.org> (raw)
In-Reply-To: <20210225180652.zwhyjhff3jxm7hcw@cosmicpenguin.net>
On 2021-02-25 23:36, Jordan Crouse wrote:
> On Thu, Feb 25, 2021 at 03:54:10PM +0530, Sai Prakash Ranjan wrote:
>> Adreno(GPU) SMMU and APSS(Application Processor SubSystem) SMMU
>> both implement "arm,mmu-500" in some QTI SoCs and to run through
>> adreno smmu specific implementation such as enabling split pagetables
>> support, we need to match the "qcom,adreno-smmu" compatible first
>> before apss smmu or else we will be running apps smmu implementation
>> for adreno smmu and the additional features for adreno smmu is never
>> set. For ex: we have "qcom,sc7280-smmu-500" compatible for both apps
>> and adreno smmu implementing "arm,mmu-500", so the adreno smmu
>> implementation is never reached because the current sequence checks
>> for apps smmu compatible(qcom,sc7280-smmu-500) first and runs that
>> specific impl and we never reach adreno smmu specific implementation.
>>
>> Suggested-by: Akhil P Oommen <akhilpo@codeaurora.org>
>> Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
>> ---
>>
>> Its either this or we add a new compatible for adreno smmu
>> implementing
>> arm,mmu-500 like "qcom,sc7280-adreno-smmu-500".
>>
>> ---
>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> index bea3ee0dabc2..7d0fc2c8e72f 100644
>> --- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> +++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> @@ -345,11 +345,11 @@ struct arm_smmu_device
>> *qcom_smmu_impl_init(struct arm_smmu_device *smmu)
>> {
>> const struct device_node *np = smmu->dev->of_node;
>>
>> - if (of_match_node(qcom_smmu_impl_of_match, np))
>> - return qcom_smmu_create(smmu, &qcom_smmu_impl);
>> -
>> if (of_device_is_compatible(np, "qcom,adreno-smmu"))
>> return qcom_smmu_create(smmu, &qcom_adreno_smmu_impl);
>>
>> + if (of_match_node(qcom_smmu_impl_of_match, np))
>> + return qcom_smmu_create(smmu, &qcom_smmu_impl);
>> +
>
> It would be good to add a comment here explaining the order here so we
> don't accidentally reorganize ourselves back into a problem later.
>
Sure its better, will add it.
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Jordan Crouse <jordan@cosmicpenguin.net>,
Jordan Crouse <jcrouse@codeaurora.org>
Cc: Will Deacon <will@kernel.org>,
Akhil P Oommen <akhilpo@codeaurora.org>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iommu/arm-smmu-qcom: Move the adreno smmu specific impl earlier
Date: Fri, 26 Feb 2021 13:36:33 +0530 [thread overview]
Message-ID: <22bbfd6bb27491adeed18f5d24c42b70@codeaurora.org> (raw)
In-Reply-To: <20210225180652.zwhyjhff3jxm7hcw@cosmicpenguin.net>
On 2021-02-25 23:36, Jordan Crouse wrote:
> On Thu, Feb 25, 2021 at 03:54:10PM +0530, Sai Prakash Ranjan wrote:
>> Adreno(GPU) SMMU and APSS(Application Processor SubSystem) SMMU
>> both implement "arm,mmu-500" in some QTI SoCs and to run through
>> adreno smmu specific implementation such as enabling split pagetables
>> support, we need to match the "qcom,adreno-smmu" compatible first
>> before apss smmu or else we will be running apps smmu implementation
>> for adreno smmu and the additional features for adreno smmu is never
>> set. For ex: we have "qcom,sc7280-smmu-500" compatible for both apps
>> and adreno smmu implementing "arm,mmu-500", so the adreno smmu
>> implementation is never reached because the current sequence checks
>> for apps smmu compatible(qcom,sc7280-smmu-500) first and runs that
>> specific impl and we never reach adreno smmu specific implementation.
>>
>> Suggested-by: Akhil P Oommen <akhilpo@codeaurora.org>
>> Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
>> ---
>>
>> Its either this or we add a new compatible for adreno smmu
>> implementing
>> arm,mmu-500 like "qcom,sc7280-adreno-smmu-500".
>>
>> ---
>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> index bea3ee0dabc2..7d0fc2c8e72f 100644
>> --- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> +++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
>> @@ -345,11 +345,11 @@ struct arm_smmu_device
>> *qcom_smmu_impl_init(struct arm_smmu_device *smmu)
>> {
>> const struct device_node *np = smmu->dev->of_node;
>>
>> - if (of_match_node(qcom_smmu_impl_of_match, np))
>> - return qcom_smmu_create(smmu, &qcom_smmu_impl);
>> -
>> if (of_device_is_compatible(np, "qcom,adreno-smmu"))
>> return qcom_smmu_create(smmu, &qcom_adreno_smmu_impl);
>>
>> + if (of_match_node(qcom_smmu_impl_of_match, np))
>> + return qcom_smmu_create(smmu, &qcom_smmu_impl);
>> +
>
> It would be good to add a comment here explaining the order here so we
> don't accidentally reorganize ourselves back into a problem later.
>
Sure its better, will add it.
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-02-26 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 10:24 [PATCH 0/2] iommu/arm-smmu-qcom: Add SC7280 support Sai Prakash Ranjan
2021-02-25 10:24 ` Sai Prakash Ranjan
2021-02-25 10:24 ` [PATCH 1/2] iommu/arm-smmu-qcom: Add SC7280 SMMU compatible Sai Prakash Ranjan
2021-02-25 10:24 ` Sai Prakash Ranjan
2021-02-25 10:24 ` [PATCH 2/2] iommu/arm-smmu-qcom: Move the adreno smmu specific impl earlier Sai Prakash Ranjan
2021-02-25 10:24 ` Sai Prakash Ranjan
2021-02-25 18:06 ` Jordan Crouse
2021-02-25 18:06 ` Jordan Crouse
2021-02-25 18:06 ` Jordan Crouse
2021-02-26 8:06 ` Sai Prakash Ranjan [this message]
2021-02-26 8:06 ` Sai Prakash Ranjan
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=22bbfd6bb27491adeed18f5d24c42b70@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=akhilpo@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=jordan@cosmicpenguin.net \
--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=robdclark@gmail.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 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.