Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1585630
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] regulator: devres: introduce managed enable and disable operations |
| Date | 2017-02-21 20:10 +0100 |
| Message-ID | <tdnZ0-6Ms-3@gated-at.bofh.it> (permalink) |
| References | <taeIx-5Qx-5@gated-at.bofh.it> <tatey-7cr-15@gated-at.bofh.it> <tau0W-7vg-9@gated-at.bofh.it> <td1vs-dn-31@gated-at.bofh.it> <tde9l-8uF-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v2] regulator: devres: introduce managed enable and disable operations Mark Brown <broonie@kernel.org> - 2017-02-20 20:10 +0100
Re: [PATCH v2] regulator: devres: introduce managed enable and disable operations Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-02-21 09:40 +0100
Re: [PATCH v2] regulator: devres: introduce managed enable and disable operations Mark Brown <broonie@kernel.org> - 2017-02-21 20:10 +0100
Re: [PATCH v2] regulator: devres: introduce managed enable and disable operations Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-02-23 08:30 +0100
csiph-web