On 21-10-20, 15:29, Manivannan Sadhasivam wrote: > Hi, > > On Wed, Oct 21, 2020 at 10:36:43AM +0800, Hector Yuan wrote: > > Hi, Manivannan > > > > On Tue, 2020-10-20 at 21:09 +0530, Manivannan Sadhasivam wrote: > > > Add devicetree documentation for 'qcom,freq-domain' property specific > > > to Qualcomm CPUs. This property is used to reference the CPUFREQ node > > > along with Domain ID (0/1). > > > > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx> > > > --- > > > Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++ > > > 1 file changed, 6 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml > > > index 1222bf1831fa..f40564bf004f 100644 > > > --- a/Documentation/devicetree/bindings/arm/cpus.yaml > > > +++ b/Documentation/devicetree/bindings/arm/cpus.yaml > > > @@ -290,6 +290,12 @@ properties: > > > > > > * arm/msm/qcom,kpss-acc.txt > > > > > > + qcom,freq-domain: > > Do you mind to change "qcom, freq-domain" to common naming? or drop the > > prefix. So that we can use this CPU node and map it to each freq-domain. > > Thanks a lot. > > I can do that but did the domain value match for other platforms as well? I am not sure if you can. The code needs to be backward compatible so it can support all devices shipped with older bootloaders and latest kernels. And so changing the bindings isn't a good idea normally. > > > > > > + $ref: '/schemas/types.yaml#/definitions/phandle-array' > > > + description: | > > > + CPUs supporting freq-domain must set their "qcom,freq-domain" property > > > + with phandle to a cpufreq_hw node followed by the Domain ID(0/1). > > > + > > > rockchip,pmu: > > > $ref: '/schemas/types.yaml#/definitions/phandle' > > > description: | > > -- viresh
