diff options
author | Kevin Chiu <Kevin.Chiu@quantatw.com> | 2018-08-27 11:44:46 +0800 |
---|---|---|
committer | Martin Roth <martinroth@google.com> | 2018-08-28 14:15:57 +0000 |
commit | 328ff7dee02e74d0d4e4107fd58810d0228203b8 (patch) | |
tree | c9aa01b6af4d39b595818b3f7a51eb62cc9d6b6b /src/drivers/i2c/ww_ring | |
parent | 6b5c3c295389ad18577444a0523f64f9ee2c33aa (diff) | |
download | coreboot-328ff7dee02e74d0d4e4107fd58810d0228203b8.tar.xz |
google/grunt: Reset BayHub EMMC freq to SD base CLK 50MHz
Bayhub eMMC controller default runs SD base 50MHz at the first power on.
After boot into OS, mmc kernel driver will config controller to HS200/208MHz
and send MMC CMD21 (tuning block).
But Bayhub PCR register 0x3E4[22] (eMMC MODE select) is not clear
after system warm reset.
So eMMC will still run 208Mhz but there is no block tuning cmd in depthcharge.
It will cause two Sandisk eMMC (SDINBDA4-64G-V/SDINBDA4-32G-V) to fail to
load kernel and trap in 0x5B error (No bootable kernel found on disk).
BUG=b:111964336
BRANCH=master
TEST=emerge-grunt coreboot
Change-Id: Ic080682e67323577c7f0ba4ed08f8adafca620cc
Signed-off-by: Kevin Chiu <Kevin.Chiu@quantatw.com>
Reviewed-on: https://review.coreboot.org/28353
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Martin Roth <martinroth@google.com>
Diffstat (limited to 'src/drivers/i2c/ww_ring')
0 files changed, 0 insertions, 0 deletions