I own an Asus UX32VD which uses eDP for its panel and it takes Linux some 3-6 seconds to show anything on screen when booting, resuming from suspend or changing resolutions. I describe the problem in bug 56086. Apparently, the delay is due to problems with eDP link training.

However, especially for laptop panels which are always connected to the machine and never change with regard to cable length and other variables, doing "full link training" should not be necessary every time. Two alternatives, "fast link training" and "no link training" are mentioned in many places on the web (although a proper specification eludes me). Specifically, they usually say:

"System can be configured to use fast link training (simplified protocol) or no link training (no training protocol, designed for fastest display re-enable time)"

Apparently, it should be possible to use full link training only *once*, remembering the values for amplitude/preemphasis/whatever else is involved, and then re-using those values upon re-establishing the link on later occasions.

I know for a fact that on my exact laptop model, when resuming from suspend, Windows 8.0 re-establishes the link and shows the desktop in less than 1 second, while my Linux takes about 3-6 seconds, and this is not due to X or other factors, but likely due to slow link training.

I don't know specifics about the protocol, but apparently this shouldn't be too difficult. After a "full" link training has been performed, the settings should be stored and then tried when booting or resuming the next time the same resolution is used on an internal panel.

It would be great if "fast" and "no" link training could be implemented because at the moment, Linux falls behind other operating systems on laptops, which resume almost instantly from suspend and offer a much nicer user experience in this regard.

Thank you for your consideration.