> Make sure that MX51_PAD_GPIO1_1 does not remain configure as > ALT0/SD1_WP (it is out of reset). This is needed because of external > pull-up resistor attached to that pad that, when left unchanged, will > drive SD1_WP high preventing eSDHC1/eMMC from working correctly. > > To fix that add a pinmux configuration line configureing the pad to > function as a GPIO. While we are at it, add a corresponding > output-high GPIO hog in an effort to minimize current consumption. > > Cc: Nikita Yushchenko <nikita.yoush@xxxxxxxxxxxxxxxxxx> > Cc: Shawn Guo <shawnguo@xxxxxxxxxx> > Cc: Fabio Estevam <fabio.estevam@xxxxxxx> > Cc: Lucas Stach <l.stach@xxxxxxxxxxxxxx> > Cc: Chris Healy <cphealy@xxxxxxxxx> > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Cc: devicetree@xxxxxxxxxxxxxxx > Cc: linux-kernel@xxxxxxxxxxxxxxx > Signed-off-by: Andrey Smirnov <andrew.smirnov@xxxxxxxxx> Tested-By: Nikita Yushchenko <nikita.yoush@xxxxxxxxxxxxxxxxxx Tested on 8.9'' RDU1. Without this patch, eMMC does not work, get [ 40.801367] mmc0: Timeout waiting for hardware interrupt. [ 40.806789] mmc0: sdhci: ============ SDHCI REGISTER DUMP =========== ... <dump follows> With this patch, eMMC works correctly. Nikita -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
