Hi Daniel, On 02/09/2016 04:28 PM, Daniel Stone wrote: > Hi Akshay, > > On 1 February 2016 at 19:02, Akshay Bhat <akshay.bhat at timesys.com> 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 >>>> are loaded after the drm driver does a probe defer, yet there is no >>>> entries >>>> in the bootlog for the drm driver being re-probed. In the next-20151202 >>>> kernel log you can see it being re-probed. This points to the drm probe >>>> deferral being broken. >>> >>> I think your problem is similar to what Tixy has found when testing HDLCD, >>> which also uses the components API. He has posted a patch here: >>> >>> http://www.spinics.net/lists/arm-kernel/msg477090.html >>> >>> Russell has added it to his branch, seems to be available in linux-next >>> as commit 57480484f9f7631738ef2. >> >> Liviu, >> >> I re-tested with next-20160201 which contains the above patch and still see >> the issue where the re-probe does not work. > > Could you please try with this patch? The component system was broken > (with the same result) in a slightly different way by the same > patchset Lixy had to fix; this also kept Rockchip DRM from loading. > > http://lkml.iu.edu/hypermail/linux/kernel/1602.1/00832.html > > Cheers, > Daniel >
Your patch fixes the above re-probe issue. Thank you very much for reaching out with the patch, appreciate your help :) Thanks, Akshay
