Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp208782pxv; Thu, 8 Jul 2021 00:23:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz7k2S0oXncpoexLLzVLoaLZoEaHEZW7jRzYAm4760Y9OKALDjXEfFX55BR36cYnIJp7cy1 X-Received: by 2002:a17:907:1b29:: with SMTP id mp41mr29229739ejc.459.1625729032527; Thu, 08 Jul 2021 00:23:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625729032; cv=none; d=google.com; s=arc-20160816; b=olxroU5rBmUPSMttz2jV+HIUUjH6XTKFuJqZqULdMo2Hw5yyxadTz3KHCN9mV9rfs2 H35wxkSvrCN7Rv90bKl3x6BpuT0MWWPVLc6aaRHLe6yxS76uC5NIvbznSWv+/e0BrPP7 gB09HqUTOS7FnRmiOHcKZHDRwqQD3mebaPTk6w4KeocvOOqUfXUhwO/Ks2QZNR003WwD TryMK81YdTbmu+X2Bl4FvsU4lS3sNcuJFKIeA8lKfmM9Roy74rZ1Hz+Q84UiIQSCraTL bVdlvAXm+QYl/MAvuhdb+EYMxpYPl3SjE/4ZuTTWcbqPGMAUAFXNe5JxLTbHkF7vyc9h qJMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=i1mJOMHUWDYqySVtTnaUWw/Vd0BNrKWKwW8tSUUEWpw=; b=oZFUk7DmhX8XytpHSJXwSYHE7G5dh4SYIzuAC6ISNNquW2VQkDst5Z7SvRf6S82u68 L+NUj0FmIRIwRSDIN2iRh/zT9+JW+Jkvi4BxmRhSBQvecMTzny2O0fgQXIMEdFu3kBi8 baWTIDI0RZyKX1P2q2lweecJ9YA3AWEEUhHlI37zYnIV9eljtQXdUg+n+OqkTkMMpH0W u/DmURC1BGW3k6VXd5peSKwFPZ0tdjut1PlcEXzajpm/yfqIopJXSGx8Y/5igBMFCK9Q oOL12f7soz72Vm0h5zAOKobIX5rnwsnF3Is6YEwS3rb43rOib7RLKVGQV42BUY9EgcxE XhTg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i9si2214523edc.312.2021.07.08.00.23.30; Thu, 08 Jul 2021 00:23:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230439AbhGHHZA (ORCPT + 99 others); Thu, 8 Jul 2021 03:25:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229780AbhGHHY7 (ORCPT ); Thu, 8 Jul 2021 03:24:59 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3CD54C061574 for ; Thu, 8 Jul 2021 00:22:18 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: dafna) with ESMTPSA id 1F3F31F437E4 Subject: Re: BUG: MTK DRM/HDMI broken on 5.13 (mt7623/bpi-r2) To: Frank Wunderlich , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Chun-Kuang Hu , Philipp Zabel , linux-mediatek@lists.infradead.org, Matthias Brugger , Enric Balletbo i Serra , Collabora Kernel ML References: From: Dafna Hirschfeld Message-ID: <25d61873-38ae-5648-faab-03431b74f777@collabora.com> Date: Thu, 8 Jul 2021 09:22:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Frank, On 06.07.21 11:54, Frank Wunderlich wrote: > Hi, > > i've noticed that HDMI is broken at least on my board (Bananapi-r2,mt7623) on 5.13. > > after some research i noticed that it is working till > > commit 2e477391522354e763aa62ee3e281c1ad9e8eb1b > Author: Dafna Hirschfeld > Date: Tue Mar 30 13:09:02 2021 +0200 > > drm/mediatek: Don't support hdmi connector creation > > > which is the last of mtk-drm-next-5.13 [1] so i guess a problem with core-patches > > dmesg shows the following: > > [ 7.071342] mediatek-drm mediatek-drm.1.auto: bound 14007000.ovl (ops mtk_dis > p_ovl_component_ops) > [ 7.080330] mediatek-drm mediatek-drm.1.auto: bound 14008000.rdma (ops mtk_di > sp_rdma_component_ops) > [ 7.089429] mediatek-drm mediatek-drm.1.auto: bound 1400b000.color (ops mtk_d > isp_color_component_ops) > [ 7.098689] mediatek-drm mediatek-drm.1.auto: bound 14012000.rdma (ops mtk_di > sp_rdma_component_ops) > [ 7.107814] mediatek-drm mediatek-drm.1.auto: bound 14014000.dpi (ops mtk_dpi > _component_ops) > [ 7.116338] mediatek-drm mediatek-drm.1.auto: Not creating crtc 1 because com > ponent 9 is disabled or missing > .... > [ 38.403957] Console: switching to colour frame buffer device 160x64 > [ 48.516398] [drm:drm_crtc_commit_wait] *ERROR* flip_done timed out > [ 48.516422] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:cr > tc-0] commit wait timed out > [ 58.756384] [drm:drm_crtc_commit_wait] *ERROR* flip_done timed out > [ 58.756399] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR: > 32:HDMI-A-1] commit wait timed out > [ 68.996384] [drm:drm_crtc_commit_wait] *ERROR* flip_done timed out > [ 68.996399] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:33:p > lane-0] commit wait timed out > [ 68.996423] [drm:mtk_drm_crtc_atomic_begin] *ERROR* new event while there is > still a pending event > [ 69.106385] ------------[ cut here ]------------ > [ 69.106392] WARNING: CPU: 2 PID: 7 at drivers/gpu/drm/drm_atomic_helper.c:151 > 1 drm_atomic_helper_wait_for_vblanks.part.0+0x2a0/0x2a8 > [ 69.106414] [CRTC:41:crtc-0] vblank wait timed out We also encountered that warning on mt8173 device - Acer Chromebook R13. It happen after resuming from suspend to ram. We could not find a version that works and we were not able to find the fix of the bug. It seems like the irq isr is not called after resuming from suspend. Please share if you have new findings regarding that bug. Thanks, Dafna > > so i guess the breaking commit may be this: > > $ git logone -S"drm_crtc_commit_wait" -- drivers/gpu/drm/ > b99c2c95412c 2021-01-11 drm: Introduce a drm_crtc_commit_wait helper > > in drivers/gpu/drm/drm_atomic{,_helper}.c > > but i cannot confirm it because my git bisect does strange things (after defining 5.13 as bad and the 2e4773915223 as good, second step is before the good commit till the end, last steps are 5.11...). sorry, i'm still new to bisect. > > the fix is targeting to 5.12-rc2, is guess because CK Hu's tree is based on this...but the fix was not included in 5.12-rc2 (only after 5.12.0...got it by merging 5.12.14) > > maybe you can help me? > > regards Frank > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-next-5.13 > > _______________________________________________ > Linux-mediatek mailing list > Linux-mediatek@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-mediatek >