Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3395826ybt; Tue, 30 Jun 2020 01:28:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyNvbLm0CL4ERvBoxFYM3MXLRJA0uAJO3dUzCXp0pH3bRNoAI5L3DDo55iHWPuoaVODO86y X-Received: by 2002:a17:906:3945:: with SMTP id g5mr18409745eje.549.1593505701627; Tue, 30 Jun 2020 01:28:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593505701; cv=none; d=google.com; s=arc-20160816; b=F9CWu96ICreCKvq3/I7dk6Z1MvO0rQR1ppXXBJ8dC0j6M+oAKvOyeg56qFErog/v98 3m5627ZiTSt3gh6BT1opVesZMLKHkmwPLhasN4WeK4KT6i5LrNeSvBXyVcdf4UQeKsed qffzmF43fbRlheAU5WfUVTC7OeQ30gbNaK7H/Exv5Ss7Fbejtt8SG6Y4btG+hXhj46Ru m9HxSiiEqqCNtnDeAg/pIdffB3RvgTZNI9uZbgcDgWWD2cCbs4QxtsWyIHzbIlnGCTLs iHl19fZzaB9KgndzqoEq9xf7I2R9SH9bHH9h43BcINNhJlB3GHvq/psSAeJ9mdREcHoF W5CA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=6TyFilXliZJy2d+mBi1GXmZQ03QK7DtnI0MwvDeR4fk=; b=Yntifabgm0dIGdllKFHfFzS98q85RPc13LhG2aIridxx5tcNfyZ5gZeQkBRqANXsAU IACuLx6XGYX8rxnz2kO7qsrotOhAs7MrLro8fjdsakp6FCO4rDM9BAM0Gx8I+HdwHlyY VYTgezyqYgIWVsSAOYTN8jrXExWa46lEnKycQRmg2EygABqgwLCXhZhoiem3UpqawF0Z Ba8qAtTq9jv8vFzZyAIDe5cmOSFy3xVbLIoPyFjmz804lQ7k0ICaouY0KLVYiWbSAG4A Kk+ZRIpMB6pgAQZa/T1Zlya8iTdTQ0G5xmaGGxULGCuVIMztRi2KrfFpJIYB0pvRuXaZ cWmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@endlessm-com.20150623.gappssmtp.com header.s=20150623 header.b=CbgtUtIu; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l5si1245333ejr.75.2020.06.30.01.27.57; Tue, 30 Jun 2020 01:28:21 -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; dkim=pass header.i=@endlessm-com.20150623.gappssmtp.com header.s=20150623 header.b=CbgtUtIu; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731413AbgF3I11 (ORCPT + 99 others); Tue, 30 Jun 2020 04:27:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54212 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731234AbgF3I1Z (ORCPT ); Tue, 30 Jun 2020 04:27:25 -0400 Received: from mail-vs1-xe41.google.com (mail-vs1-xe41.google.com [IPv6:2607:f8b0:4864:20::e41]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 575C4C03E979 for ; Tue, 30 Jun 2020 01:27:25 -0700 (PDT) Received: by mail-vs1-xe41.google.com with SMTP id k7so9375049vso.2 for ; Tue, 30 Jun 2020 01:27:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=endlessm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=6TyFilXliZJy2d+mBi1GXmZQ03QK7DtnI0MwvDeR4fk=; b=CbgtUtIunRLER4yB3euokUNze9d9uxoJ5Et643+JAhV/AIM/JYGkYp6wRKA+vfY3iA 0uAQm/XS5fyEGuSP7fCODzq4WOnnMcbmJ3gK/o7JvnSLN1jQgwmxlvglyiLRjWQ9d1DK G3oWjo9EGntTmCL7rmn/GPZCW7KRREtAD50RPfxk0lOEeSZjbAH7pHnFKQGbA6j+xBDZ YCrEtI4B5ozVcVfRq8vw+uwZ1TvuHkFwgPk+KeC/7qDjTeidEp2fCBxslutoxYfOjZgv jaOhjuq5zqInQz6/KQJkx4+ZKXAhWTrchC/3PioCwpcUw6VsdjcUFu4TAzROH7ulEu72 TY0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=6TyFilXliZJy2d+mBi1GXmZQ03QK7DtnI0MwvDeR4fk=; b=Rc2VJJ3R75RC3XEtjmjew+AdTHaJCsZKAQVu/k+fBo3bqTwj06iDZJr3wL/5ZQNG9E eGbAzYylcMWzuINXACjWVTCNj3Pnjd1Ui8QYXvIKOeC9/OKzKHc/k59febvmEJff6ww0 DuPOi9I2FtNwkIG2zgOW4wigwcgkAFp/hULDY3exbkIsKoI1ZbX5XkbJt/uT8HYK15ML V2mfQEPbrAHBSzpxRq2u+HeirZ5Wv+mEkFRfJYOyzGwefrxTjnJZD62oPJH3Offv4dex VOUeV3TQBRjtEosdkEKbWR7GVF+Dm5JzlBODQfNVZSR8g3h7tV1Ke0fVOm3ahdpG0Q52 ikdg== X-Gm-Message-State: AOAM531oh8akfdg15qXB7hYTgy4WYcndDI59QQ/s7hLfGRfeMXE0NO4b PKVnm+fU0ms/xrCn6xVfwczdz1ZRdlN4/M1ez2nRAw== X-Received: by 2002:a67:1e45:: with SMTP id e66mr13255904vse.95.1593505644125; Tue, 30 Jun 2020 01:27:24 -0700 (PDT) MIME-Version: 1.0 References: <20200526102018.kznh6aglpkqlp6en@gilmour.lan> <20200527091335.7wc3uy67lbz7j4di@gilmour.lan> <20200528073055.znutrhkryzu3grrl@gilmour.lan> <20200602110442.2ceuymhwuomvjj6i@gilmour> <20200629142145.aa2vdfkgeugrze4c@gilmour.lan> In-Reply-To: <20200629142145.aa2vdfkgeugrze4c@gilmour.lan> From: Jian-Hong Pan Date: Tue, 30 Jun 2020 16:26:20 +0800 Message-ID: Subject: Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin To: Maxime Ripard Cc: Daniel Drake , Nicolas Saenz Julienne , Eric Anholt , dri-devel , linux-rpi-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org, Linux Kernel , devicetree , linux-clk@vger.kernel.org, linux-i2c@vger.kernel.org, Linux Upstreaming Team Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Maxime Ripard =E6=96=BC 2020=E5=B9=B46=E6=9C=8829=E6=97= =A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=8810:21=E5=AF=AB=E9=81=93=EF=BC=9A > > Hi! > > On Fri, Jun 05, 2020 at 04:44:51PM +0800, Jian-Hong Pan wrote: > > Maxime Ripard =E6=96=BC 2020=E5=B9=B46=E6=9C=882=E6= =97=A5 =E9=80=B1=E4=BA=8C =E4=B8=8B=E5=8D=887:04=E5=AF=AB=E9=81=93=EF=BC=9A > > > > > > Hi, > > > > > > On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote: > > > > Maxime Ripard =E6=96=BC 2020=E5=B9=B45=E6=9C=88= 28=E6=97=A5 =E9=80=B1=E5=9B=9B =E4=B8=8B=E5=8D=883:30=E5=AF=AB=E9=81=93=EF= =BC=9A > > > > > > > > > > Hi Daniel, > > > > > > > > > > On Wed, May 27, 2020 at 05:15:12PM +0800, Daniel Drake wrote: > > > > > > On Wed, May 27, 2020 at 5:13 PM Maxime Ripard wrote: > > > > > > > I'm about to send a v3 today or tomorrow, I can Cc you (and J= ian-Hong) if you > > > > > > > want. > > > > > > > > > > > > That would be great, although given the potentially inconsisten= t > > > > > > results we've been seeing so far it would be great if you could > > > > > > additionally push a git branch somewhere. > > > > > > That way we can have higher confidence that we are applying exa= ctly > > > > > > the same patches to the same base etc. > > > > > > > > > > So I sent a new iteration yesterday, and of course forgot to cc y= ou... Sorry for > > > > > that. > > > > > > > > > > I've pushed my current branch here: > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git= /log/?h=3Drpi4-kms > > > > > > > > Thanks to Maxime! > > > > > > > > I have tried your repository on branch rpi4-kms. The DRM VC4 is us= ed! > > > > But got some issues: > > > > 1. Some weird error message in dmesg. Not sure it is related, or n= ot > > > > [ 5.219321] [drm:vc5_hdmi_init_resources] *ERROR* Failed to get > > > > HDMI state machine clock > > > > https://gist.github.com/starnight/3f317dca121065a361cf08e91225e389 > > > > > > That's a deferred probing. The first time the HDMI driver is being > > > probed, the firmware clock driver has not been probed yet. It's makin= g > > > another attempt later on, which succeeds. > > > > > > > 2. The screen flashes suddenly sometimes. > > > > I append drm.debug=3D0x3 to boot command. Whenever, the screen flashes= , > > I notice the logs like this: > > > > Jun 01 15:22:40 endless kernel: [drm:drm_calc_timestamping_constants] > > crtc 64: hwmode: htotal 2200, vtotal 1125, vdisplay 1080 > > Jun 01 15:22:40 endless kernel: [drm:drm_calc_timestamping_constants] > > crtc 64: clock 148500 kHz framedur 16666666 linedur 14814 > > Jun 01 15:22:40 endless kernel: [drm:drm_vblank_enable] enabling > > vblank on crtc 3, ret: 0 > > Jun 01 15:22:40 endless kernel: [drm:drm_mode_object_put.part.0] OBJ ID= : 159 (2) > > Jun 01 15:22:40 endless kernel: [drm:drm_mode_object_put.part.0] OBJ ID= : 154 (1) > > Jun 01 15:22:40 endless kernel: [drm:vblank_disable_fn] disabling > > vblank on crtc 3 > > Jun 01 15:22:42 endless kernel: [drm:drm_ioctl] pid=3D584, dev=3D0xe200= , > > auth=3D1, DRM_IOCTL_MODE_CURSOR > > Jun 01 15:22:42 endless kernel: [drm:drm_ioctl] pid=3D584, dev=3D0xe200= , > > auth=3D1, DRM_IOCTL_MODE_CURSOR2 > > Jun 01 15:22:42 endless kernel: [drm:drm_mode_object_get] OBJ ID: 159 (= 1) > > Jun 01 15:22:42 endless kernel: [drm:drm_mode_object_get] OBJ ID: 154 (= 1) > > Jun 01 15:22:42 endless kernel: [drm:drm_calc_timestamping_constants] > > crtc 64: hwmode: htotal 2200, vtotal 1125, vdisplay 1080 > > Jun 01 15:22:42 endless kernel: [drm:drm_calc_timestamping_constants] > > crtc 64: clock 148500 kHz framedur 16666666 linedur 14814 > > Jun 01 15:22:42 endless kernel: [drm:drm_vblank_enable] enabling > > vblank on crtc 3, ret: 0 > > Jun 01 15:22:42 endless kernel: [drm:drm_mode_object_put.part.0] OBJ ID= : 159 (2) > > Jun 01 15:22:42 endless kernel: [drm:drm_mode_object_put.part.0] OBJ ID= : 154 (2) > > > > Here is the full log > > https://gist.github.com/starnight/85d641819839eddc7a55ca7173990a56 > > > > > > 3. The higher resolutions, like 1920x1080 ... are lost after hot > > > > re-plug HDMI cable (HDMI0) > > > > I should explain this in more detail. Here are the steps to reproduce > > this issue: > > 1. Before unplug the HDMI cable from HDMI0 port. > > $ xrandr > > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 2048 x 2048 > > HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x > > axis y axis) 521mm x 293mm > > 1920x1080 60.00*+ 50.00 59.94 > > 1920x1080i 60.00 50.00 59.94 > > 1680x1050 59.88 > > 1280x1024 75.02 60.02 > > 1440x900 59.90 > > 1280x960 60.00 > > 1152x864 75.00 > > 1280x720 60.00 50.00 59.94 > > 1440x576 50.00 > > 1024x768 75.03 70.07 60.00 > > 1440x480 60.00 59.94 > > 832x624 74.55 > > 800x600 72.19 75.00 60.32 56.25 > > 720x576 50.00 > > 720x480 60.00 59.94 > > 640x480 75.00 72.81 66.67 60.00 59.94 > > 720x400 70.08 > > HDMI-2 disconnected (normal left inverted right x axis y axis) > > > > 2. Unplug the HDMI cable from HDMI0 port. > > 3. Plug the HDMI cable to **HDMI1** port. > > $ xrandr > > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 2048 x 2048 > > HDMI-1 disconnected (normal left inverted right x axis y axis) > > HDMI-2 connected primary 1920x1080+0+0 (normal left inverted right x > > axis y axis) 521mm x 293mm > > 1920x1080 60.00*+ 50.00 59.94 > > 1920x1080i 60.00 50.00 59.94 > > 1680x1050 59.88 > > 1280x1024 75.02 60.02 > > 1440x900 59.90 > > 1280x960 60.00 > > 1152x864 75.00 > > 1280x720 60.00 50.00 59.94 > > 1440x576 50.00 > > 1024x768 75.03 70.07 60.00 > > 1440x480 60.00 59.94 > > 832x624 74.55 > > 800x600 72.19 75.00 60.32 56.25 > > 720x576 50.00 > > 720x480 60.00 59.94 > > 640x480 75.00 72.81 66.67 60.00 59.94 > > 720x400 70.08 > > > > 4. Unplug the HDMI cable from **HDMI1** port. > > 5. Plug the HDMI cable back to HDMI0 port. > > $ xrandr > > Screen 0: minimum 320 x 200, current 1368 x 768, maximum 2048 x 2048 > > HDMI-1 connected primary 1368x768+0+0 (normal left inverted right x > > axis y axis) 0mm x 0mm > > 1368x768 59.88* > > 1360x768 59.80 > > 1280x800 59.81 > > 1152x864 60.00 > > 1280x720 59.86 > > 1024x768 60.00 > > 1024x576 59.90 > > 960x540 59.63 > > 800x600 60.32 > > 800x450 59.82 > > 700x450 59.88 > > 640x480 59.94 > > 684x384 59.88 59.85 > > 680x384 59.80 59.96 > > 640x400 59.88 59.98 > > 576x432 60.06 > > 640x360 59.86 59.83 > > 512x384 60.00 > > 512x288 60.00 59.92 > > 480x270 59.63 59.82 > > 400x300 60.32 > > 320x240 60.05 > > HDMI-2 disconnected (normal left inverted right x axis y axis) > > Sorry for getting back at it so late. I just tested with modetest only > and my current branch and it seems to behave properly. Did you had to > run X to get that issue, or is it just how you noticed it? > > Also, was that with the branch based on 5.7 I pushed on my git tree on > kernel.org or some earlier revision of the series? Thanks for coming back :) I use GNOME 3.36 with Xorg 1.20.4. To understand when it starts to hit the issues, I separate to step by step: 1. System boots into command line mode first (systemd multi-user.target) 2. Execute Xorg, then xterm. 3. Execute mutter upon the screen of Xorg. I tried both branches rpi4-kms and rpi4-kms-5.7 of https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git Both of the branches hit issues: * The screen flashes suddenly sometimes. This happens after mutter is laun= ched. * The higher resolutions, like 1920x1080 ... are lost after hot re-plug HDMI cable (HDMI0). HDMI cable connects to HDMI0 -> HDMI1 -> HDMI0. This happens not only with GNOME, but also pure Xorg. Jian-Hong Pan