On 7/8/2023 1:04 AM, Pablo Ceballos wrote:
On Wed, Jun 14, 2023 at 9:35 PM Nautiyal, Ankit K
<ankit.k.nautiyal@xxxxxxxxx> wrote:
I was wondering if trying to set LS/PCON mode multiple time will have
any effect.
Unfortunately I do not have access to machine with Parade LSPCON chip,
had suggested in yet another git lab issue [2].
I have a patch for this, sent to try-bot, though not sent to intel-gfx
yet [3].
I tested this patch and it did not resolve the problem. The error log
was repeated multiple times and there were still link training issues
afterwards.
Really appreciate to try this thing out, thanks. Too bad it didn't
workout :(
I have seen increasing timeout does improves situation, but didn't have
enough data points to come to a timeout value.
I agree with the change based on the experiments and data you have shared.
Lets just change the timeout to 800 ms when the lspcon->vendor is
LSPCON_VENDOR_PARADE, so that it doesn't have any effect on platforms
that don't have this.
IMHO a function to get timeout value based on lspcon vendor will be
better (returns 800 ms for Parade, 400 otherwise.)
In the function itself, we can have the explanation of arriving at 800
ms for the Parade chip (as given in the commit message) as a comment.
Thanks again for trying different solutions.
Regards,
Ankit
The timeout value was already increased from 100 ms to 400 ms earlier too.
If there is indeed no other way, perhaps need to have this solution.
Yes, can this please be merged?
Regards,
Pablo
