mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rajendra Nayak <rnayak@codeaurora.org>
Cc: Kevin Hilman <khilman@baylibre.com>,
	Rob Herring <robh@kernel.org>, Rafael Wysocki <rjw@rjwysocki.net>,
	ulf.hansson@linaro.org, Viresh Kumar <vireshk@kernel.org>,
	Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@codeaurora.org>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	lina.iyer@linaro.org, sudeep.holla@arm.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property
Date: Mon, 8 May 2017 12:41:46 +0530	[thread overview]
Message-ID: <20170508071146.GG17010@vireshk-i7> (raw)
In-Reply-To: <fd54a7b8-d88f-af70-61a2-f32befac21be@codeaurora.org>

I had a long chat with Rajendra offline and clarified few things..

On 08-05-17, 11:06, Rajendra Nayak wrote:
> On 05/08/2017 09:45 AM, Viresh Kumar wrote:
> > On 06-05-17, 11:58, Kevin Hilman wrote:

> >> I had the same question.  Seems the same comment about an abstract
> >> "index" is needed for voltage also.
> > 
> > Why should we do that? Here are the cases that I had in mind while writing this:
> > 
> > - DT only contains the performance-index and nothing else (i.e. voltages aren't
> >   exposed).
> > 
> >   We wouldn't be required to fill the microvolt property as it is optional.
> 
> So the performance-index is specified in opp-hz property?

Yes, but in the OPP table of the power-domain and not the device. The
device can still have its own OPP table with normal freq/voltage
values (for a separate regulator).

> What if the microcontroller firmware maps the performance-index to voltage but
> expects linux to scale the frequency?

As you clarified on the chat, you were talking about the device here.
It isn't a problem as we will have two separate tables here, one for
the device and one for the domain.

-- 
viresh

  reply	other threads:[~2017-05-08  7:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 10:57 [PATCH V6 0/9] PM / Domains: Implement domain performance states Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Viresh Kumar
2017-04-28 20:48   ` Rob Herring
2017-05-03 11:29     ` Sudeep Holla
2017-05-06  9:39       ` Kevin Hilman
2017-05-08 13:47         ` Sudeep Holla
2017-05-08  7:13       ` Viresh Kumar
2017-05-08 13:57         ` Sudeep Holla
2017-05-09  5:29           ` Viresh Kumar
2017-05-06  9:58     ` Kevin Hilman
2017-05-08  4:15       ` Viresh Kumar
2017-05-08  5:36         ` Rajendra Nayak
2017-05-08  7:11           ` Viresh Kumar [this message]
2017-05-12 14:59         ` Kevin Hilman
2017-05-12 16:18           ` Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 2/9] PM / Domains: Allow OPP table to be used for power-domains Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 3/9] PM / QOS: Keep common notifier list for genpd constraints Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 4/9] PM / QOS: Add DEV_PM_QOS_PERFORMANCE request Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 5/9] PM / OPP: Add support to parse "power-domain-opp" property Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 6/9] PM / OPP: Implement dev_pm_opp_of_add_table_indexed() Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 7/9] PM / domain: Register PM QOS performance notifier Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 8/9] PM / Domain: Add struct device to genpd Viresh Kumar
2017-04-26 10:57 ` [PATCH V6 9/9] PM / Domain: Add support to parse domain's OPP table 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=20170508071146.GG17010@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=lina.iyer@linaro.org \
    --cc=linaro-kernel@lists.linaro.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@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

all inboxes | Powered by JetHome®