summaryrefslogtreecommitdiffstats
path: root/src/device/Kconfig
diff options
context:
space:
mode:
authorFelix Held <felix-coreboot@felixheld.de>2023-12-16 22:42:19 +0100
committerFelix Held <felix-coreboot@felixheld.de>2023-12-19 13:15:39 +0000
commitdf4955297f8fd798c1faf61cf92577edd4b2a7ce (patch)
treef35837b327b49ffeee26507d3651142314dd0e15 /src/device/Kconfig
parent7a83ab7612148e17bee158fcb933674340021bff (diff)
downloadcoreboot-df4955297f8fd798c1faf61cf92577edd4b2a7ce.tar.gz
coreboot-df4955297f8fd798c1faf61cf92577edd4b2a7ce.tar.bz2
coreboot-df4955297f8fd798c1faf61cf92577edd4b2a7ce.zip
nb/amd/pi: drop HW_MEM_HOLE_SIZEK Kconfig option
There's neither need to remove get_hw_mem_hole_info from the code if the Kconfig option was set to 0 nor the actual value didn't make any difference in the behavior of the code: When node_id has still its initial value of -1, domain_read_resources won't use the value of hole_startk, and when node_id is set to 0, get_hw_mem_hole_info also sets hole_startk to the actual value that then gets used by domain_read_resources. Signed-off-by: Felix Held <felix-coreboot@felixheld.de> Change-Id: Ieffab695a3151ed7f6bf9d6c880bbb43eecf7893 Reviewed-on: https://review.coreboot.org/c/coreboot/+/79609 Reviewed-by: Arthur Heymans <arthur@aheymans.xyz> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/device/Kconfig')
0 files changed, 0 insertions, 0 deletions