Probing LPC can cause PCI enumeration to take place, which significantly
increases pre-relocation memory usage. Also, LPC is somtimes enabled
directly by SPL.

Adjust the logic to probe the LPC only after relocation. This allows
chromebook_link64 to start up without a much larger
CONFIG_SYS_MALLOC_F_LEN value.

Signed-off-by: Simon Glass <[email protected]>
---

Changes in v2:
- Add new patch to set up LPC only after relocation

 drivers/sysreset/sysreset_x86.c | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/drivers/sysreset/sysreset_x86.c b/drivers/sysreset/sysreset_x86.c
index 8042f3994fe2..4936fdb76c72 100644
--- a/drivers/sysreset/sysreset_x86.c
+++ b/drivers/sysreset/sysreset_x86.c
@@ -129,8 +129,13 @@ static int x86_sysreset_probe(struct udevice *dev)
 {
        struct x86_sysreset_plat *plat = dev_get_plat(dev);
 
-       /* Locate the PCH if there is one. It isn't essential */
-       uclass_first_device(UCLASS_PCH, &plat->pch);
+       /*
+        * Locate the PCH if there is one. It isn't essential. Avoid this before
+        * relocation as we shouldn't need reset then and it needs a lot of
+        * memory for PCI enumeration.
+        */
+       if (gd->flags & GD_FLG_RELOC)
+               uclass_first_device(UCLASS_PCH, &plat->pch);
 
        return 0;
 }
-- 
2.40.0.634.g4ca3ef3211-goog

Reply via email to