[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180718071622.ujb7xm2whryyhu5v@vireshk-i7>
Date: Wed, 18 Jul 2018 12:46:22 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
linaro-kernel <linaro-kernel@...ts.linaro.org>,
Linux PM list <linux-pm@...r.kernel.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Nishanth Menon <nm@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH V3 11/16] cpufreq: dt: Pass regulator name to the OPP core
On 18-07-18, 09:09, Geert Uytterhoeven wrote:
> IMHO they should be documented somewhere, with a link to
> Documentation/devicetree/bindings/regulator/regulator.txt.
> How else can a DTS writer know he/she needs them?
> Without cpu-supply (and clock!) properties, cpufreq can't work.
>
> Candidates:
> - Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
> This has operating points without clocks nor cpu-supply, but with
> clock-latency (for which clock? ;-)
> - Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt
> Again, operating points without clocks nor cpu-supply, but with
> clock-latency.
Sounds reasonable. Will cook patches for that soon. Thanks.
--
viresh
Powered by blists - more mailing lists