Hi, On Fri, Oct 30, 2026 at 3:00 PM Alexandre Marquet <[email protected]> wrote: > > > /** > > * @enable: Time for the panel to display a valid frame. > > * > > * The time (in milliseconds) that it takes for the panel to > > * display the first valid frame after starting to receive > > * video data. > > * > > * This is (T6-min + max(T7-max, T8-min)) on eDP timing diagrams or > > * the delay after link training finishes until we can turn the > > * backlight on and see valid data. > > */ > > > > That sounds like exactly what you're looking for, no? > > Indeed. Also having the 97ms value from the downstream code in .enable > removes the guessing associated with the 50ms in my initial proposal. So > I will implement this in v2. > > Any preference as to where I should put the new delay_200_500_e97 > panel_delay struct? I was thinking after delay_200_500_e80_d50, but > I noticed that the delays are not strictly in alphabetical order.
Yeah, it's a bit of a mess. Probably they need to be fully sorted as you said, and I probably should have been enforcing that all this time. If you wanted to send a patch sorting them, I wouldn't object. ;-) Otherwise then after "delay_200_500_e80_d50" sounds fine. -Doug
