[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokXT3m0jnX4R25gzcJUAf_HFj15MueOD2mhG6DRF-0uvg@mail.gmail.com>
Date: Mon, 2 Mar 2015 11:46:54 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Leo Yan <leo.yan@...aro.org>
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Dan Zhao <dan.zhao@...ilicon.com>, zhenwei.wang@...ilicon.com,
mohaoju@...ilicon.com,
devicetree-discuss <devicetree-discuss@...ts.ozlabs.org>,
Rob Herring <rob.herring@...aro.org>
Subject: Re: [PATCH 2/2] dt-bindings: cpufreq: document for hisilicon acpu driver
For bindings you need to cc DT list, cc'd now..
On 26 February 2015 at 18:51, Leo Yan <leo.yan@...aro.org> wrote:
> This adds documentation for hisilicon acpu's cpufreq driver.
>
> OPP library is used for device tree parsing to get frequency list;
> Furthermore, this driver can bind all CPUs to change frequency together,
> or the two clusters can trigger the frequency change independently. This
> is controlled by the dtb flag "hisilicon,coupled-clusters".
>
> Signed-off-by: Leo Yan <leo.yan@...aro.org>
> ---
> .../bindings/cpufreq/cpufreq-hisi-acpu.txt | 112 +++++++++++++++++++++
> 1 file changed, 112 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-hisi-acpu.txt
Bindings must be added before using them and so this patch should have been 1/2.
Apart from that, it looks like you can reuse cpufreq-dt easily without
much trouble.
> +- hisilicon,coupled-clusters: Specify whether all clusters share one clock
> + source. This must be defined under node cpufreq.
> +cpufreq {
> + compatible = "hisilicon,hisi-acpu-cpufreq";
> + hisilicon,coupled-clusters = <1>;
> +};
Such virtual nodes aren't allowed in DT.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists