[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ba22b1f2-3a9a-0e23-04ee-74e173c531c1@codeaurora.org>
Date: Mon, 28 May 2018 12:59:51 +0530
From: Taniya Das <tdas@...eaurora.org>
To: Viresh Kumar <viresh.kumar@...aro.org>,
Rob Herring <robh@...nel.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-pm@...r.kernel.org, Stephen Boyd <sboyd@...nel.org>,
Rajendra Nayak <rnayak@...eaurora.org>,
Amit Nischal <anischal@...eaurora.org>,
devicetree@...r.kernel.org,
Saravana Kannan <skannan@...eaurora.org>,
Amit Kucheria <amit.kucheria@...aro.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ FW
bindings
Hello Rob,
Could you please suggest if the below looks okay to be implemented?
On 5/24/2018 11:13 AM, Viresh Kumar wrote:
> On 24-05-18, 10:48, Taniya Das wrote:
>> Hello Rob, Viresh,
>>
>> Thank you for the comments. If I understand correctly, the device tree nodes
>> should look something like the below.
>>
>> Though I am not sure if any vendor name could be associated in the cpu
>> nodes.
>
> Well Rob said Yes to that I think.
>
>> Please suggest if my understanding is wrong.
>>
>> cpu@0 {
>> qcom,freq-domain = <&freq_domain_table0>;
>> …
>> };
>>
>> same follows for cpu 1/2/3
>>
>> cpu@400 {
>> qcom,freq-domain = <&freq_domain_table1>;
>> …
>> };
>> same follows for cpu 5/6/7
>>
>> freq_domain_table0 : freq_table {
>> reg = < >, < >, < > ;
>> reg-names = "perf_base", "lut_base", "en_base";
>> };
>>
>> freq_domain_table1 : freq_table {
>> reg = < >, < >, < > ;
>> reg-names = "perf_base", "lut_base", "en_base";
>> };
>
> Mostly yes.
>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
Powered by blists - more mailing lists