[RFC 4/8] regulator: core: Check enabling bypass respects constraints
From: broonie@kernel.org (Mark Brown)
Date: 2017-04-07 11:22:48
Also in:
linux-devicetree, linux-pm, lkml
From: broonie@kernel.org (Mark Brown)
Date: 2017-04-07 11:22:48
Also in:
linux-devicetree, linux-pm, lkml
On Fri, Apr 07, 2017 at 01:51:52PM +0300, Leonard Crestez wrote:
It currently seems to work how I expect but from your statement it's not clear if it's entirely intentional.
The current behaviour of bypassed regulators is intentional.
quoted
quoted
Or should a bypassed regulator ignore all other requests? One of the behaviors that this patch series relies on is that calling set_voltage on a bypassed regulator propagates this request to the supply and picks the minimum voltage there. An alternative implementation would be to
quoted
Yes, the expectation is that if anything is being changed it won't have any effect until regulation is reenabled but we're not particularly expecting much activity on bypassed regulators.
OK, so it is up to consumers to ensure the supply voltage is acceptable before allowing bypass. If they want to do something clever they should register as a consumer to the supply as well.
No, that's not expected either - one or the other is fine but both isn't expected. What you're looking for here is something logically different to bypass even if the hardware implementation ends up the same. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170407/b4473be6/attachment.sig>