Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/33142 )
Change subject: Kconfig: Create coreboot separate stage kconfigs ......................................................................
Patch Set 1:
What is this patch actually solving (at a high level)? I feel like it's just adding some more vines to the config jungle for no real benefit other than for people to trip over. Don't we already know which stages we have from other options? In general, coreboot always has a bootblock, a romstage and a ramstage. It has a verstage if CONFIG_SEPARATE_VERSTAGE is set. With your new feature, it does not have a ramstage if the main Kconfig for that feature is set (is that CONFIG_RAMPAYLOAD? I didn't keep track...).
So if you want something you can depend ramstage-specific stuff on, can't you just do 'depends on !RAMPAYLOAD'? Why does it need a separate option that's tied so weirdly into the architecture Kconfigs? Sure, if we eventually have 4 different cases where coreboot somehow doesn't have a ramstage it might make sense to factor those all out into a common option, but I don't really see that happening anytime soon?