On 06/24/2014 04:01 AM, Stephen Warren wrote:
On 06/23/2014 01:32 AM, Alexandre Courbot wrote:
Input had been disabled by mistake on these pins, leading to issues with
SDIO devices like the Wifi module not being probed or random errors
occuring on the SD card.
I thought the host controller always drove the clock, so there should be
no need for the pin's input path to be enabled. Perhaps it depends on
the transfer mode (e.g. UHS)?
That's what I thought too, so I went against what was done downstream
and disabled input mode. Eventually noticed various issues with MMC
devices, reverted to the downstream settings and noticed my problems
were solved by this single change.
If this fix is valid, perhaps Jetson TK1's sdmmc3_clk and Venice2's
sdmmc1_clk need the same fix, although we'll need to file bugs against
their pinmux spreadsheets first if that's the case.
Are we having MMC issues with Jetson? I haven't noticed anything
recently, and I have been using both eMMC and SD card.
Anyway, at least for SHIELD, this change seems to be valid.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
