summaryrefslogtreecommitdiff
path: root/src/mainboard/getac/Kconfig
diff options
context:
space:
mode:
authorDavid Hendricks <dhendrix@chromium.org>2013-04-22 16:03:11 -0700
committerDavid Hendricks <dhendrix@chromium.org>2013-04-23 03:20:44 +0200
commitaee444f453f38e53f3e2ac54b560707616767869 (patch)
treec504f2853a7d0779258abae395c7663ebfdf2b0f /src/mainboard/getac/Kconfig
parente8a91347b182281f18c969229f02e07102e21898 (diff)
downloadcoreboot-aee444f453f38e53f3e2ac54b560707616767869.tar.xz
exynos5250: ungate the product ID register
This makes sure that the product ID (PRO_ID) register can be read when the OS kernel is figuring out what kind of CPU it's running on. For historical reference, the original U-Boot code seems to have worked basically by accident here. The hardware has a quirk where by reading the value before gating the IP block keeps the value persistent. U-Boot reads the chip ID early on to distinguish between chip family, but we do not mix code the same way so we do not read the chip ID. Since the value has been read before the clock gating happens, the value remains available for the kernel to use during the decompression stage. We don't want to rely on that behavior when using coreboot. Instead the kernel should gate unused IPs. (credit to Gabe for finding symptom in the kernel) Change-Id: Iaa21e6e718b9000b5558f568020f393779fd208e Signed-off-by: Gabe Black <gabeblack@chromium.org> Signed-off-by: David Hendricks <dhendrix@chromium.org> Reviewed-on: http://review.coreboot.org/3121 Reviewed-by: Ronald G. Minnich <rminnich@gmail.com> Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Tested-by: build bot (Jenkins)
Diffstat (limited to 'src/mainboard/getac/Kconfig')
0 files changed, 0 insertions, 0 deletions