drm: imx: callback after probe deferral not working

2016-02-09 Thread Daniel Stone
Hi Akshay, On 9 February 2016 at 22:25, Akshay Bhat wrote: > On 02/09/2016 04:28 PM, Daniel Stone wrote: >> On 1 February 2016 at 19:02, Akshay Bhat wrote: >>> On 02/01/2016 07:11 AM, Liviu Dudau wrote: On Fri, Jan 29, 2016 at 05:12:28PM -0500, Akshay Bhat wrote: > On 01/28/2016 05:29 P

drm: imx: callback after probe deferral not working

2016-02-09 Thread Daniel Stone
Hi Akshay, On 1 February 2016 at 19:02, Akshay Bhat wrote: > On 02/01/2016 07:11 AM, Liviu Dudau wrote: >> On Fri, Jan 29, 2016 at 05:12:28PM -0500, Akshay Bhat wrote: >>> On 01/28/2016 05:29 PM, Rob Clark wrote: >>> Also from the original log you can see that there are a lot of modules >>> that

drm: imx: callback after probe deferral not working

2016-02-09 Thread Akshay Bhat
Hi Daniel, On 02/09/2016 04:28 PM, Daniel Stone wrote: > Hi Akshay, > > On 1 February 2016 at 19:02, Akshay Bhat wrote: >> On 02/01/2016 07:11 AM, Liviu Dudau wrote: >>> On Fri, Jan 29, 2016 at 05:12:28PM -0500, Akshay Bhat wrote: On 01/28/2016 05:29 PM, Rob Clark wrote: Also from the o

drm: imx: callback after probe deferral not working

2016-02-01 Thread Akshay Bhat
On 02/01/2016 07:11 AM, Liviu Dudau wrote: > On Fri, Jan 29, 2016 at 05:12:28PM -0500, Akshay Bhat wrote: >> >> >> On 01/28/2016 05:29 PM, Rob Clark wrote: >>> can't really say if that is the issue in this case, but these are the >>> symptoms you'd see if the kernel was built without some driver

drm: imx: callback after probe deferral not working

2016-02-01 Thread Liviu Dudau
On Fri, Jan 29, 2016 at 05:12:28PM -0500, Akshay Bhat wrote: > > > On 01/28/2016 05:29 PM, Rob Clark wrote: > >can't really say if that is the issue in this case, but these are the > >symptoms you'd see if the kernel was built without some driver that > >imx-drm depends on[1]. The kernel will on

drm: imx: callback after probe deferral not working

2016-02-01 Thread Rob Herring
On Thu, Jan 28, 2016 at 4:29 PM, Rob Clark wrote: > can't really say if that is the issue in this case, but these are the > symptoms you'd see if the kernel was built without some driver that > imx-drm depends on[1]. The kernel will only try to reprobe a driver > if some other driver has loaded s

drm: imx: callback after probe deferral not working

2016-01-29 Thread Akshay Bhat
On 01/28/2016 05:29 PM, Rob Clark wrote: > can't really say if that is the issue in this case, but these are the > symptoms you'd see if the kernel was built without some driver that > imx-drm depends on[1]. The kernel will only try to reprobe a driver > if some other driver has loaded since it

drm: imx: callback after probe deferral not working

2016-01-28 Thread Rob Clark
can't really say if that is the issue in this case, but these are the symptoms you'd see if the kernel was built without some driver that imx-drm depends on[1]. The kernel will only try to reprobe a driver if some other driver has loaded since it last deferred (otherwise, it would be pointless, yo

drm: imx: callback after probe deferral not working

2016-01-28 Thread Akshay Bhat
Hi, There appears to be a bug in kernel where after a probe deferral by the drm driver, the deferred drm function is never called again at a later point. I have a iMX6 based board where there is pca9547 i2c mux between the display and the mx6 processor. The drm driver tries to get EDID inform