On Fri, 2020-09-25 at 15:25 +0800, Hector Yuan wrote: > Hi, Rob sir: > > Yes, my patch follows > Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt way to > define frequency domain. > Is it OK to you if I use the same way to do? > And if there exist any schema problem, please kindly let me know how to > fix it. > > My patch reference > Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml > to use the cpu node. > https://elixir.bootlin.com/linux/v5.9-rc6/source/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml > > Thanks a lot. > Hi, Rob sir: Sorry to bother you, may we know your comment for this. Thanks so much. > On Fri, 2020-09-25 at 11:45 +0530, Viresh Kumar wrote: > > On 25-09-20, 10:27, Hector Yuan wrote: > > > Hi, Viresh & Rob Sir: > > > > > > I will change frequency domain to below and define it in cpufreq_hw > > > schema rather than cpu node. > > > > > > mediatek,freq-domain-0 = <&cpu0>, <&cpu1>; > > > > I think it would be better to do it the standard way we have done it elsewhere. > > i.e. follow Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt, that > > is similar to what you did earlier. > > >
