All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	nm@ti.com, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings
Date: Wed, 13 Jan 2016 11:17:50 +0530	[thread overview]
Message-ID: <20160113054750.GD6050@ubuntu> (raw)
In-Reply-To: <20160113004335.GD22188@codeaurora.org>

On 12-01-16, 16:43, Stephen Boyd wrote:
> It's far easier to implement, but not far better. In most designs
> the pin is not called <device_name>-supply, but something more
> mundane like vdd-supply, vddio-supply, vcc-supply, etc. In the
> case of CPUs, there's probably nothing in the datasheets, so cpu
> vs cpu0 is not too important to distinguish here. But for things
> like a GPU, DSP, video encoder, etc. I doubt it's going to be
> called <device_name>-supply, so making that the norm is
> misguided.

I completely agree with that, but here is the usecase:
- A OPP-user driver doesn't need to call any special OPP API and OPP
  layer can allocate the regulator for it using <device>-name. This
  will make all drivers (that follow this nomenclature in DT) very
  simple and straight-forward.
- But then there are drivers, which need special supply-name. They can
  always call opp-set-regulator API to mention that, no one is
  stopping them from that.

And so I still believe, OPP layer has only this option to do it
generically.

Comments ?

-- 
viresh

  reply	other threads:[~2016-01-13  5:47 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 10:16 [PATCH 00/17] PM / OPP: Introduce APIs to transition OPPs Viresh Kumar
2015-12-22 10:16 ` [PATCH 01/17] PM / OPP: get/put regulators from OPP core Viresh Kumar
2016-01-11 23:21   ` Stephen Boyd
2016-01-12  3:05     ` Viresh Kumar
2016-01-12  5:23       ` Viresh Kumar
2016-01-12 19:32         ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 02/17] PM / OPP: Add APIs to set regulator-name Viresh Kumar
2016-01-12  1:18   ` Stephen Boyd
2016-01-12  4:43     ` Viresh Kumar
2015-12-22 10:16 ` [PATCH 03/17] PM / OPP: Disable OPPs that aren't supported by the regulator Viresh Kumar
2016-01-12  1:19   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency() Viresh Kumar
2016-01-12  1:25   ` Stephen Boyd
2016-01-12  5:10     ` Viresh Kumar
2016-01-12 19:45       ` Stephen Boyd
2016-01-13  5:34         ` Viresh Kumar
2016-01-18  7:23           ` Viresh Kumar
2016-01-21  0:20           ` Stephen Boyd
2016-01-21  2:32             ` Viresh Kumar
2016-01-21  2:43               ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 05/17] PM / OPP: Introduce dev_pm_opp_get_max_transition_latency() Viresh Kumar
2016-01-12  2:20   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings Viresh Kumar
2016-01-12  1:29   ` Stephen Boyd
2016-01-12  5:14     ` Viresh Kumar
2016-01-13  0:36       ` Stephen Boyd
2016-01-13  5:35         ` Viresh Kumar
2016-01-15  1:54           ` Stephen Boyd
2016-01-15  1:54   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 07/17] PM / OPP: Manage device clk Viresh Kumar
2016-01-12  1:32   ` Stephen Boyd
2016-01-12  5:43     ` Viresh Kumar
2016-01-12 19:47       ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 08/17] PM / OPP: Add dev_pm_opp_set_rate() Viresh Kumar
2016-01-12  1:40   ` Stephen Boyd
2016-01-12  6:58     ` Viresh Kumar
2016-01-13  0:49       ` Stephen Boyd
2016-01-13  5:51         ` Viresh Kumar
2015-12-22 10:16 ` [PATCH 10/17] cpufreq: dt: Rename 'need_update' to 'opp_v1' Viresh Kumar
2016-01-12  1:41   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 11/17] cpufreq: dt: OPP layers handles clock-latency for V1 bindings as well Viresh Kumar
2016-01-12  1:41   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings Viresh Kumar
2016-01-12  1:53   ` Stephen Boyd
2016-01-12  7:11     ` Viresh Kumar
2016-01-13  0:43       ` Stephen Boyd
2016-01-13  5:47         ` Viresh Kumar [this message]
2016-01-13 11:15           ` Mark Brown
2015-12-22 10:16 ` [PATCH 13/17] cpufreq: dt: Unsupported OPPs are already disabled Viresh Kumar
2016-01-12  1:53   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 14/17] cpufreq: dt: Reuse dev_pm_opp_get_max_transition_latency() Viresh Kumar
2016-01-12  1:54   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 15/17] cpufreq: dt: Use dev_pm_opp_set_rate() to switch frequency Viresh Kumar
2016-01-12  1:55   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 16/17] cpufreq: dt: drop references to DT node Viresh Kumar
2016-01-12  1:55   ` Stephen Boyd
2015-12-22 10:16 ` [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore Viresh Kumar
2016-01-12  2:20   ` Stephen Boyd
2016-01-12  7:34     ` Viresh Kumar
2016-01-21  1:18       ` Stephen Boyd
2016-01-21  2:36         ` Viresh Kumar
2016-01-21  2:45           ` Stephen Boyd
2016-01-25 10:33     ` Viresh Kumar
2015-12-22 10:20 ` [PATCH 09/17] cpufreq: dt: Convert few pr_debug/err() calls to dev_dbg/err() Viresh Kumar
2016-01-12  1:40   ` Stephen Boyd
2015-12-23  3:12 ` [PATCH 00/17] PM / OPP: Introduce APIs to transition OPPs Rafael J. Wysocki
2015-12-23  2:46   ` Viresh Kumar
2016-01-11 16:28 ` 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=20160113054750.GD6050@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=broonie@kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.