dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Gilmore <dennis@ausil.us>
To: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org
Subject: bug in autoloading of imx-ipuv3-crtc
Date: Tue, 19 Apr 2016 13:34:23 -0500	[thread overview]
Message-ID: <6926808.b0joqYQPQE@anubis.ausil.us> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 512 bytes --]

Hi All,

on all of my i.MX6 systems imx-ipuv3-crtc ius not getting automatically 
loaded.  Everything is built as a module

CONFIG_DRM_IMX=m
CONFIG_DRM_IMX_FB_HELPER=m
CONFIG_DRM_IMX_HDMI=m
CONFIG_DRM_IMX_IPUV3=m
CONFIG_DRM_IMX_LDB=m
CONFIG_DRM_IMX_PARALLEL_DISPLAY=m
CONFIG_DRM_IMX_TVE=m
CONFIG_IMX_IPUV3_CORE=m

The result is that until I log in via serial or ssh and modprobe the module 
there is no display.  I suspect that there is some devicetree glue missing 4.4 
and 4.5 seem to both be effected.

Dennis

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2016-04-19 18:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 18:34 Dennis Gilmore [this message]
2016-04-19 18:50 ` bug in autoloading of imx-ipuv3-crtc Russell King - ARM Linux
2016-04-19 19:27   ` Dennis Gilmore
2016-04-19 20:16     ` Dennis Gilmore
2016-04-20 23:03       ` Uwe Kleine-König
2016-04-21 17:37         ` Dennis Gilmore
2016-04-21 19:39           ` Dennis Gilmore
2016-04-22 13:11         ` Dennis Gilmore
2016-04-26 22:59           ` Dave Airlie
2016-04-27 15:21             ` Philipp Zabel
2016-04-27  8:30           ` Philipp Zabel

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=6926808.b0joqYQPQE@anubis.ausil.us \
    --to=dennis@ausil.us \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox