From: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Mike Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC v1] regulator: core: introduce regulator chain locking scheme
Date: Mon, 15 Apr 2013 19:21:25 +0300 [thread overview]
Message-ID: <516C2905.8000200@ti.com> (raw)
In-Reply-To: <20130415155040.GD15837@opensource.wolfsonmicro.com>
Hi Mark,
On 04/15/2013 06:50 PM, Mark Brown wrote:
>> In addition, such locking scheme allows to have access to the supplier
>> regulator API from inside child's (consumer) regulator API.
> I've still not seen any use case articulated for doing this...
Use case is introduced in ABB series:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg88293.html
During voltage scaling we would like to have the following sequence:
cpufreq_cpu0
|
|---> set_voltage(ABB)
|
|->set_voltage(AVS)
|
|-->set_voltage(smps123)
Where smps123 is a regulator, connected ot i2c bus. In this particular
case "regulator chain" guarantees proper order of calls of voltage
scaling sequence.
Regards,
Andrii
WARNING: multiple messages have this Message-ID (diff)
From: andrii.tseglytskyi@ti.com (Andrii Tseglytskyi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v1] regulator: core: introduce regulator chain locking scheme
Date: Mon, 15 Apr 2013 19:21:25 +0300 [thread overview]
Message-ID: <516C2905.8000200@ti.com> (raw)
In-Reply-To: <20130415155040.GD15837@opensource.wolfsonmicro.com>
Hi Mark,
On 04/15/2013 06:50 PM, Mark Brown wrote:
>> In addition, such locking scheme allows to have access to the supplier
>> regulator API from inside child's (consumer) regulator API.
> I've still not seen any use case articulated for doing this...
Use case is introduced in ABB series:
http://www.mail-archive.com/linux-omap at vger.kernel.org/msg88293.html
During voltage scaling we would like to have the following sequence:
cpufreq_cpu0
|
|---> set_voltage(ABB)
|
|->set_voltage(AVS)
|
|-->set_voltage(smps123)
Where smps123 is a regulator, connected ot i2c bus. In this particular
case "regulator chain" guarantees proper order of calls of voltage
scaling sequence.
Regards,
Andrii
WARNING: multiple messages have this Message-ID (diff)
From: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
Mike Turquette <mturquette@linaro.org>,
Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC v1] regulator: core: introduce regulator chain locking scheme
Date: Mon, 15 Apr 2013 19:21:25 +0300 [thread overview]
Message-ID: <516C2905.8000200@ti.com> (raw)
In-Reply-To: <20130415155040.GD15837@opensource.wolfsonmicro.com>
Hi Mark,
On 04/15/2013 06:50 PM, Mark Brown wrote:
>> In addition, such locking scheme allows to have access to the supplier
>> regulator API from inside child's (consumer) regulator API.
> I've still not seen any use case articulated for doing this...
Use case is introduced in ABB series:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg88293.html
During voltage scaling we would like to have the following sequence:
cpufreq_cpu0
|
|---> set_voltage(ABB)
|
|->set_voltage(AVS)
|
|-->set_voltage(smps123)
Where smps123 is a regulator, connected ot i2c bus. In this particular
case "regulator chain" guarantees proper order of calls of voltage
scaling sequence.
Regards,
Andrii
next prev parent reply other threads:[~2013-04-15 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:03 [RFC v1 0/1] introduce regulator chain locking scheme Grygorii Strashko
2013-04-15 13:03 ` Grygorii Strashko
2013-04-15 13:03 ` [RFC v1] regulator: core: " Grygorii Strashko
2013-04-15 13:03 ` Grygorii Strashko
2013-04-15 13:03 ` Grygorii Strashko
2013-04-15 15:50 ` Mark Brown
2013-04-15 15:50 ` Mark Brown
2013-04-15 16:21 ` Andrii Tseglytskyi [this message]
2013-04-15 16:21 ` Andrii Tseglytskyi
2013-04-15 16:21 ` Andrii Tseglytskyi
2013-04-15 16:40 ` Mark Brown
2013-04-15 16:40 ` Mark Brown
2013-04-18 16:29 ` Grygorii Strashko
2013-04-18 16:29 ` Grygorii Strashko
2013-04-18 16:29 ` Grygorii Strashko
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=516C2905.8000200@ti.com \
--to=andrii.tseglytskyi@ti.com \
--cc=broonie@kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=t-kristo@ti.com \
/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.