[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ebc98e4b-1f94-e9a5-cad4-0677f4e440f7@nvidia.com>
Date: Tue, 14 Jul 2020 21:44:22 +0530
From: Sumit Gupta <sumitg@...dia.com>
To: Rob Herring <robh@...nel.org>
CC: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
Catalin Marinas <catalin.marinas@....com>,
"Will Deacon" <will@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
<devicetree@...r.kernel.org>, Jon Hunter <jonathanh@...dia.com>,
Timo Alho <talho@...dia.com>,
"open list:THERMAL" <linux-pm@...r.kernel.org>,
linux-tegra <linux-tegra@...r.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
<bbasu@...dia.com>, Mikko Perttunen <mperttunen@...dia.com>,
Sumit Gupta <sumitg@...dia.com>
Subject: Re: [TEGRA194_CPUFREQ PATCH v5 1/4] dt-bindings: arm: Add t194 ccplex
compatible and bpmp property
>>>
>>> The cpus.yaml binding documents what's in 'cpu' nodes, not 'cpus'
>>> node. AIUI, the latter is what you want. You should do your own schema
>>> file here.
>>>
>> Do you mean to change existing file name from 'cpus.yaml' to 'cpu.yaml'
>> and create new 'cpus.yaml' file?
>> I think it's better to incorporate the change in existing 'cpus.yaml'
>> file to keep both cpu@X and cpus node details together. Please suggest.
>
> No, I'm suggesting you create nvidia,tegra194-ccplex.yaml.
>
Have posted new version of only this patch with new schema file.
Please review.
Thanks,
Sumit
Powered by blists - more mailing lists