elog: Ensure eventlog will always get initialized when configured in
commita46ee4d34d6b7ce7d47882779c7fb36270ccbda1
authorJulius Werner <jwerner@chromium.org>
Mon, 8 Aug 2016 23:18:28 +0000 (8 16:18 -0700)
committerJulius Werner <jwerner@chromium.org>
Wed, 10 Aug 2016 00:54:21 +0000 (10 02:54 +0200)
treecb8bea702a1a3b342d4c178b682605112fb96369
parenteec1c28bd424ece0b60abda21912c4e8f51ff3ba
elog: Ensure eventlog will always get initialized when configured in

Commit 0d9cd92e (chromeos: Clean up elog handling) removed the
individual elog_init() calls from mainboards that did them and automated
adding certain events through the boot state machine. Unfortunately,
the new code would sometimes not log any specific event at all, and
thereby also never call elog_init() (through elog_add_event()) which
adds the "System boot" event.

We can assume that any board that configures the eventlog at all
actually wants to use it, so let's just add another call to elog_init()
to the boot state machine so we can ensure it gets called at least once.

BRANCH=None
BUG=chrome-os-partner:56001
TEST=Booted Kevin, confirmed that eventlog code runs again.

Change-Id: Ibe7bfc94b3e3d11ba881399a39f9915991c89d8c
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/16118
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Tested-by: build bot (Jenkins)
src/drivers/elog/elog.c