Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1608386
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode |
| Date | 2017-03-24 14:00 +0100 |
| Message-ID | <towYW-1Hf-21@gated-at.bofh.it> (permalink) |
| References | <tnS5s-5Vz-17@gated-at.bofh.it> <towYW-1Hf-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Wed, Mar 22, 2017 at 06:53:07PM +0200, Leonard Crestez wrote: > + if (anatop_reg->bypass) > + anatop_reg->rdesc.min_dropout_uV = 0; > + else > + anatop_reg->rdesc.min_dropout_uV = LDO_MIN_DROPOUT_UV; No, this is completely broken - you can't expect to randomly change hthe regulator description at runtime behind the back of the framework and expect things to work. If there is a need to do this we need an interface for getting the current value and a way to notify of changes. That said I would not expect the dropout voltage to be considered at all when the regulator is bypassed, since the regulator is not regulating it doesn't need any headroom.
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode Mark Brown <broonie@kernel.org> - 2017-03-24 14:00 +0100
csiph-web