diff options
| author | Felix Held <felix-coreboot@felixheld.de> | 2023-12-16 22:42:19 +0100 |
|---|---|---|
| committer | Felix Held <felix-coreboot@felixheld.de> | 2023-12-19 13:15:39 +0000 |
| commit | df4955297f8fd798c1faf61cf92577edd4b2a7ce (patch) | |
| tree | f35837b327b49ffeee26507d3651142314dd0e15 /src/northbridge/amd/pi/00730F01/Kconfig | |
| parent | 7a83ab7612148e17bee158fcb933674340021bff (diff) | |
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/northbridge/amd/pi/00730F01/Kconfig')
| -rw-r--r-- | src/northbridge/amd/pi/00730F01/Kconfig | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/northbridge/amd/pi/00730F01/Kconfig b/src/northbridge/amd/pi/00730F01/Kconfig index 493bc6a13e..46acb2d59d 100644 --- a/src/northbridge/amd/pi/00730F01/Kconfig +++ b/src/northbridge/amd/pi/00730F01/Kconfig @@ -10,10 +10,6 @@ config CHIPSET_DEVICETREE string default "northbridge/amd/pi/00730F01/chipset.cb" -config HW_MEM_HOLE_SIZEK - hex - default 0x100000 - config ECAM_MMCONF_BASE_ADDRESS default 0xF8000000 |