Re: [Intel-gfx] [PATCH 1/8] drm/fb-helper: Eliminate the .best_encoder() usage

2018-06-27 Thread Ville Syrjälä
On Wed, Jun 27, 2018 at 11:03:31AM +0200, Daniel Vetter wrote: > On Tue, Jun 26, 2018 at 08:47:07PM +0300, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Instead of using the .best_encoder() hook to figure out whether a given > > connector+crtc combo will work, let's instead do what userspa

Re: [Intel-gfx] [PATCH 1/8] drm/fb-helper: Eliminate the .best_encoder() usage

2018-06-27 Thread Daniel Vetter
On Tue, Jun 26, 2018 at 08:47:07PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Instead of using the .best_encoder() hook to figure out whether a given > connector+crtc combo will work, let's instead do what userspace does and > just iterate over all the encoders for the connector, and t

Re: [Intel-gfx] [PATCH 1/8] drm/fb-helper: Eliminate the .best_encoder() usage

2018-06-26 Thread Alex Deucher
On Tue, Jun 26, 2018 at 1:47 PM, Ville Syrjala wrote: > From: Ville Syrjälä > > Instead of using the .best_encoder() hook to figure out whether a given > connector+crtc combo will work, let's instead do what userspace does and > just iterate over all the encoders for the connector, and then check

[Intel-gfx] [PATCH 1/8] drm/fb-helper: Eliminate the .best_encoder() usage

2018-06-26 Thread Ville Syrjala
From: Ville Syrjälä Instead of using the .best_encoder() hook to figure out whether a given connector+crtc combo will work, let's instead do what userspace does and just iterate over all the encoders for the connector, and then check each crtc against each encoder's possible_crtcs bitmask. Cc: D