From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
devicetree@vger.kernel.org, robh@kernel.org,
skannan@codeaurora.org, linux-arm-msm@vger.kernel.org,
evgreen@google.com, Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH v12 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ Firmware bindings
Date: Fri, 14 Dec 2018 09:39:39 +0530 [thread overview]
Message-ID: <822086a5-a3ca-f44c-33be-5a51894f39d5@codeaurora.org> (raw)
In-Reply-To: <154468968610.19322.9386616050590076502@swboyd.mtv.corp.google.com>
Hello Stephen,
On 12/13/2018 1:58 PM, Stephen Boyd wrote:
> Quoting Taniya Das (2018-12-12 23:49:53)
>> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
>> new file mode 100644
>> index 0000000..2b82965
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
>> @@ -0,0 +1,172 @@
> [...]
>> +- reg-names
>> + Usage: Optional
>> + Value type: <string>
>> + Definition: Frequency domain name i.e.
>> + "freq-domain0", "freq-domain1".
>> +
>> +- freq-domain-cells:
>
> Should be #freq-domain-cells? Or maybe #qcom,freq-domain-cells?
>
Updated in the next series.
>> + Usage: required.
>> + Definition: Number of cells in a freqency domain specifier.
>> +
>> +* Property qcom,freq-domain
>> +Devices supporting freq-domain must set their "qcom,freq-domain" property with
>> +phandle to a cpufreq_hw followed by the Domain ID(0/1) in the CPU DT node.
>> +
>> +
--
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-12-14 4:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 7:49 [PATCH v12 0/2] cpufreq: qcom-hw: Add support for QCOM cpufreq HW Taniya Das
2018-12-13 7:49 ` [PATCH v12 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ Firmware bindings Taniya Das
2018-12-13 8:28 ` Stephen Boyd
2018-12-14 4:09 ` Taniya Das [this message]
2018-12-13 7:49 ` [PATCH v12 2/2] cpufreq: qcom-hw: Add support for QCOM cpufreq HW driver Taniya Das
2018-12-13 9:13 ` Viresh Kumar
2018-12-13 9:58 ` Stephen Boyd
2018-12-13 10:05 ` Viresh Kumar
2018-12-13 10:12 ` Stephen Boyd
2018-12-13 10:14 ` Viresh Kumar
2018-12-13 10:32 ` Stephen Boyd
2018-12-13 10:36 ` Viresh Kumar
2018-12-18 5:45 ` Viresh Kumar
2018-12-18 19:13 ` Stephen Boyd
2018-12-19 5:44 ` Viresh Kumar
2018-12-14 4:10 ` Taniya Das
2018-12-13 19:43 ` Matthias Kaehlcke
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=822086a5-a3ca-f44c-33be-5a51894f39d5@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@google.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.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;
as well as URLs for NNTP newsgroup(s).