From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@ti.com>,
Mike Turquette <mturquette@linaro.org>,
Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>,
linux-kernel@vger.kernel.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
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: Thu, 18 Apr 2013 19:29:35 +0300 [thread overview]
Message-ID: <51701F6F.7070206@ti.com> (raw)
In-Reply-To: <20130415164018.GA14064@sirena.org.uk>
On 04/15/2013 07:40 PM, Mark Brown wrote:
> On Mon, Apr 15, 2013 at 07:21:25PM +0300, Andrii Tseglytskyi wrote:
>> 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:
> Sorry, I meant any sensible use case.
Hi Mark,
Thanks for you comments. I'll split it to 3 patches:
- abstract locking out into helper functions;
- introduce regulator chain locking scheme
- allow reentrant calls into the regulator framework (with hope that is
has future,
may be can enable/disable it through constraints)
I understand that Regulator FW is common and wide used and we should
very careful here.
Regards,
- grygorii
prev parent reply other threads:[~2013-04-18 16:29 UTC|newest]
Thread overview: 6+ 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 ` [RFC v1] regulator: core: " Grygorii Strashko
2013-04-15 15:50 ` Mark Brown
2013-04-15 16:21 ` Andrii Tseglytskyi
2013-04-15 16:40 ` Mark Brown
2013-04-18 16:29 ` Grygorii Strashko [this message]
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=51701F6F.7070206@ti.com \
--to=grygorii.strashko@ti.com \
--cc=andrii.tseglytskyi@ti.com \
--cc=broonie@kernel.org \
--cc=broonie@opensource.wolfsonmicro.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 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).