[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220307064531.47678-1-manivannan.sadhasivam@linaro.org>
Date: Mon, 7 Mar 2022 12:15:29 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: rafael@...nel.org, viresh.kumar@...aro.org, robh+dt@...nel.org
Cc: bjorn.andersson@...aro.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org,
angelogioacchino.delregno@...ainline.org,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Subject: [PATCH 0/2] Convert Qcom CPUFREQ HW binding to YAML
Hi,
Patch 1/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 2/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@linaro.org/
Manivannan Sadhasivam (2):
dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings
dt-bindings: dvfs: Use MediaTek CPUFREQ HW as an example
.../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
Powered by blists - more mailing lists