Re: [PATCH v4 1/4] drm: Introduce generic probe function for component based masters.

2015-10-20 Thread Liviu Dudau
On Tue, Oct 20, 2015 at 11:09:09AM +0100, Russell King - ARM Linux wrote: > On Tue, Oct 20, 2015 at 11:00:55AM +0100, Emil Velikov wrote: > > Hi Liviu, > > > > On 20 October 2015 at 10:23, Liviu Dudau wrote: > > > A lot of component based DRM drivers use a variant of the same code > > > as the pr

Re: [PATCH v4 1/4] drm: Introduce generic probe function for component based masters.

2015-10-20 Thread Russell King - ARM Linux
On Tue, Oct 20, 2015 at 11:00:55AM +0100, Emil Velikov wrote: > Hi Liviu, > > On 20 October 2015 at 10:23, Liviu Dudau wrote: > > A lot of component based DRM drivers use a variant of the same code > > as the probe function. They bind the crtc ports in the first iteration > > and then scan throug

Re: [PATCH v4 1/4] drm: Introduce generic probe function for component based masters.

2015-10-20 Thread Emil Velikov
Hi Liviu, On 20 October 2015 at 10:23, Liviu Dudau wrote: > A lot of component based DRM drivers use a variant of the same code > as the probe function. They bind the crtc ports in the first iteration > and then scan through the child nodes and bind the encoders attached > to the remote endpoints

[PATCH v4 1/4] drm: Introduce generic probe function for component based masters.

2015-10-20 Thread Liviu Dudau
A lot of component based DRM drivers use a variant of the same code as the probe function. They bind the crtc ports in the first iteration and then scan through the child nodes and bind the encoders attached to the remote endpoints. Factor the common code into a separate function called drm_of_comp