From: Mark Brown <broonie@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: 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 16:50:40 +0100 [thread overview]
Message-ID: <20130415155040.GD15837@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366031015-17073-2-git-send-email-grygorii.strashko@ti.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Mon, Apr 15, 2013 at 04:03:35PM +0300, Grygorii Strashko wrote:
> To achieve this goal:
> - abstract regulator locking out into helper functions;
> - use the root Regulator (which has no supply defined, like regA) in chain to
> protect the whole chain;
> - implement regulator chain locking scheme as proposed by Thomas Gleixner for CCF
> re-entrance in https://lkml.org/lkml/2013/3/27/171 and in the similar way as
> it is done for CCF by Mike Turquette in https://lkml.org/lkml/2013/3/28/512
Split this into separate refactoring and other change commits - one
change per commit.
> 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...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v1] regulator: core: introduce regulator chain locking scheme
Date: Mon, 15 Apr 2013 16:50:40 +0100 [thread overview]
Message-ID: <20130415155040.GD15837@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366031015-17073-2-git-send-email-grygorii.strashko@ti.com>
On Mon, Apr 15, 2013 at 04:03:35PM +0300, Grygorii Strashko wrote:
> To achieve this goal:
> - abstract regulator locking out into helper functions;
> - use the root Regulator (which has no supply defined, like regA) in chain to
> protect the whole chain;
> - implement regulator chain locking scheme as proposed by Thomas Gleixner for CCF
> re-entrance in https://lkml.org/lkml/2013/3/27/171 and in the similar way as
> it is done for CCF by Mike Turquette in https://lkml.org/lkml/2013/3/28/512
Split this into separate refactoring and other change commits - one
change per commit.
> 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...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130415/b87dbd6a/attachment.sig>
next prev parent reply other threads:[~2013-04-15 15:50 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 [this message]
2013-04-15 15:50 ` Mark Brown
2013-04-15 16:21 ` Andrii Tseglytskyi
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=20130415155040.GD15837@opensource.wolfsonmicro.com \
--to=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.