From: Rob Herring <robh@kernel.org>
To: Rob Clark <robdclark@gmail.com>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>,
Akshay Bhat <akshay.bhat@timesys.com>
Subject: Re: drm: imx: callback after probe deferral not working
Date: Mon, 1 Feb 2016 07:19:46 -0600 [thread overview]
Message-ID: <CAL_JsqJD=qjjQytoyTcBwJx6NK4kNwZJEm9gjyZEWU2ig91cMQ@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGv+e_ZZxKt_98F71C0H5A_aAO1gopT4--zaZAxDp+V5ag@mail.gmail.com>
On Thu, Jan 28, 2016 at 4:29 PM, Rob Clark <robdclark@gmail.com> 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 last deferred (otherwise, it
> would be pointless, you'd just -EPROBE_DEFER again).
>
> [1] which is a really annoying thing about devicetree.. there's no
> good way to figure out which drivers need to be enabled in kernel
> config..
The same problem existed w/o DT. It could be solved with
board/platform kconfigs to turn on all dependencies, but then we'd be
back to having board files to some extent. IIRC, Geert U has a script
that generates the config entries from dts files.
Rob
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-02-01 13:20 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
2016-02-09 22:25 ` Akshay Bhat
2016-02-09 22:35 ` Daniel Stone
2016-02-01 13:19 ` Rob Herring [this message]
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='CAL_JsqJD=qjjQytoyTcBwJx6NK4kNwZJEm9gjyZEWU2ig91cMQ@mail.gmail.com' \
--to=robh@kernel.org \
--cc=akshay.bhat@timesys.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.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.