Conversation
This reverts commit d1e6a84.
Change-Id: Idf37290a410a2e31549e26e852b94f81fc939061
Change-Id: I8076322d2950b33641a1a2aa678b9e088c494a43
Change-Id: Icc4a882ff73f62a134b92f1afb0dc298ea809189
Change-Id: Id7f4373989dffe8c3bc68a034f59a94d2160dd15
Change-Id: Id239f4bb28a3c755a6ff64d66ec046b0da6c27ef
Change-Id: Ic2dbbf351f2b14b6d9a1c1b123ce2553a73a2f79
Change-Id: Ib4c568f74eec928a420fb42204303ef1c65c3c71
The `clear` command for SMMSTORE version 1 does not require a parameter. Change-Id: I992b7ce5962bf7ee62b7e1970ae7aa1b975ef42e Signed-off-by: Tim Crawford <tcrawford@system76.com>
Change-Id: I51f047b62a8a2eadcaf89a4c6e6041d5bb9d1331
- Remove the comments, which were copied from the header - Remove the dq entries for LPDDR, which are not used - Allow higher memory speeds on oryp5 Change-Id: Ied41e9aad832c19344f92845b0d8d4bdab7e1ac8
Upstream is moving towards having registers set within their relevant device. Do this now to reduce the diff for upstreaming and later syncing changes back. Does not touch the TGL boards or lemp9, which have most of the changes. - Move registers to devices - Remove unneeded registers - Remove extra comments Change-Id: I8cd54d428493981538722e9fe6a8f3ff2918a041
Change-Id: I528320065b0d90926bb94963cdc833c02106b35c
Change-Id: I8be16d9203dd71ca877cbc00290ec044e8b5cc77
Change-Id: Iab3d22ed7af4986c457fdbbbfafb3699f8e60e27
Change-Id: Ia0a505b22b91c70b5263fa6c2471d3dc905d13e8
Change-Id: Iba9cf8eda1957fc0f594125d987c083b18c719c2
Change-Id: I99e92293946229b4212ce38f75499d0fadd3b6a7
Change-Id: I215bf6e502e1cbf67635d3ac26b0b6208137423b
Change-Id: I4cca07b77dd486a8d79b3ceea1c5aa4f15fbe54d
Change-Id: I83bdf50d4f9789400b6a49ee027797718fd8118b
Change-Id: Icef5501856a955fc32775870e6d6d492bb03a669
|
Had the error on oryp6 on boot. |
|
I can't comment at all on the xHCI error. Regarding the first error: The issue appears to be that the method tries to guarantee that the link will come up, and will set the "retrain link" bit after every 'timeout' until it does (I haven't examined the datasheet to find the exact bits, but this appears to be the purpose based on the uses and names). The issue is that this gets aborted (AE_AML_LOOP_TIMEOUT, from the log) if it takes too long, which is registered as a significant error. I've had luck with a much simpler If I recall correctly, if the link doesn't come up, the drivers just try again. Regarding the second error: It appears to me that since _PS3 will only execute after Optimus sets flags, the named status variable is not updated. As a result, _PS0 skips execution, so the link is not brought up. |
|
Replaced by #98 |
No description provided.