linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: Rcar Gen2: DU: Bootlogs Error and show image error
Date: Fri, 27 Nov 2015 00:39:57 +0000	[thread overview]
Message-ID: <1607515.VtNMz4L24e@avalon> (raw)
In-Reply-To: <564ECE30.9000206@jinso.co.jp>

Hello,

On Thursday 26 November 2015 11:48:22 Cao Minh Hiep wrote:
> On 2015年11月25日 10:08, Laurent Pinchart wrote:
> > On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote:
> >> Hi Laurent-san
> >> 
> >> Thanks for your kindness support!
> >> I don't mean to bother you!
> > 
> > You're not bothering me at all :-)
> > 
> >> But as you know, we have reported to you before, have some problems
> >> related to DU driver.
> >> We couldn't show a image on the display. We found the messages as showed
> >> below:
> >> -----
> >> Boot logs on Rcar-H2:
> >> rcar-du feb00000.display: failed to initialize encoder
> >> /i2c@e6520000/hdmi@39 (-38), skipping
> >> rcar-du feb00000.display: fb0:  frame buffer device
> >> -----
> >> Boot logs on Rcar-M2:
> >> rcar-du feb00000.display: failed to initialize encoder
> >> /i2c@e6530000/hdmi@39 (-g
> >> rcar-du feb00000.display: error: no encoder could be initialized
> >> rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
> >> rcar-du: probe of feb00000.display failed with error -22
> >> -----
> >> 
> >> This is tested on linux stable v4.3.
> >> Please have a look when you have time.
> > 
> > Have you enabled CONFIG_DRM_RCAR_HDMI ?
> 
> Yes, These initialize logs are taken with default config that
> CONFIG_DRM_RCAR_HDMI disabled at v4.3.
> But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show
> any images on HDMI or RGB Screen.
> 
> I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default
> config at v4.4-rc2.
> But have a error message as below and DU is still not improved(still can
> not show images on screen).
> 
> 
> On Rcar-H2(Lager):
> 
> [drm] Initialized drm 1.1.0 20060810
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [drm] No driver support for vblank timestamp query.
> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
> rcar-du feb00000.display: fb0:  frame buffer device
> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
> 
> On Rcar-M2(Koelsch):
> 
> [drm] Initialized drm 1.1.0 20060810
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [drm] No driver support for vblank timestamp query.
> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
> rcar-du feb00000.display: fb0:  frame buffer device
> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0

-517 (-EPROBE_DEFER) means that probe deferral is requested because a required 
dependency is not present. Have you compiled and loaded the adv7511 driver 
(CONFIG_DRM_I2C_ADV7511) ?

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2015-11-27  0:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20  7:39 Rcar Gen2: DU: Bootlogs Error and show image error Cao Minh Hiep
2015-11-25  1:08 ` Laurent Pinchart
2015-11-26  2:48 ` Cao Minh Hiep
2015-11-27  0:39 ` Laurent Pinchart [this message]
2015-11-27  6:13 ` Cao Minh Hiep
2015-12-02  7:23 ` Cao Minh Hiep
2015-12-13 19:45 ` Laurent Pinchart
2016-06-29 23:58 ` Laurent Pinchart

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=1607515.VtNMz4L24e@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).