Change in coreboot[master]: soc/intel/elkhartlake: Introduce Intel PSE

[Nico Huber (Code Review)]

Attention is currently required from: Arthur Heymans, Maulik V Vaghela, Paul Menzel, Mario Scheithauer, Angel Pons, Subrata Banik, Michael Niewöhner, Werner Zeh, Patrick Rudolph, Felix Held.
Nico Huber has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/55367 )

Change subject: soc/intel/elkhartlake: Introduce Intel PSE
......................................................................

Patch Set 50:

(2 comments)

Patchset:

PS50: 
https://review.coreboot.org/c/flashrom/+/58883

File src/soc/intel/elkhartlake/romstage/fsp_params.c:

https://review.coreboot.org/c/coreboot/+/55367/comment/e2f1be42_b864ed5a 
PS49, Line 127: 	m_cfg->PchPseEnable = CONFIG(PSE_ENABLE);
> We will see if there is something useable here and add a follow-up. […]

I don't know what OK means on your scale. You outrank me anyway, so
there is no point in asking me for permission and it's not a technical
matter anyway.

From a social point of view, no, it's not OK. Upstream coreboot is
mostly maintained by individuals of the community in their spare time,
same for developer support. We have worked hard to make things around
blobs maintainable and to avoid error-prone code that might not boot
and results in support requests. It becomes more tedious if we have
to repeat every tiny discussion for every tiny blob added. Ignoring
the hard work naturally looks like you don't care about the feelings
of the people committed to coreboot. Also, pushing patches like this
prematurely forward makes it much harder to get authors like Sheng
accepted by the hard working folks. Not only now but also long-term.
If somebody will look at the Git history in a year or so, they don't
see this discussion, they see the code and who wrote it. And with
every TODO comment you add, you gamble. If it isn't handled before
somebody stumbles over it, it will make things look even worse.