Krzysztof Kozlowski <krzk@xxxxxxxxxx> 于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>;
+ };
