On Tue, Oct 4, 2022 at 10:38 AM Jani Nikula wrote:
> Got any bug report with more info, or any other details to back this up?
> This is kind of thin. What's the 800 ms based on?
This issue affected several different CometLake-based Chrome OS device
designs. The details of the original report are
PCON mode. 100 reboot trials on one device resulted
in a median settle time of 440ms and a maximum of 444ms. Even after
increasing the timeout to 500ms, 2% of devices still had this error. So
this increases the timeout to 800ms.
Signed-off-by: Pablo Ceballos
---
Changelog since v1:
- Added more
PCON mode. 100 reboot trials on one device resulted
in a median settle time of 440ms and a maximum of 444ms. Even after
increasing the timeout to 500ms, 2% of devices still had this error. So
this increases the timeout to 800ms.
Signed-off-by: Pablo Ceballos
---
V2: Added more details in the co
On Wed, Jun 14, 2023 at 9:35 PM Nautiyal, Ankit K
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, s
