summaryrefslogtreecommitdiff
path: root/include/configs/colibri_imx7.h
diff options
context:
space:
mode:
authorMarcel Ziswiler <marcel.ziswiler@toradex.com>2022-02-14 10:46:02 +0100
committerMarcel Ziswiler <marcel.ziswiler@toradex.com>2022-02-14 18:14:39 +0100
commit140ff985b96f631b70254c0fac79e6cf74a0a154 (patch)
tree314b7103e421c1a99db2324e3e6d7a625c9ddb30 /include/configs/colibri_imx7.h
parent421a6ba683f97713dc4f0e445aee48b87bbe18c8 (diff)
board: colibri_imx7_emmc: fix emmc detection
Later Colibri iMX7D V1.1B modules are using a “new” SoC fusing. The difference has to do with whether or not we do enable the boot ROM to enable/use the eMMC reset signal. Depending on that SoC fuse, the boot ROM configures this pin as a GPIO output to actually be able to do/drive the reset signal. Our eMMC vs. NAND detection so far only sets that signal to a GPIO but without explicitly setting any direction as, of course, so far, by default, it was an input. As the boot ROM now sets it as an output we do get back a value of zero instead of a one which would indicate the pull-up being present on eMMC modules. Fix this by setting the SION bit which allows reading back the value even if it is set to be an output by the boot ROM. Note that with the new SoC fusing we now read back what the boot ROM drived rather than the real value caused by the pull-up resistor. However, if it would ever be driven low the eMMC would anyway permanently be reset. Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Diffstat (limited to 'include/configs/colibri_imx7.h')
0 files changed, 0 insertions, 0 deletions