Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1608386 > unrolled thread

Re: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode

Started byMark Brown <broonie@kernel.org>
First post2017-03-24 14:00 +0100
Last post2017-03-24 14:00 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode Mark Brown <broonie@kernel.org> - 2017-03-24 14:00 +0100

#1608386 — Re: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode

FromMark Brown <broonie@kernel.org>
Date2017-03-24 14:00 +0100
SubjectRe: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode
Message-ID<towYW-1Hf-21@gated-at.bofh.it>

[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.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web