From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
<~postmarketos/upstreaming@lists.sr.ht>,
<phone-devel@vger.kernel.org>, "Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: ufs: qcom: Add reg-names property for ICE
Date: Fri, 09 Dec 2022 16:11:59 +0100 [thread overview]
Message-ID: <COXDTKRPPU1J.373YHYKBQIN38@otso> (raw)
In-Reply-To: <24fa41d2-87d1-be19-af44-337784b0f0a4@linaro.org>
On Fri Dec 9, 2022 at 4:05 PM CET, Krzysztof Kozlowski wrote:
> On 09/12/2022 15:29, Luca Weiss wrote:
> > The code in ufs-qcom-ice.c needs the ICE reg to be named "ice". Add this
> > in the bindings so the existing dts can validate successfully.
> >
> > Also sm8450 is using ICE since commit 276ee34a40c1 ("arm64: dts: qcom:
> > sm8450: add Inline Crypto Engine registers and clock") so move the
> > compatible to the correct if.
> >
> > Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> > ---
> > (no cover subject)
> >
> > The only remaining validation issues I see is the following on sc8280xp-crd.dtb
> > and sa8540p-ride.dtb:
> >
> > Unevaluated properties are not allowed ('required-opps', 'dma-coherent' were unexpected)
> >
> > Maybe someone who knows something about this can handle this?
> >
> > And the patch adding qcom,sm6115-ufshc hasn't been applied yet.
> > ---
> > Documentation/devicetree/bindings/ufs/qcom,ufs.yaml | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml b/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
> > index f2d6298d926c..58a2fb2c83c3 100644
> > --- a/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
> > +++ b/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
> > @@ -102,7 +102,6 @@ allOf:
> > - qcom,sc8280xp-ufshc
> > - qcom,sm8250-ufshc
> > - qcom,sm8350-ufshc
> > - - qcom,sm8450-ufshc
> > then:
> > properties:
> > clocks:
> > @@ -130,6 +129,7 @@ allOf:
> > - qcom,sdm845-ufshc
> > - qcom,sm6350-ufshc
> > - qcom,sm8150-ufshc
> > + - qcom,sm8450-ufshc
> > then:
> > properties:
> > clocks:
> > @@ -149,6 +149,12 @@ allOf:
> > reg:
> > minItems: 2
> > maxItems: 2
> > + reg-names:
>
> There are no reg-names in top-level, so it's surprising to see its
> customized here. It seems no one ever documented that usage...
From what I can tell, from driver side all devices not using ICE don't
need reg-names, only the "ice" reg is referenced by name in the driver.
I didn't add it top-level because with only one reg I think we're not
supposed to use reg-names, right?
Regards
Luca
>
> > + items:
> > + - const: std
> > + - const: ice
> > + required:
> > + - reg-names
> >
> > - if:
> > properties:
> >
> > ---
> > base-commit: f925116b24c0c42dc6d5ab5111c55fd7f74e8dc7
> > change-id: 20221209-dt-binding-ufs-2d7f64797ff2
> >
> > Best regards,
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-12-09 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 14:29 [PATCH] dt-bindings: ufs: qcom: Add reg-names property for ICE Luca Weiss
2022-12-09 15:05 ` Krzysztof Kozlowski
2022-12-09 15:11 ` Luca Weiss [this message]
2022-12-09 15:19 ` Krzysztof Kozlowski
2022-12-09 19:35 ` Eric Biggers
2022-12-10 11:01 ` Krzysztof Kozlowski
2022-12-09 15:43 ` Johan Hovold
2022-12-09 17:41 ` Rob Herring
2022-12-28 11:50 ` Krzysztof Kozlowski
2022-12-28 11:53 ` Luca Weiss
2022-12-28 11:58 ` Krzysztof Kozlowski
2022-12-28 15:24 ` Luca Weiss
2022-12-29 8:06 ` Krzysztof Kozlowski
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=COXDTKRPPU1J.373YHYKBQIN38@otso \
--to=luca.weiss@fairphone.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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