Searched hist:"02 ad33aa3a84821c8d9a6c4f167f143f6248b084" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/include/configs/ |
| H A D | tinker_rk3288.h | 26d5ee8f9b29e06272f8bab052b12df90fe7b6f8 Mon Feb 20 03:08:16 UTC 2017 Eddie Cai <eddie.cai.linux@gmail.com> rockchip: tinker: configs: use correct mmc instance as boot target device
We are using wrong mmc instance as boot target device now. below Jaehoon Chung's
patch use mmc alias which correct it. That make tinker board can not find mmc
device. So give it correct mmc device instance.
commit 02ad33aa3a84821c8d9a6c4f167f143f6248b084
Author: Jaehoon Chung <jh80.chung@samsung.com>
Date: Thu Feb 2 13:41:14 2017 +0900
mmc: mmc-uclass: use the fixed devnum with alias node
Signed-off-by: Eddie Cai <eddie.cai.linux@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/drivers/mmc/ |
| H A D | mmc-uclass.c | 02ad33aa3a84821c8d9a6c4f167f143f6248b084 Thu Feb 02 04:41:14 UTC 2017 Jaehoon Chung <jh80.chung@samsung.com> mmc: mmc-uclass: use the fixed devnum with alias node
If there are alias nodes as "mmc", use the devnum as alias index
number.
This patch is for fixing a problem of Exynos4 series.
Problem is the below thing.
Current legacy mode:
EXYNOS DWMMC: 0, SAMSUNG SDHCI: 1
After using DM:
SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
Dev index is swapped.
Then u-boot can't find the kernel image..because it is already set to 0 as mmcdev.
If change from legacy to DM, also needs to touch all exynos4 config file.
For using simply, just supporting the fixed devnum with alias node is better than it.
Usage:
alaise {
....
mmc0 = &sdhci2; /* eMMC */
mmc1 = &sdhci1; /* SD */
...
}
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|