Re: [U-Boot] [PATCH 2/4] mmc: fsl_esdhc: Add support to force VSELECT set

On Mon, Feb 16, 2015 at 11:38 PM, Troy Kisky troy.kisky@boundarydevices.com wrote:

On 2/16/2015 2:38 PM, Otavio Salvador wrote:

...

Some boards cannot do voltage negotiation but need to set the VSELECT bit forcely to ensure it to work at 1.8V.

This commit adds CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT flag for this use.

Signed-off-by: Otavio Salvador otavio@ossystems.com.br

...

What if 1 controller needs it set and another needs it clear?

I am not sure it makes much sense to have one in 3V3 and another 1V8. Does it?