From: Mark Brown <broonie@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regulator: devres: introduce managed enable and disable operations
Date: Tue, 21 Feb 2017 10:56:34 -0800 [thread overview]
Message-ID: <20170221185634.hzlsfap4746qev7u@sirena.org.uk> (raw)
In-Reply-To: <20170221083003.GA21739@dtor-ws>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Tue, Feb 21, 2017 at 12:30:03AM -0800, Dmitry Torokhov wrote:
> On Mon, Feb 20, 2017 at 11:02:58AM -0800, Mark Brown wrote:
> > On Mon, Feb 13, 2017 at 10:51:52AM -0800, Dmitry Torokhov wrote:
> But that is what I meant here about managed action. You are not
> interacting with managed regulator here, you have managed enable. There
> is absolutely nothing preventing you from calling
> devm_regulator_enable() on a regulator that was obtained with
> regulator_get() (i.e. non-managed).
That's not the point, the point is using both devm_regulator_enable()
and regulator_enable() and so on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-02-21 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 2:32 [PATCH v2] regulator: devres: introduce managed enable and disable operations Dmitry Torokhov
2017-02-13 18:01 ` Mark Brown
2017-02-13 18:51 ` Dmitry Torokhov
2017-02-20 19:02 ` Mark Brown
2017-02-21 8:30 ` Dmitry Torokhov
2017-02-21 18:56 ` Mark Brown [this message]
2017-02-23 7:25 ` Dmitry Torokhov
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=20170221185634.hzlsfap4746qev7u@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).