summaryrefslogtreecommitdiff
path: root/src/mainboard/asus/m2n-e/hda_verb.c
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2017-03-22 16:16:34 -0700
committerAaron Durbin <adurbin@chromium.org>2017-05-05 23:24:20 +0200
commitb9126fe46cb7432b9d9d1f4ca8b557e50e303380 (patch)
tree5e6905ba730f62bb6e9ecf3462ad262ce74a2fef /src/mainboard/asus/m2n-e/hda_verb.c
parentc623aa055d590501e14669277bfa3ba46c5ec22b (diff)
cr50: check if the new image needs to be enabled and act on it
The AP sends the Cr50 a request to enable the new firmware image. If the new Cr50 image was found and enabled, the AP expects the Cr50 to reset the device in 1 second. While waiting for the Cr50 to reset, the AP logs a newly defined event and optionally shuts down the system. By default the x86 systems power off as shutting those systems down is not board specific. BRANCH=gru,reef BUG=b:35580805 TEST=built a reef image, observed that in case cr50 image is updated, after the next reboot the AP stops booting before loading depthcharge, reports upcoming reset and waits for it. Once the system is booted after that, the new event can be found in the log: localhost ~ # mosys eventlog list ... 7 | 2017-03-23 18:42:12 | Chrome OS Developer Mode 8 | 2017-03-23 18:42:13 | Unknown | 0xac 9 | 2017-03-23 18:42:21 | System boot | 46 ... Change-Id: I45fd6058c03f32ff8edccd56ca2aa5359d9b21b1 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/18946 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Furquan Shaikh <furquan@google.com>
Diffstat (limited to 'src/mainboard/asus/m2n-e/hda_verb.c')
0 files changed, 0 insertions, 0 deletions