diff options
author | Stephen Warren <swarren@nvidia.com> | 2014-05-23 13:24:47 -0600 |
---|---|---|
committer | Pantelis Antoniou <panto@antoniou-consulting.com> | 2014-06-12 15:21:12 +0300 |
commit | a5710920b7b0016c6d83897d251b44922f5ca832 (patch) | |
tree | 08159fdc55478553351155ef7aed7ba3615b3aae /drivers | |
parent | 941944e445193a07dea77787680666db049a14dc (diff) | |
download | u-boot-imx-a5710920b7b0016c6d83897d251b44922f5ca832.zip u-boot-imx-a5710920b7b0016c6d83897d251b44922f5ca832.tar.gz u-boot-imx-a5710920b7b0016c6d83897d251b44922f5ca832.tar.bz2 |
cmd_mmc: make mmc dev always re-probe the HW
Currently, U-Boot behaves as follows:
- Begin with no SD card inserted in "mmc 1"
- Execute: mmc dev 1
- This fails, since there is no card
- User plugs in an SD card
- Execute: mmc dev 1
- This still fails, since the HW isn't reprobed.
With this change, U-Boot behaves as follows:
- Begin with no SD card inserted in "mmc 1"
- Execute: mmc dev 1
- This fails, since there is no card
- User plugs in an SD card
- Execute: mmc dev 1
- The newly present SD card is detected
I know that "mmc rescan" will force the HW to be reprobed, but I feel it
makes more sense if "mmc dev" always reprobes the HW after selecting the
current MMC device. This allows scripts to just execute "mmc dev", and
not have to also execute "mmc rescan" to check for media presense.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions