From: Jun Nie <jun.nie@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
cw00.choi@samsung.com, bryan.odonoghue@linaro.org,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm CCI dt-bindings
Date: Fri, 3 Feb 2023 11:45:31 +0800 [thread overview]
Message-ID: <CABymUCMA9fxGjKAxLhpnSxr92t-oFDfe=mOSiLWb4Jjbzs=n8g@mail.gmail.com> (raw)
In-Reply-To: <957f2bd0-d249-169b-04cc-242b9fcf8c6b@kernel.org>
Krzysztof Kozlowski <krzk@kernel.org> 于2023年2月2日周四 17:42写道:
>
> On 02/02/2023 10:29, Jun Nie wrote:
> >>> +
> >>> +properties:
> >>> + compatible:
> >>> + enum:
> >>> + - qcom,msm8939-cci
> >>> +
> >>> + clocks:
> >>> + maxItems: 1
> >>> +
> >>> + operating-points-v2: true
> >>> + opp-table:
> >>> + type: object
> >>> +
> >>> +required:
> >>> + - compatible
> >>> + - clocks
> >>> + - operating-points-v2
> >>> + - nvmem-cells
> >>
> >> ?? You cannot require properties which are not present.
> >>
> >>> + - power-domains
> >>
> >> Same here.
> >>
> >
> > So the properties should be added later, after cpr and fuse nodes are
> > available in mainline, right?
>
> No, binding should be complete, so why would you skip some properties? I
> don't see here dependency on other bindings. Unless I missed here
> something and there is a dependency? But then what kind? Do you
> reference other schema?
>
> Best regards,
> Krzysztof
>
Sorry, it is a copy/modified error with overlooking some added properties.
+ cci_opp3: opp-cpr14-400000000 {
+ opp-hz = /bits/ 64 <400000000>;
+ opp-supported-hw = <0x1>;
+ required-opps = <&cpr_opp14>;
+ };
+
+ cci_opp4: opp-cpr15-400000000 {
Documentation/devicetree/bindings/interconnect/qcom,cci.example.dtb:
opp-table-cci: Unevaluated properties are not allowed
('opp-cpr14-400000000', 'opp-cpr15-400000000' were unexpected)
Do you know how to fix this dts check warning?
The cci_opp3 and cci_opp4 have the same frequency but with different
requirements to
power domain. So the name of the 2 opp should be identical or with a
different tag, but there
are warnings for both cases for the 2 lines. Thanks!
+ opp-hz = /bits/ 64 <400000000>;
+ opp-supported-hw = <0x3e>;
+ required-opps = <&cpr_opp15>;
+ };
next prev parent reply other threads:[~2023-02-03 3:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 8:02 [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm CCI dt-bindings Jun Nie
2023-02-01 8:02 ` [PATCH 2/2] PM / devfreq: qcom: Introduce CCI devfreq driver Jun Nie
2023-02-01 8:48 ` Krzysztof Kozlowski
2023-02-01 15:15 ` Jun Nie
2023-02-01 10:27 ` Bryan O'Donoghue
2023-02-01 11:02 ` Chanwoo Choi
2023-02-01 15:17 ` Jun Nie
2023-02-01 17:18 ` Dmitry Baryshkov
2023-02-01 11:32 ` Dmitry Baryshkov
2023-02-01 11:46 ` Bryan O'Donoghue
2023-02-01 13:41 ` Dmitry Baryshkov
2023-02-01 14:45 ` Bryan O'Donoghue
2023-02-01 14:58 ` Dmitry Baryshkov
2023-02-01 15:17 ` Bryan O'Donoghue
2023-02-01 17:12 ` Dmitry Baryshkov
2023-02-01 17:16 ` Bryan O'Donoghue
2023-02-01 17:19 ` Dmitry Baryshkov
2023-02-02 12:55 ` Jun Nie
2023-02-01 15:23 ` Jun Nie
2023-02-01 8:43 ` [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm CCI dt-bindings Krzysztof Kozlowski
2023-02-02 9:29 ` Jun Nie
2023-02-02 9:42 ` Krzysztof Kozlowski
2023-02-03 3:45 ` Jun Nie [this message]
2023-02-03 7:06 ` Krzysztof Kozlowski
2023-02-01 10:46 ` Chanwoo Choi
2023-02-01 14:23 ` Rob Herring
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='CABymUCMA9fxGjKAxLhpnSxr92t-oFDfe=mOSiLWb4Jjbzs=n8g@mail.gmail.com' \
--to=jun.nie@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).