summaryrefslogtreecommitdiff
path: root/src/mainboard/gigabyte/ga-b75m-d3v/devicetree.cb
diff options
context:
space:
mode:
authorArthur Heymans <arthur@aheymans.xyz>2016-11-30 18:40:38 +0100
committerNico Huber <nico.h@gmx.de>2017-02-17 23:44:06 +0100
commit97e13d84c30c308c3b2bc629b38e6bcc9565dc3a (patch)
treee177a3c3b2cb9804767d7bbee0cb735ddc001246 /src/mainboard/gigabyte/ga-b75m-d3v/devicetree.cb
parent17335fab175ed1a16f61729b03c1fbeeec366f37 (diff)
nb/intel/x4x: Fix raminit on reset path
Previously the raminit failed on hot reset and to work around this issue it unconditionally did a cold reset. This has the following issues: * it's slow; * when the OS issues a hot reset some disk drives expect their 5V power supply to remain on, which gets cut off by a cold reset, causing data corruption. To fix this some steps in raminit must be ommited on the reset path. This includes receive enable calibration. To achieve this it stores receive enable results in RTC nvram for them to be rewritten on the resume path. Note: The same thing needs to be done on the S3 resume path. Calling a hot reset after raminit "outb(0x6, 0cf9)" works. Change-Id: I6601dd90aebd071a0de7cec070487b0f9845bc30 Signed-off-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-on: https://review.coreboot.org/18009 Tested-by: build bot (Jenkins) Reviewed-by: Nico Huber <nico.h@gmx.de>
Diffstat (limited to 'src/mainboard/gigabyte/ga-b75m-d3v/devicetree.cb')
0 files changed, 0 insertions, 0 deletions