2 comments:
Patch Set #9, Line 94: #if CONFIG(FSP_USES_CB_STACK)
Yes, it should be guarded to be more correct. However, what matters here is the ordering. […]
yes, agree the ordering is important hence i have added the layout diagram to call out where FSP heap should exist. i hope that helps. Now as you said, will guard with ENV_ROMSTAGE to make it explicit. but i need to check in case of FSP-T usecase do FSP need to have heap region reversed as well (i hope that would be the case as well), right not chrome doesn't use FSP_t but there are some user for FSp-T as well.
File src/drivers/intel/fsp2_0/Kconfig:
Patch Set #9, Line 209: default 0x10000
> we had a sync with FSP team and finalize heap = 0x10000 and stack = 0x20000 for now on all FSP2. […]
seems like this always the case with single stack assumption where FSP need to have bigger stack size and heap requirement is something that personally i have noticed with this issue but it was there and got resolved by our arch->StacKBase UPD wrongly assumed as stack base for FSP to provide additional 128KB for heap as well.
Now hopefully with CML integration guide documentation, FSP stack requirement ~128KB (mostly getting used in FSP-M training considering both debug and release mode) and heap requirement ~64KB (for all hobs)
To view, visit change 35165. To unsubscribe, or for help writing mail filters, visit settings.