Attention is currently required from: Henry Sun, Ren Kuo, Paul Menzel, Simon Yang, Kane Chen, Karthik Ramasubramanian. Angel Pons has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/60301 )
Change subject: mb/google/dedede/var/magolor: Set core display clock to 172.8 MHz ......................................................................
Patch Set 6:
(2 comments)
Commit Message:
https://review.coreboot.org/c/coreboot/+/60301/comment/c2c01cb3_7a6f18b4 PS6, Line 9: With the default core display clock of 172.8 MHz,it improved the : stability of start up in Chrome OS in secure mode. : The rare fail system will not hang up in Chrome OS from secure mode. : The core display clock = 172.8 MHz in coreboot is form Intel's : recommendation. Hmmm, this paragraph is a bit confusing to understand. If I understand it correctly:
- Magolor has a rare stability issue when booting ChromeOS in secure mode, where the system may hang. - Reducing the initial CD clock frequency to 172.8 MHz avoids this problem.
If my understanding is correct, here's my suggestion:
When using the default initial core display clock frequency, Magolor has a rare stability issue where the startup of Chrome OS in secure mode may hang. Slowing the initial core display clock frequency down to 172.8 MHz as per Intel recommendation avoids this problem.
https://review.coreboot.org/c/coreboot/+/60301/comment/003da546_c7c1e771 PS6, Line 18: Check the DUTs can boot up in secure mode. Out of curiosity, can the CdClk frequency be increased back to regular speeds when OS GFX drivers take over?