Re: [Intel-gfx] [PATCH] drm/fb-helper: Support deferred setup

2017-06-29 Thread Daniel Vetter
On Thu, Jun 29, 2017 at 12:59 PM, Maarten Lankhorst wrote: >> @@ -2538,6 +2563,12 @@ int drm_fb_helper_hotplug_event(struct drm_fb_helper >> *fb_helper) >> return 0; >> >> mutex_lock(_helper->lock); >> + if (fb_helper->deferred_setup) {

Re: [Intel-gfx] [PATCH] drm/fb-helper: Support deferred setup

2017-06-29 Thread Maarten Lankhorst
Op 28-06-17 om 13:32 schreef Daniel Vetter: > FB helper code falls back to a 1024x768 mode if no outputs are connected > or don't report back any modes upon initialization. This can be annoying > because outputs that are added to FB helper later on can't be used with > FB helper if they don't

Re: [Intel-gfx] [PATCH] drm/fb-helper: Support deferred setup

2017-06-28 Thread Liviu Dudau
On Wed, Jun 28, 2017 at 01:32:01PM +0200, Daniel Vetter wrote: > FB helper code falls back to a 1024x768 mode if no outputs are connected > or don't report back any modes upon initialization. This can be annoying > because outputs that are added to FB helper later on can't be used with > FB helper

[Intel-gfx] [PATCH] drm/fb-helper: Support deferred setup

2017-06-28 Thread Daniel Vetter
FB helper code falls back to a 1024x768 mode if no outputs are connected or don't report back any modes upon initialization. This can be annoying because outputs that are added to FB helper later on can't be used with FB helper if they don't support a matching mode. The fallback is in place

[Intel-gfx] [PATCH] drm/fb-helper: Support deferred setup

2017-06-23 Thread Daniel Vetter
From: Thierry Reding FB helper code falls back to a 1024x768 mode if no outputs are connected or don't report back any modes upon initialization. This can be annoying because outputs that are added to FB helper later on can't be used with FB helper if they don't support a