On 27/04/2022 14:54, Dmitry Baryshkov wrote: > Split tsens properties to the child node of the gcc. This follows the > lead of ipq8064 (which also uses a separate node for tsens) and makes > device tree closer to other platforms, where tsens is a completely > separate device. > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > --- > .../bindings/clock/qcom,gcc-apq8064.yaml | 49 +++++++++---------- > 1 file changed, 22 insertions(+), 27 deletions(-) > > diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml > index bd7b04c75e50..3a8bb5a5b37f 100644 > --- a/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml > +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml > @@ -23,47 +23,42 @@ description: | > > properties: > compatible: > - enum: > - - qcom,gcc-apq8064 > - - qcom,gcc-msm8960 > - > - nvmem-cells: > - minItems: 1 > - maxItems: 2 > - description: > - Qualcomm TSENS (thermal sensor device) on some devices can > - be part of GCC and hence the TSENS properties can also be part > - of the GCC/clock-controller node. > - For more details on the TSENS properties please refer > - Documentation/devicetree/bindings/thermal/qcom-tsens.yaml > - > - nvmem-cell-names: All these properties (and old compatible list) should be rather instead made deprecated:true. These bindings exists since some time, so it's not like refactoring during development. > - minItems: 1 > items: > - - const: calib > - - const: calib_backup > + - enum: > + - qcom,gcc-apq8064 > + - qcom,gcc-msm8960 > + - const: syscon > + > + thermal-sensor: > + type: object > > - '#thermal-sensor-cells': > - const: 1 > + allOf: > + - $ref: /schemas/thermal/qcom-tsens.yaml# No need for allOf and type, just $ref and description. > > required: > - compatible > - - nvmem-cells > - - nvmem-cell-names > - - '#thermal-sensor-cells' > > unevaluatedProperties: false Best regards, Krzysztof
