diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2016-06-08 05:07:34 -0700 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2016-06-12 12:19:35 +0800 |
| commit | 58d1fedb1f7d1a65918dcdc82c53f83b4c813368 (patch) | |
| tree | bbd0b27f492c85d65f3efe5f4e19b986701fec76 /arch/avr32 | |
| parent | e264e3cc5be81548c6f102b6b597a474e5bd4f20 (diff) | |
| download | u-boot-58d1fedb1f7d1a65918dcdc82c53f83b4c813368.tar.gz u-boot-58d1fedb1f7d1a65918dcdc82c53f83b4c813368.tar.bz2 u-boot-58d1fedb1f7d1a65918dcdc82c53f83b4c813368.zip | |
x86: baytrail: Change fsp, emmc-boot-mode to "auto"
At present all BayTrail boards configure fsp,emmc-boot-mode to 2,
which means "eMMC 4.1" per FSP documentation. However, eMMC 4.1
only shows up on some early stepping silicon of BayTrail SoC.
Newer stepping SoC integrates an eMMC 4.5 controller. Intel FSP
provides a config option fsp,emmc-boot-mode which tells FSP which
eMMC controller it initializes. Instead of hardcoded to 2, now
we change it to 1 which means "auto".
With this change, MinnowMax board (with a D0 stepping BayTrail SoC)
can see the eMMC 4.5 controller at PCI address 00.17.00 via U-Boot
'pci' command.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch/avr32')
0 files changed, 0 insertions, 0 deletions