From: Taniya Das <tdas@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>, Rob Herring <robh@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Amit Nischal <anischal@codeaurora.org>,
devicetree@vger.kernel.org,
Saravana Kannan <skannan@codeaurora.org>,
Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ FW bindings
Date: Mon, 28 May 2018 12:59:51 +0530 [thread overview]
Message-ID: <ba22b1f2-3a9a-0e23-04ee-74e173c531c1@codeaurora.org> (raw)
In-Reply-To: <20180524054333.56vga66xrkfuqtkr@vireshk-i7>
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.
--
next prev parent reply other threads:[~2018-05-28 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 17:34 [PATCH v2 0/2] Add support for QCOM cpufreq FW driver Taniya Das
2018-05-19 17:34 ` [PATCH v2 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ FW bindings Taniya Das
2018-05-22 19:31 ` Rob Herring
2018-05-23 5:48 ` Viresh Kumar
2018-05-23 14:18 ` Rob Herring
2018-05-24 5:18 ` Taniya Das
2018-05-24 5:43 ` Viresh Kumar
2018-05-28 7:29 ` Taniya Das [this message]
2018-05-23 15:13 ` Sudeep Holla
2018-05-24 5:46 ` Taniya Das
2018-05-19 17:34 ` [PATCH v2 2/2] cpufreq: qcom-fw: Add support for QCOM cpufreq FW driver Taniya Das
2018-05-21 9:01 ` Viresh Kumar
2018-05-21 19:06 ` skannan
2018-05-22 10:43 ` Taniya Das
2018-05-23 5:54 ` Viresh Kumar
2018-05-21 6:05 ` [PATCH v2 0/2] " Viresh Kumar
2018-05-21 7:35 ` Taniya Das
2018-05-21 9:02 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba22b1f2-3a9a-0e23-04ee-74e173c531c1@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=amit.kucheria@linaro.org \
--cc=anischal@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=skannan@codeaurora.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome