From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cao Minh Hiep Date: Thu, 26 Nov 2015 02:48:22 +0000 Subject: Re: Rcar Gen2: DU: Bootlogs Error and show image error Message-Id: <565672F6.7060509@jinso.co.jp> List-Id: References: <564ECE30.9000206@jinso.co.jp> In-Reply-To: <564ECE30.9000206@jinso.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: linux-sh@vger.kernel.org Hi Laurent-san Thanks for your reply! On 2015年11月25日 10:08, Laurent Pinchart wrote: > Hello, and sorry for the late reply. No, problems! > 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 Thank you! Jinso/Hiep