Re: [PATCH 2/2] regulator: core: Ensure we are at least in bounds for our constraints

Mark Brown
2016-03-29T18:27:50Z

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

On Tue, Mar 29, 2016 at 08:05:34PM +0200, Geert Uytterhoeven wrote:

> sh_mobile_sdhi ee100000.sd: Got WP GPIO
> ======> sh_mobile_sdhi ee100000.sd: could not set regulator OCR (-22)
> gpio_rcar e6055400.gpio: sense irq = 6, type = 3
> sh_mobile_sdhi ee100000.sd: mmc0 base at 0xee100000 clock rate 97 MHz

> The line marked with the arrow is introduced by the changed check, and looks
> to be the origin of the failure.

This isn't making any sense. Why would a change in how we apply voltage
constraints on initial probe of the regulator have an impact here? The
changed code shouldn't even be executing at the point where the SDHCI
driver is trying to use the regulator. There's something else going on
here.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]