From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko =?ISO-8859-1?Q?St=FCbner?= Subject: Re: rk3288: Enable HDMI hang boot and no Linux log Date: Mon, 04 Sep 2017 15:34:25 +0200 Message-ID: <2008140.oetUxFhdGh@diego> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Jagan Teki Cc: "linux-kernel@vger.kernel.org" , dri-devel@lists.freedesktop.org, linux-rockchip@lists.infradead.org, "linux-arm-kernel@lists.infradead.org" List-Id: linux-rockchip.vger.kernel.org SGksCgpBbSBNb250YWcsIDQuIFNlcHRlbWJlciAyMDE3LCAxODoxNDo1NiBDRVNUIHNjaHJpZWIg SmFnYW4gVGVraToKPiBJcyBsaW51eC1uZXh0IHN1cHBvcnQgSERNSSBvbiByazMyODg/IEknbSB0 cnlpbmcgdG8gZW5hYmxlIGhkbWkgKHdpdGgKPiBkZGMtaTJjLWJ1cykgc3RhdGljYWxseSBhbG9u ZyB3aXRoIExpbnV4IGJvb3QgbG9nby4gT2JzZXJ2ZWQgYW4ga2VybmVsCj4gYm9vdCBoYW5nLCBk aWRuJ3QgZmluZCB3aGF0cyB3cm9uZyBiZWNhdXNlIERXQyBNSEwgUEhZIGFzIGRldGVjdGVkCj4g ZnJvbSB0aGUgbG9nLgoKRldJVyBqdXN0IGNoZWNrZWQgc29tZXRoaW5nIGJhc2VkIG9uIDQuMTMt cmM3IG9uIGEgcmszMjg4LWZpcmVmbHkgYW5kIGhkbWkKaXMgd29ya2luZyBuaWNlbHkgLSBhcyBl eHBlY3RlZC4KCkFsc28geW91ciBrZXJuZWwgc2VlbXMgdG8gc3RvcCBhdCB0aGUgc3RhZ2Ugd2hl cmUgaXQgaGFuZHMgb3ZlciB0byB0aGUgcm9vdGZzLCAKc28gSSdkIGd1ZXNzIHlvdXIgaXNzdWUg bWlnaHQgYmUgZm91bmQgaW4gdGhhdCBhcmVhLiBUaGUgaGRtaSBsb29rcyBpbm5vY2VudCAKcmVn YXJkaW5nIHlvdXIgaXNzdWUuCgoKSGVpa28KCgo+IEhlcmUgaXMgdGhlIGZ1bGwgbG9nWzFdIHBs ZWFzZSBsZXQgbWUga25vdyBpZiBJIG1pc3MgYW55Pwo+IAo+IExvZzoKPiAtLS0tLQo+IFsgICAg MS45ODM4MzJdIHJvY2tjaGlwLWRybSBkaXNwbGF5LXN1YnN5c3RlbTogYm91bmQgZmY5MzAwMDAu dm9wIChvcHMKPiAweGMwZjUzNDE4KQo+IFsgICAgMS45OTIxNzBdIHJvY2tjaGlwLWRybSBkaXNw bGF5LXN1YnN5c3RlbTogYm91bmQgZmY5NDAwMDAudm9wIChvcHMKPiAweGMwZjUzNDE4KQo+IFsg ICAgMi4wMDA0MTZdIGR3aGRtaS1yb2NrY2hpcCBmZjk4MDAwMC5oZG1pOiBEZXRlY3RlZCBIRE1J IFRYCj4gY29udHJvbGxlciB2Mi4wMGEgd2l0aCBIRENQIChEV0MgTUhMIFBIWSkKPiBbICAgIDIu MDExMjEwXSByb2NrY2hpcC1kcm0gZGlzcGxheS1zdWJzeXN0ZW06IGJvdW5kIGZmOTgwMDAwLmhk bWkKPiAob3BzIDB4YzBmNTUxZjQpCj4gWyAgICAyLjAxOTQ5MF0gW2RybV0gU3VwcG9ydHMgdmJs YW5rIHRpbWVzdGFtcCBjYWNoaW5nIFJldiAyICgyMS4xMC4yMDEzKS4KPiBbICAgIDIuMDI2ODg4 XSBbZHJtXSBObyBkcml2ZXIgc3VwcG9ydCBmb3IgdmJsYW5rIHRpbWVzdGFtcCBxdWVyeS4KPiBb ICAgIDIuMDMzNTE2XSBbZHJtXSBDYW5ub3QgZmluZCBhbnkgY3J0YyBvciBzaXplcwo+IFsgICAg Mi4wMzg3MzFdIFtkcm1dIEluaXRpYWxpemVkIHJvY2tjaGlwIDEuMC4wIDIwMTQwODE4IGZvcgo+ IGRpc3BsYXktc3Vic3lzdGVtIG9uIG1pbm9yIDAKPiBbICAgIDIuMDQ3ODE4XSBoY3Rvc3lzOiB1 bmFibGUgdG8gb3BlbiBydGMgZGV2aWNlIChydGMwKQo+IFsgICAgMi4wNTM5NThdICBtbWNibGsw OiBwMQo+IFsgICAgMi4wNTcwMDldIHR0eVMyIC0gZmFpbGVkIHRvIHJlcXVlc3QgRE1BCj4gCj4g WzFdIGh0dHBzOi8vcGFzdGUudWJ1bnR1LmNvbS8yNTQ2NDY3NC8KPiAKPiB0aGFua3MhCgoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVsIG1h aWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlzdHMu ZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== From mboxrd@z Thu Jan 1 00:00:00 1970 From: heiko@sntech.de (Heiko =?ISO-8859-1?Q?St=FCbner?=) Date: Mon, 04 Sep 2017 15:34:25 +0200 Subject: rk3288: Enable HDMI hang boot and no Linux log In-Reply-To: References: Message-ID: <2008140.oetUxFhdGh@diego> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, Am Montag, 4. September 2017, 18:14:56 CEST schrieb Jagan Teki: > Is linux-next support HDMI on rk3288? I'm trying to enable hdmi (with > ddc-i2c-bus) statically along with Linux boot logo. Observed an kernel > boot hang, didn't find whats wrong because DWC MHL PHY as detected > from the log. FWIW just checked something based on 4.13-rc7 on a rk3288-firefly and hdmi is working nicely - as expected. Also your kernel seems to stop at the stage where it hands over to the rootfs, so I'd guess your issue might be found in that area. The hdmi looks innocent regarding your issue. Heiko > Here is the full log[1] please let me know if I miss any? > > Log: > ----- > [ 1.983832] rockchip-drm display-subsystem: bound ff930000.vop (ops > 0xc0f53418) > [ 1.992170] rockchip-drm display-subsystem: bound ff940000.vop (ops > 0xc0f53418) > [ 2.000416] dwhdmi-rockchip ff980000.hdmi: Detected HDMI TX > controller v2.00a with HDCP (DWC MHL PHY) > [ 2.011210] rockchip-drm display-subsystem: bound ff980000.hdmi > (ops 0xc0f551f4) > [ 2.019490] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 2.026888] [drm] No driver support for vblank timestamp query. > [ 2.033516] [drm] Cannot find any crtc or sizes > [ 2.038731] [drm] Initialized rockchip 1.0.0 20140818 for > display-subsystem on minor 0 > [ 2.047818] hctosys: unable to open rtc device (rtc0) > [ 2.053958] mmcblk0: p1 > [ 2.057009] ttyS2 - failed to request DMA > > [1] https://paste.ubuntu.com/25464674/ > > thanks! From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753671AbdIDNee (ORCPT ); Mon, 4 Sep 2017 09:34:34 -0400 Received: from gloria.sntech.de ([95.129.55.99]:39674 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751363AbdIDNed (ORCPT ); Mon, 4 Sep 2017 09:34:33 -0400 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Jagan Teki Cc: Mark Yao , David Airlie , "linux-arm-kernel@lists.infradead.org" , dri-devel@lists.freedesktop.org, linux-rockchip@lists.infradead.org, "linux-kernel@vger.kernel.org" Subject: Re: rk3288: Enable HDMI hang boot and no Linux log Date: Mon, 04 Sep 2017 15:34:25 +0200 Message-ID: <2008140.oetUxFhdGh@diego> User-Agent: KMail/5.2.3 (Linux/4.11.0-1-amd64; KDE/5.28.0; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Am Montag, 4. September 2017, 18:14:56 CEST schrieb Jagan Teki: > Is linux-next support HDMI on rk3288? I'm trying to enable hdmi (with > ddc-i2c-bus) statically along with Linux boot logo. Observed an kernel > boot hang, didn't find whats wrong because DWC MHL PHY as detected > from the log. FWIW just checked something based on 4.13-rc7 on a rk3288-firefly and hdmi is working nicely - as expected. Also your kernel seems to stop at the stage where it hands over to the rootfs, so I'd guess your issue might be found in that area. The hdmi looks innocent regarding your issue. Heiko > Here is the full log[1] please let me know if I miss any? > > Log: > ----- > [ 1.983832] rockchip-drm display-subsystem: bound ff930000.vop (ops > 0xc0f53418) > [ 1.992170] rockchip-drm display-subsystem: bound ff940000.vop (ops > 0xc0f53418) > [ 2.000416] dwhdmi-rockchip ff980000.hdmi: Detected HDMI TX > controller v2.00a with HDCP (DWC MHL PHY) > [ 2.011210] rockchip-drm display-subsystem: bound ff980000.hdmi > (ops 0xc0f551f4) > [ 2.019490] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 2.026888] [drm] No driver support for vblank timestamp query. > [ 2.033516] [drm] Cannot find any crtc or sizes > [ 2.038731] [drm] Initialized rockchip 1.0.0 20140818 for > display-subsystem on minor 0 > [ 2.047818] hctosys: unable to open rtc device (rtc0) > [ 2.053958] mmcblk0: p1 > [ 2.057009] ttyS2 - failed to request DMA > > [1] https://paste.ubuntu.com/25464674/ > > thanks!