Hi, Patch 2/2 was submitted separately [1] but Rob's bot reported errors related to the performance domain binding that used Qcom CPUFREQ as an example. But Qcom CPUFREQ driver doesn't support the generic performance domains yet. So I've added a patch 1/2 that fixes the warning by using MediaTek CPUFREQ as the example and added both patches to this series. Thanks, Mani [1] https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20211005044920.78544-1-manivannan.sadhasivam@xxxxxxxxxx/ Changes in v2: * Moved dvfs binding patch to 1/2 for avoiding DT Bot error. * Added Krzysztof to "To" list. Manivannan Sadhasivam (2): dt-bindings: dvfs: Use MediaTek CPUFREQ HW as an example dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings .../bindings/cpufreq/cpufreq-qcom-hw.txt | 172 --------------- .../bindings/cpufreq/cpufreq-qcom-hw.yaml | 201 ++++++++++++++++++ .../bindings/dvfs/performance-domain.yaml | 14 +- 3 files changed, 211 insertions(+), 176 deletions(-) delete mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml -- 2.25.1
