From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Kevin Hilman <khilman@kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values
Date: Thu, 2 Nov 2017 10:19:23 +0530 [thread overview]
Message-ID: <20171102044923.GW4240@vireshk-i7> (raw)
In-Reply-To: <CAL_JsqK-qtAaM_Ou5NtxcWR3F_q=8rMPJUm-VqGtKhbtWe5SAQ@mail.gmail.com>
On 01-11-17, 15:39, Rob Herring wrote:
> On Tue, Oct 31, 2017 at 9:17 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 31 October 2017 at 16:02, Rob Herring <robh+dt@kernel.org> wrote:
> >> Why not a new property for magic values? opp-magic? Don't we want to
> >> know when we have magic values?
> >
> > I have kept a separate property since beginning (domain-performance-state)
> > and moved to using these magic values in the existing field because of the
> > suggestion Kevin gave earlier.
> >
> > https://marc.info/?l=linux-kernel&m=149306082218001&w=2
> >
> > I am not sure what to do now :)
>
> Okay, I guess reusing the properties is fine.
Okay, great.
> >> Wouldn't magic values in opp-hz get propagated to user space?
> >
> > The OPP core puts them in debugfs just to know how the OPPs are
> > set. Otherwise, I am not sure that the power domain core/drivers would
> > be exposing that to user space.
>
> I was thinking thru the cpufreq interface, but I guess this is not for cpus.
Oh no. That's not the target here for sure.
--
viresh
next prev parent reply other threads:[~2017-11-02 4:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:47 [RFC V7 0/2] OPP: Allow OPP table to be used for power-domains Viresh Kumar
2017-10-31 12:47 ` [RFC V7 1/2] " Viresh Kumar
2017-11-28 15:50 ` Ulf Hansson
2017-11-29 16:46 ` Rob Herring
2017-11-30 4:48 ` Viresh Kumar
2017-10-31 12:47 ` [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Viresh Kumar
2017-10-31 16:02 ` Rob Herring
2017-11-01 2:17 ` Viresh Kumar
2017-11-01 20:39 ` Rob Herring
2017-11-01 21:43 ` Stephen Boyd
2017-11-02 4:51 ` Viresh Kumar
2017-11-02 7:15 ` Stephen Boyd
2017-11-02 9:00 ` Viresh Kumar
2017-11-28 16:38 ` Ulf Hansson
2017-11-30 0:50 ` Stephen Boyd
2017-11-30 6:59 ` Viresh Kumar
2017-12-14 7:30 ` Viresh Kumar
2017-12-26 20:23 ` Rob Herring
2017-12-27 4:45 ` Viresh Kumar
2017-12-27 21:36 ` Rob Herring
2017-12-28 4:32 ` Viresh Kumar
2017-11-02 4:49 ` Viresh Kumar [this message]
2017-11-28 16:14 ` Ulf Hansson
2017-11-29 4:14 ` [RFC V7 0/2] OPP: Allow OPP table to be used for power-domains Viresh Kumar
2017-11-29 16:37 ` Rob Herring
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=20171102044923.GW4240@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=vireshk@kernel.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