summaryrefslogtreecommitdiff
path: root/src/soc/intel/braswell/placeholders.c
diff options
context:
space:
mode:
authorKevin Chiu <Kevin.Chiu@quantatw.com>2020-09-26 20:34:28 +0800
committerFurquan Shaikh <furquan@google.com>2020-10-01 20:15:35 +0000
commit768f59a32ff4a6dc1c8db0e03bb06ece02d20b72 (patch)
tree1ac4cfc74bcf53ae643880948412f97c3f015248 /src/soc/intel/braswell/placeholders.c
parentbbbdba1e50d1fa96708b4ce07f15a36b70244bbb (diff)
mb/google/zork: Configure EMMC_RESET_L to drive high
Configure EMMC_RESET_L (GPIO68) to drive high by default. As per JEDEC specification for eMMC, RST_n_FUNCTION defaults to temporarily disable reset using RST_n signal (which is connected to EMMC_RESET_L on zork). Chrome OS platforms do not configure RST_n_FUNCTION thus making the reset signal unused. The spec also says that there are no internal pulls on the card and hence the RST_n signal should be driven appropriately to prevent the input circuits from flowing unnecessary leakage current. Thus, even though the line remains unused, since it is connected in hardware, this change drives EMMC_RESET_L to high. BUG=b:169222156 BRANCH=zork TEST=emerge-zork coreboot eMMC DUT reboot/suspend x100 iterations pass Change-Id: I9feb826eec8a8cdad5e2bd7efcbb1dcf96185dfd Signed-off-by: Kevin Chiu <kevin.chiu@quantatw.com> Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/45756 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Raul Rangel <rrangel@chromium.org>
Diffstat (limited to 'src/soc/intel/braswell/placeholders.c')
0 files changed, 0 insertions, 0 deletions