From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Taniya Das <tdas@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
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, skannan@codeaurora.org,
amit.kucheria@linaro.org
Subject: Re: [PATCH v2 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ FW bindings
Date: Wed, 23 May 2018 11:18:46 +0530 [thread overview]
Message-ID: <20180523054846.zn7gftt6aqyibd26@vireshk-i7> (raw)
In-Reply-To: <20180522193139.GA21623@rob-hp-laptop>
On 22-05-18, 14:31, Rob Herring wrote:
> On Sat, May 19, 2018 at 11:04:50PM +0530, Taniya Das wrote:
> > + freq-domain-0 {
> > + compatible = "cpufreq";
> > + reg = <0x17d43920 0x4>,
> > + <0x17d43110 0x500>,
> > + <0x17d41000 0x4>;
> > + reg-names = "perf_base", "lut_base", "en_base";
> > + qcom,cpulist = <&CPU0 &CPU1 &CPU2 &CPU3>;
I was thinking, can't we add platform specific properties in the CPU
nodes ? If yes, then we can point the phandle of fw node from the CPUs
and this awkward list can go away.
--
viresh
next prev parent reply other threads:[~2018-05-23 5:48 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 [this message]
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
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=20180523054846.zn7gftt6aqyibd26@vireshk-i7 \
--to=viresh.kumar@linaro.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=tdas@codeaurora.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).