All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Akshay Bhat <akshay.bhat@timesys.com>
Cc: "Waters,
	Justin (justin.waters@timesys.com)" <justin.waters@timesys.com>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: drm: imx: callback after probe deferral not working
Date: Tue, 9 Feb 2016 21:28:54 +0000	[thread overview]
Message-ID: <CAPj87rOALhvKrqCsfDTH9ZT+Nw9FJMKxoVLc_LMim+b8TBgeOw@mail.gmail.com> (raw)
In-Reply-To: <56AFABC6.7000006@timesys.com>

Hi Akshay,

On 1 February 2016 at 19:02, Akshay Bhat <akshay.bhat@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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-02-09 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 19:56 drm: imx: callback after probe deferral not working Akshay Bhat
2016-01-28 22:29 ` Rob Clark
2016-01-29 22:12   ` Akshay Bhat
2016-02-01 12:11     ` Liviu Dudau
2016-02-01 19:02       ` Akshay Bhat
2016-02-09 21:28         ` Daniel Stone [this message]
2016-02-09 22:25           ` Akshay Bhat
2016-02-09 22:35             ` Daniel Stone
2016-02-01 13:19   ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPj87rOALhvKrqCsfDTH9ZT+Nw9FJMKxoVLc_LMim+b8TBgeOw@mail.gmail.com \
    --to=daniel@fooishbar.org \
    --cc=Liviu.Dudau@arm.com \
    --cc=akshay.bhat@timesys.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=justin.waters@timesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.