All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Mark Brown <broonie@kernel.org>, Mike Turquette <mturquette@linaro.org>
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
Date: Mon, 10 Mar 2014 14:25:43 -0500	[thread overview]
Message-ID: <531E11B7.6080109@ti.com> (raw)
In-Reply-To: <20140310180131.GZ28112@sirena.org.uk>

On 03/10/2014 01:01 PM, Mark Brown wrote:
> On Mon, Mar 10, 2014 at 12:41:05PM -0500, Nishanth Menon wrote:
> 
>> The only other options are:
>> a) Abstract it at a higher level at "user drivers", since they are
>> aware of the sequencing needs - but this partially defeats the
>> purpose, unless ofcourse, we do a tricky implementation such as:
>> clk a, b, c -> prenotifiers in a, postnotifiers in c (which as you
>> mentioned is a little trickier to get right).
>> b) introduce a higher level generic dvfs function[1] which does not
>> seem very attractive either.
> 
>> Any other suggestions other than limiting the usage(and documenting it
>> so) and hoping for a future evolution to take this into consideration?
> 
> Something might be doable with telling the clock API about maintianing
> ratios between clocks?  I do think we should have an idea where we'd go
> with such requirements, even if we don't currently handle it, so that we
> can hopefully avoid another round of refactoring everything but it
> doesn't seem 100% essential, just very nice to have.
> 
Mike,
Any suggestions about the above? could we use composite clocks in some
manner here(even though I think the original intent of the same was
not the same)?

-- 
Regards,
Nishanth Menon

WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
Date: Mon, 10 Mar 2014 14:25:43 -0500	[thread overview]
Message-ID: <531E11B7.6080109@ti.com> (raw)
In-Reply-To: <20140310180131.GZ28112@sirena.org.uk>

On 03/10/2014 01:01 PM, Mark Brown wrote:
> On Mon, Mar 10, 2014 at 12:41:05PM -0500, Nishanth Menon wrote:
> 
>> The only other options are:
>> a) Abstract it at a higher level at "user drivers", since they are
>> aware of the sequencing needs - but this partially defeats the
>> purpose, unless ofcourse, we do a tricky implementation such as:
>> clk a, b, c -> prenotifiers in a, postnotifiers in c (which as you
>> mentioned is a little trickier to get right).
>> b) introduce a higher level generic dvfs function[1] which does not
>> seem very attractive either.
> 
>> Any other suggestions other than limiting the usage(and documenting it
>> so) and hoping for a future evolution to take this into consideration?
> 
> Something might be doable with telling the clock API about maintianing
> ratios between clocks?  I do think we should have an idea where we'd go
> with such requirements, even if we don't currently handle it, so that we
> can hopefully avoid another round of refactoring everything but it
> doesn't seem 100% essential, just very nice to have.
> 
Mike,
Any suggestions about the above? could we use composite clocks in some
manner here(even though I think the original intent of the same was
not the same)?

-- 
Regards,
Nishanth Menon

WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Mark Brown <broonie@kernel.org>, Mike Turquette <mturquette@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	<devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <cpufreq@vger.kernel.org>,
	<linux-pm@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-omap@vger.kernel.org>
Subject: Re: [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support
Date: Mon, 10 Mar 2014 14:25:43 -0500	[thread overview]
Message-ID: <531E11B7.6080109@ti.com> (raw)
In-Reply-To: <20140310180131.GZ28112@sirena.org.uk>

On 03/10/2014 01:01 PM, Mark Brown wrote:
> On Mon, Mar 10, 2014 at 12:41:05PM -0500, Nishanth Menon wrote:
> 
>> The only other options are:
>> a) Abstract it at a higher level at "user drivers", since they are
>> aware of the sequencing needs - but this partially defeats the
>> purpose, unless ofcourse, we do a tricky implementation such as:
>> clk a, b, c -> prenotifiers in a, postnotifiers in c (which as you
>> mentioned is a little trickier to get right).
>> b) introduce a higher level generic dvfs function[1] which does not
>> seem very attractive either.
> 
>> Any other suggestions other than limiting the usage(and documenting it
>> so) and hoping for a future evolution to take this into consideration?
> 
> Something might be doable with telling the clock API about maintianing
> ratios between clocks?  I do think we should have an idea where we'd go
> with such requirements, even if we don't currently handle it, so that we
> can hopefully avoid another round of refactoring everything but it
> doesn't seem 100% essential, just very nice to have.
> 
Mike,
Any suggestions about the above? could we use composite clocks in some
manner here(even though I think the original intent of the same was
not the same)?

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2014-03-10 19:25 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 20:32 [RFC PATCH 0/6] PM: introduce voltage domain abstraction Nishanth Menon
2014-02-18 20:32 ` Nishanth Menon
2014-02-18 20:32 ` Nishanth Menon
2014-02-18 20:32 ` [RFC PATCH 1/6] PM / Voltagedomain: Add generic clk notifier handler for regulator based dynamic voltage scaling Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-25  5:51   ` Mike Turquette
2014-02-25  5:51     ` Mike Turquette
2014-02-25  5:51     ` Mike Turquette
2014-02-25 20:56     ` Nishanth Menon
2014-02-25 20:56       ` Nishanth Menon
2014-02-25 20:56       ` Nishanth Menon
2014-02-27  2:34       ` Nishanth Menon
2014-02-27  2:34         ` Nishanth Menon
2014-02-27  2:34         ` Nishanth Menon
2014-02-27  2:34         ` Nishanth Menon
2014-02-27  5:00         ` Mike Turquette
2014-02-27  5:00           ` Mike Turquette
2014-02-27 14:42           ` Nishanth Menon
2014-02-27 14:42             ` Nishanth Menon
2014-02-27 14:42             ` Nishanth Menon
2014-02-27 18:59         ` Felipe Balbi
2014-02-27 18:59           ` Felipe Balbi
2014-02-27 18:59           ` Felipe Balbi
2014-02-18 20:32 ` [RFC PATCH 2/6] cpufreq: cpufreq-cpu0: use clk rate-change notifiers Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32 ` [RFC PATCH 3/6] PM / Voltagedomain: introduce voltage domain driver support Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-24  1:58   ` Mark Brown
2014-02-24  1:58     ` Mark Brown
2014-02-24 14:38     ` Nishanth Menon
2014-02-24 14:38       ` Nishanth Menon
2014-02-24 14:38       ` Nishanth Menon
2014-03-03  3:54       ` Mark Brown
2014-03-03  3:54         ` Mark Brown
2014-03-10 17:11         ` Nishanth Menon
2014-03-10 17:11           ` Nishanth Menon
2014-03-10 17:11           ` Nishanth Menon
2014-03-10 17:22           ` Mark Brown
2014-03-10 17:22             ` Mark Brown
2014-03-10 17:41             ` Nishanth Menon
2014-03-10 17:41               ` Nishanth Menon
2014-03-10 17:41               ` Nishanth Menon
2014-03-10 18:01               ` Mark Brown
2014-03-10 18:01                 ` Mark Brown
2014-03-10 19:25                 ` Nishanth Menon [this message]
2014-03-10 19:25                   ` Nishanth Menon
2014-03-10 19:25                   ` Nishanth Menon
2014-03-19 22:35                   ` Mike Turquette
2014-03-19 22:35                     ` Mike Turquette
2014-02-18 20:32 ` [RFC PATCH 4/6] devicetree: bindings: add documentation for voltagedomain Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32 ` [RFC PATCH 5/6] PM / Voltagedomain: introduce basic voltage domain support for OMAP Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32 ` [RFC PATCH 6/6] devicetree: bindings: voltagedomain: add bindings for OMAP compatible SoCs Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon
2014-02-18 20:32   ` Nishanth Menon

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=531E11B7.6080109@ti.com \
    --to=nm@ti.com \
    --cc=broonie@kernel.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.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.