On Wed, Mar 09, 2022 at 08:45:40PM +0530, Manivannan Sadhasivam wrote: > Qcom CPUFREQ HW don't have the support for generic performance domains yet. > So use MediaTek CPUFREQ HW that has the support available in mainline. > > This also silences the below dtschema warnings for "cpufreq-qcom-hw.yaml": > > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml: performance-controller@12340000: reg: [[305397760, 4096]] is too short > From schema: Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml: performance-controller@12340000: 'clocks' is a required property > From schema: Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml: performance-controller@12340000: 'clock-names' is a required property > From schema: Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml: performance-controller@12340000: '#freq-domain-cells' is a required property > From schema: Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml: performance-controller@12340000: '#performance-domain-cells' does not match any of the regexes: 'pinctrl-[0-9]+' > From schema: Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml > > Cc: Hector Yuan <hector.yuan@xxxxxxxxxxxx> > Cc: Sudeep Holla <sudeep.holla@xxxxxxx> Thanks for fixing this. It seem to have slipped through the cracks. I had plans to push this once Mediatek driver was merged but totally forgot about it. Acked-by: Sudeep Holla <sudeep.holla@xxxxxxx> -- Regards, Sudeep
