summaryrefslogtreecommitdiff
path: root/src/mainboard/asus
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2016-03-31 11:38:13 -0500
committerAaron Durbin <adurbin@chromium.org>2016-04-02 03:52:23 +0200
commit595688a3d60c7ad0227ec7f72d8f2e73fd8f236e (patch)
tree76a14dbe86351104e15e2923125eb7f90ae3e7ab /src/mainboard/asus
parent7123e2e9b6fd5a7844cc42d5b26983db75a5c73d (diff)
soc/intel/apollolake: use CAR code coherency for all CAR stages
The flush L1D to L2 operation was only being used when loading romstage from bootblock. However, when the FSP-M component is loaded no code coherency actions are taken. I suspect this is because the FSP-M component is larger than the 24KiB L1D and the entry point is early in the image. Thus, when loading the FSP-M component the earlier part of the image is flushed out to L2 in the process of loading the latter part of the component. Also, once verstage is introduced the same code coherency actions need to be taken as well. Therefore, position the apollolake code to handle all these cases. Change-Id: Ie71764f1b420a6072c4f149ad3e37278b6cb70e1 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/14210 Tested-by: build bot (Jenkins) Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Andrey Petrov <andrey.petrov@intel.com>
Diffstat (limited to 'src/mainboard/asus')
0 files changed, 0 insertions, 0 deletions