From: Marijn Suijten <marijn.suijten@somainline.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: Re: [PATCH] dt-bindings: arm-smmu: disallow clocks when not used
Date: Thu, 22 Dec 2022 14:33:05 +0100 [thread overview]
Message-ID: <20221222133305.txcla3kk6lrqk7sc@SoMainline.org> (raw)
In-Reply-To: <bff48e91-3cdc-a052-9573-3c4271f88e5a@linaro.org>
On 2022-12-22 11:36:16, Krzysztof Kozlowski wrote:
> On 22/12/2022 11:16, Marijn Suijten wrote:
> > Is this missing a cc to linux-arm-msm?
>
> No, it is not (or maybe but then fix MAINTAINERS). The policy is to use
> get_maintainers.pl to CC people.
Yes, that is the question: is it in MANTAINERS and if not, why not?
> > On 2022-12-22 10:23:55, Krzysztof Kozlowski wrote:
> >> Disallow clocks for variants other than:
> >> 1. SMMUs with platform-specific compatibles which list explicit clocks
> >> and clock-names,
> >> 2. SMMUs using only generic compatibles, e.g. arm,mmu-500, which have a
> >> variable clocks on different implementations.
> >>
> >> This requires such variants with platform-specific compatible, to
> >> explicitly list the clocks or omit them, making the binding more
> >> constraint.
> >>
> >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >
> > Reviewed-by: Marijn Suijten <marijn.suijten@somainline.org>
> >
> > But...
> >
> >> ---
> >>
> >> Cc: Marijn Suijten <marijn.suijten@somainline.org>
> >> Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> >> Cc: Konrad Dybcio <konrad.dybcio@linaro.org>
> >> ---
> >> .../devicetree/bindings/iommu/arm,smmu.yaml | 28 +++++++++++++++++++
> >> 1 file changed, 28 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
> >> index 895ec8418465..0d88395e43ad 100644
> >> --- a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
> >> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
> >> @@ -367,6 +367,34 @@ allOf:
> >> - description: interface clock required to access smmu's registers
> >> through the TCU's programming interface.
> >>
> >> + # Disallow clocks for all other platforms with specific compatibles
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + enum:
> >> + - cavium,smmu-v2
> >> + - marvell,ap806-smmu-500
> >> + - nvidia,smmu-500
> >> + - qcom,qcm2290-smmu-500
> >> + - qcom,qdu1000-smmu-500
> >> + - qcom,sc7180-smmu-500
> >
> > Hmm, sc7280 has two SMMUs. The one for Adreno has clocks and a PD, the
>
> sc7280 is not here, so what is the mistake you see?
sc7280 has two IOMMU nodes. One with clocks (should not be in this
list), the other doesn't have clocks (should be in this list).
How do you want to address that?
> > one for APPS has neither. Same story on sm8[12]50. Aren't those going
> > to trip up the other `if` that requires clocks in both scenarios?
>
> They are not here either, so what is the error?
Ditto.
> > Note that the Adreno SMMUs have (or will get when we/Konrad submit
> > support for it) the "qcom,adreno-smmu" compatible to distinguish them.
- Marijn
next prev parent reply other threads:[~2022-12-22 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 9:23 Krzysztof Kozlowski
2022-12-22 10:16 ` Marijn Suijten
2022-12-22 10:36 ` Krzysztof Kozlowski
2022-12-22 13:33 ` Marijn Suijten [this message]
2022-12-22 14:03 ` Krzysztof Kozlowski
2022-12-22 14:47 ` Marijn Suijten
2023-01-04 0:20 ` Rob Herring
2023-01-12 13:53 ` Krzysztof Kozlowski
2023-01-13 9:50 ` Will Deacon
2023-01-19 19:08 ` Will Deacon
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=20221222133305.txcla3kk6lrqk7sc@SoMainline.org \
--to=marijn.suijten@somainline.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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®