linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Mark Brown <broonie@kernel.org>, robh+dt@kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Rajendra Nayak <rnayak@codeaurora.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	ulf.hansson@linaro.org, Kevin Hilman <khilman@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, devicetree@vger.kernel.org
Subject: Re: [PATCH V4 1/9] PM / OPP: Allow OPP table to be used for power-domains
Date: Wed, 3 May 2017 12:21:54 +0100	[thread overview]
Message-ID: <8aacc296-2549-f0b8-ac25-2f4000c084c1@arm.com> (raw)
In-Reply-To: <20170430124917.4m3d237pik7q47f3@sirena.org.uk>



On 30/04/17 13:49, Mark Brown wrote:
> On Thu, Apr 27, 2017 at 10:42:49AM +0100, Sudeep Holla wrote:
>> On 26/04/17 14:55, Mark Brown wrote:
> 
>>> As I'm getting fed up of saying: if the values you are setting are not
>>> voltages and do not behave like voltages then the hardware should not be
>>> represented as a voltage regulator since if they are represented as
>>> voltage regulators things will expect to be able to control them as
>>> voltage regulators.  This hardware is quite clearly providing OPPs
>>> directly, I would expect this to be handled in the OPP code somehow.
> 
>> I agree with you that we need to be absolutely sure on what it actually
>> represents.
> 
>> But as more and more platform are pushing such power controls to
>> dedicated M3 or similar processors, we need abstraction. Though we are
>> controlling hardware, we do so indirectly. Since there were discussions
>> around device tree representing hardware vs platform, I tend to think,
>> we are moving towards platform(something similar to ACPI).
> 
> I don't think there's a meaningful hardware/platform distinction here -
> in terms of what DT is describing the platform bit is just what the
> hardware (the microcontrollers) happen to do, 
> 

Yes agreed. It's similar to PSCI or any other platform firmware IMO.

The question is how do we deal with such controls that needs to be done
via the firmware ? We generally plug-in to the existing framework in
Linux using the existing bindings. Most of the time, much simpler
bindings than the one that present complete hardware description.

> DT doesn't much care about that though.

No sure about that, may be doesn't care about the internals, but we need
to care about interface, no ?

-- 
Regards,
Sudeep

  reply	other threads:[~2017-05-03 11:22 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20  9:32 [PATCH V4 0/9] PM / Domains: Implement domain performance states Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 1/9] PM / OPP: Allow OPP table to be used for power-domains Viresh Kumar
2017-03-24 15:44   ` Rob Herring
2017-04-10  9:25     ` Viresh Kumar
2017-04-10  9:50       ` Viresh Kumar
2017-04-12 16:49   ` Sudeep Holla
2017-04-13  5:37     ` Viresh Kumar
2017-04-13 13:42       ` Sudeep Holla
2017-04-17  5:27         ` Viresh Kumar
2017-04-18 16:01           ` Sudeep Holla
2017-04-19 10:11             ` Viresh Kumar
2017-04-19 11:47             ` Viresh Kumar
2017-04-19 13:58               ` Sudeep Holla
2017-04-20  5:25                 ` Viresh Kumar
2017-04-20  8:23                   ` Ulf Hansson
2017-04-20  9:33                     ` Viresh Kumar
2017-04-20  9:51                     ` Sudeep Holla
2017-04-20  9:43                   ` Sudeep Holla
2017-04-20  9:52                     ` Viresh Kumar
2017-04-23 22:07                       ` Kevin Hilman
2017-04-26  4:32             ` Rajendra Nayak
2017-04-26 13:55               ` Mark Brown
2017-04-27  9:42                 ` Sudeep Holla
2017-04-27 10:50                   ` Rajendra Nayak
2017-04-28  5:00                     ` Viresh Kumar
2017-04-28  9:44                       ` Sudeep Holla
2017-04-28 11:12                         ` Viresh Kumar
2017-04-30 12:49                   ` Mark Brown
2017-05-03 11:21                     ` Sudeep Holla [this message]
2017-05-14  9:55                       ` Mark Brown
2017-04-12 17:05   ` Sudeep Holla
2017-04-13  5:50     ` Viresh Kumar
2017-04-13 13:43       ` Sudeep Holla
2017-04-17  5:33         ` Viresh Kumar
2017-04-18 16:03           ` Sudeep Holla
2017-04-19 10:12             ` Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 2/9] PM / Domains: Use OPP tables " Viresh Kumar
2017-04-12 16:58   ` Sudeep Holla
2017-04-13  6:03     ` Viresh Kumar
2017-04-13 13:45       ` Sudeep Holla
2017-03-20  9:32 ` [PATCH V4 3/9] PM / QOS: Keep common notifier list for genpd constraints Viresh Kumar
2017-04-19 14:06   ` Ulf Hansson
2017-04-20  4:45   ` [PATCH V5 " Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 4/9] PM / QOS: Add DEV_PM_QOS_PERFORMANCE request Viresh Kumar
2017-04-19 14:07   ` Ulf Hansson
2017-04-20  4:34     ` Viresh Kumar
2017-04-20  4:46   ` [PATCH V5 " Viresh Kumar
2017-04-20  6:53     ` Ulf Hansson
2017-03-20  9:32 ` [PATCH V4 5/9] PM / OPP: Add support to parse OPP table for power-domains Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 6/9] PM / OPP: Add dev_pm_opp_find_dps() helper Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 7/9] PM / domain: Register for PM QOS performance notifier Viresh Kumar
2017-04-20  4:46   ` [PATCH V5 " Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 8/9] PM / Domain: Add struct device to genpd Viresh Kumar
2017-03-20  9:32 ` [PATCH V4 9/9] PM / Domain: Add support to parse domain's OPP table Viresh Kumar
2017-04-12 14:24 ` [PATCH V4 0/9] PM / Domains: Implement domain performance states 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=8aacc296-2549-f0b8-ac25-2f4000c084c1@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@linaro.org \
    --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+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=ulf.hansson@linaro.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).