On Fri, 13 Jan 2023 at 17:26, Rob Herring <robh@xxxxxxxxxx> wrote: > > > On Fri, 13 Jan 2023 10:37:10 +0200, Dmitry Baryshkov wrote: > > Convert the mdp5.txt into the yaml format. Changes to the existing (txt) schema: > > - MSM8996 has additional "iommu" clock, define it separately > > - Add new properties used on some of platforms: > > - interconnects, interconnect-names > > - iommus > > - power-domains > > - operating-points-v2, opp-table > > > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > > --- > > .../devicetree/bindings/display/msm/mdp5.txt | 132 ----------------- > > .../bindings/display/msm/qcom,mdp5.yaml | 138 ++++++++++++++++++ > > 2 files changed, 138 insertions(+), 132 deletions(-) > > delete mode 100644 Documentation/devicetree/bindings/display/msm/mdp5.txt > > create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,mdp5.yaml > > > > Running 'make dtbs_check' with the schema in this patch gives the > following warnings. Consider if they are expected or the schema is > incorrect. These may not be new warnings. > > Note that it is not yet a requirement to have 0 warnings for dtbs_check. > This will change in the future. > > Full log is available here: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230113083720.39224-2-dmitry.baryshkov@xxxxxxxxxx > > > mdp@1a01000: compatible:0: 'qcom,mdp5' was expected > arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dtb > > mdp@1a01000: compatible: ['qcom,msm8953-mdp5', 'qcom,mdp5'] is too long > arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dtb This is because we ended up in the middle of the conversion. msm8953 ended up using a new style of bindings, while the rest used old ones. This is fixed by the patch 02 (which adds SoC-specific compatibles to the schema) and patches 6 and 7 that convert the rest of DT. -- With best wishes Dmitry
