[coreboot-gerrit] Patch merged into coreboot/master: f3d5736 veyron: Change eMMC enable pin to be pulled (not driven) high

[gerrit at coreboot.org]

the following patch was just integrated into master:
commit f3d5736c8f079321af3cc8dc7210dc0b1a05a327
Author: Doug Anderson <dianders at chromium.org>
Date:   Tue Oct 28 14:09:47 2014 -0700

    veyron: Change eMMC enable pin to be pulled (not driven) high
    
    The eMMC enable pin is in a 3.3V IO domain.  Unfortunately the eMMC
    expects this pin to be 1.8V.  The way we were driving this pin would
    cause the eMMC to pull power through this pin and that was causing
    current leaks.
    
    In future revisions of hardware we should move this pin somewhere more
    legit.  However, in the current hardware we can get things working
    pretty well by using a pullup to "drive" this pin.  This will work in
    conjunction with the external 100K pullup to give a somewhat
    reasonable voltage.  The eMMC will also not be able to pull much
    current through this pin, so it can't leak too badly.
    
    BRANCH=none
    BUG=chrome-os-partner:33319
    TEST=Boot a kernel that doesn't touch the mux/pulls and see no leak:
         dut-control --port=${SERVO} vcc_flash_ma -t 5
    
    Change-Id: Ibc25cd090d826c8215be24a0b5c11d97b5281700
    Signed-off-by: Patrick Georgi <pgeorgi at chromium.org>
    Original-Commit-Id: 26e7a9d7e067ed4dd859387ee63bf654ab9dc529
    Original-Change-Id: Iadfc1477cd478773cc9d159e3fbc22b66b8f0f78
    Original-Signed-off-by: Doug Anderson <dianders at chromium.org>
    Original-Reviewed-on: https://chromium-review.googlesource.com/226039
    Original-Reviewed-by: Julius Werner <jwerner at chromium.org>
    Reviewed-on: http://review.coreboot.org/9545
    Tested-by: build bot (Jenkins)
    Reviewed-by: Stefan Reinauer <stefan.reinauer at coreboot.org>


See http://review.coreboot.org/9545 for details.

-gerrit