Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi Maxime, On Tue, May 26, 2020 at 6:20 PM Maxime Ripard wrote: > I gave it a try with U-Boot with my latest work and couldn't reproduce it, so > it > seems that I fixed it along the way Is your latest work available in a git branch anywhere that we could test directly? Thanks Daniel
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi Daniel, On Wed, May 27, 2020 at 11:49:36AM +0800, Daniel Drake wrote: > Hi Maxime, > > On Tue, May 26, 2020 at 6:20 PM Maxime Ripard wrote: > > I gave it a try with U-Boot with my latest work and couldn't reproduce it, > > so it > > seems that I fixed it along the way > > Is your latest work available in a git branch anywhere that we could > test directly? I'm about to send a v3 today or tomorrow, I can Cc you (and Jian-Hong) if you want. Maxime signature.asc Description: PGP signature
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
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 Jian-Hong) if you > want. That would be great, although given the potentially inconsistent 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 exactly the same patches to the same base etc. Thanks Daniel
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi, On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote: > Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道： > > > > 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 Jian-Hong) > > > > if you > > > > want. > > > > > > That would be great, although given the potentially inconsistent > > > 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 exactly > > > the same patches to the same base etc. > > > > So I sent a new iteration yesterday, and of course forgot to cc you... > > Sorry for > > that. > > > > I've pushed my current branch here: > > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms > > Thanks to Maxime! > > I have tried your repository on branch rpi4-kms. The DRM VC4 is used! > But got some issues: > 1. Some weird error message in dmesg. Not sure it is related, or not > [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 making another attempt later on, which succeeds. > 2. The screen flashes suddenly sometimes. > > 3. The higher resolutions, like 1920x1080 ... are lost after hot > re-plug HDMI cable (HDMI0) I'm not sure on how to exactly reproduce those issues (or what they are) though, can you expand on this? Maxime signature.asc Description: PGP signature
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
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 Jian-Hong) if > > you > > want. > > That would be great, although given the potentially inconsistent > 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 exactly > the same patches to the same base etc. So I sent a new iteration yesterday, and of course forgot to cc you... Sorry for that. I've pushed my current branch here: https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms Maxime signature.asc Description: PGP signature
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi, On Mon, May 11, 2020 at 11:12:05AM +0800, Jian-Hong Pan wrote: > Jian-Hong Pan 於 2020年5月8日 週五 下午2:20寫道： > > > > Maxime Ripard 於 2020年5月8日 週五 上午1:22寫道： > > > > > > On Mon, May 04, 2020 at 02:35:08PM +0800, Jian-Hong Pan wrote: > > > > Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > > > > > > > > > Hi, > > > > > > > > > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > > > > > > Hi Maxime, > > > > > > > > > > > > Thanks for your V2 patch series! I'm testing it. > > > > > > > > > > > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly > > > > > > and built. > > > > > > System can boot into console text mode, but no graphic UI. > > > > > > > > > > > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > > > > > > > > > > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > > > > > > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent > > > > > > 'vc4-hdmi' already present! > > > > > > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> > > > > > > fef00700.hdmi mapping ok > > > > > > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > > > > > > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > > > > > > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > > > > > > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' > > > > > > already present! > > > > > > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> > > > > > > fef05700.hdmi mapping ok > > > > > > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > > > > > > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > > > > > > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > > > > > > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > > > > > > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > > > > > > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 > > > > > > ) > > > > > > [5.589297] fb0: switching to vc4drmfb from simple > > > > > > [5.589433] Console: switching to colour dummy device 80x25 > > > > > > [5.589481] [drm] Supports vblank timestamp caching Rev 2 > > > > > > (21.10.2013). > > > > > > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on > > > > > > minor 0 > > > > > > [5.601079] [ cut here ] > > > > > > [5.601095] WARNING: CPU: 2 PID: 127 at > > > > > > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 > > > > > > vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > > [5.601097] Modules linked in: > > > > > > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > > > > > > 5.7.0-rc2-00091-ga181df59a930 #7 > > > > > > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > > > > > > [5.601112] Workqueue: events deferred_probe_work_func > > > > > > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > > > > > > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > > > [5.601124] sp : 80001217b410 > > > > > > [5.601126] x29: 80001217b410 x28: ec6370f0 > > > > > > [5.601129] x27: f650d400 x26: 8a50 > > > > > > [5.601132] x25: 8000113b4ac0 x24: 2060 > > > > > > [5.601135] x23: 0a50 x22: 0300 > > > > > > [5.601137] x21: 08d9ee20 x20: ec535080 > > > > > > [5.601140] x19: 00010989e7c0 x18: > > > > > > [5.601142] x17: 0001 x16: 5207 > > > > > > [5.601145] x15: 4932ad293c92 x14: 0137 > > > > > > [5.601147] x13: 800010015000 x12: 0001 > > > > > > [5.601150] x11: 0001 x10: > > > > > > [5.601152] x9 : x8 : 800010015038 > > > > > > [5.601154] x7 : 0001 x6 : 80001217b368 > > > > > > [5.601157] x5 : x4 : 004c > > > > > > [5.601159] x3 : x2 : 8000113b4ac0 > > > > > > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > > > > > > [5.601164] Call trace: > > > > > > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > > > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > > > > > > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > > > > > > [5.601182] v
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi, On Mon, May 11, 2020 at 11:12:05AM +0800, Jian-Hong Pan wrote: > Jian-Hong Pan 於 2020年5月8日 週五 下午2:20寫道： > > > > Maxime Ripard 於 2020年5月8日 週五 上午1:22寫道： > > > > > > On Mon, May 04, 2020 at 02:35:08PM +0800, Jian-Hong Pan wrote: > > > > Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > > > > > > > > > Hi, > > > > > > > > > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > > > > > > Hi Maxime, > > > > > > > > > > > > Thanks for your V2 patch series! I'm testing it. > > > > > > > > > > > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly > > > > > > and built. > > > > > > System can boot into console text mode, but no graphic UI. > > > > > > > > > > > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > > > > > > > > > > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > > > > > > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent > > > > > > 'vc4-hdmi' already present! > > > > > > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> > > > > > > fef00700.hdmi mapping ok > > > > > > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > > > > > > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > > > > > > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > > > > > > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' > > > > > > already present! > > > > > > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> > > > > > > fef05700.hdmi mapping ok > > > > > > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > > > > > > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > > > > > > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > > > > > > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > > > > > > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > > > > > > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops > > > > > > vc4_crtc_ops) > > > > > > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 > > > > > > ) > > > > > > [5.589297] fb0: switching to vc4drmfb from simple > > > > > > [5.589433] Console: switching to colour dummy device 80x25 > > > > > > [5.589481] [drm] Supports vblank timestamp caching Rev 2 > > > > > > (21.10.2013). > > > > > > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on > > > > > > minor 0 > > > > > > [5.601079] [ cut here ] > > > > > > [5.601095] WARNING: CPU: 2 PID: 127 at > > > > > > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 > > > > > > vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > > [5.601097] Modules linked in: > > > > > > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > > > > > > 5.7.0-rc2-00091-ga181df59a930 #7 > > > > > > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > > > > > > [5.601112] Workqueue: events deferred_probe_work_func > > > > > > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > > > > > > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > > > [5.601124] sp : 80001217b410 > > > > > > [5.601126] x29: 80001217b410 x28: ec6370f0 > > > > > > [5.601129] x27: f650d400 x26: 8a50 > > > > > > [5.601132] x25: 8000113b4ac0 x24: 2060 > > > > > > [5.601135] x23: 0a50 x22: 0300 > > > > > > [5.601137] x21: 08d9ee20 x20: ec535080 > > > > > > [5.601140] x19: 00010989e7c0 x18: > > > > > > [5.601142] x17: 0001 x16: 5207 > > > > > > [5.601145] x15: 4932ad293c92 x14: 0137 > > > > > > [5.601147] x13: 800010015000 x12: 0001 > > > > > > [5.601150] x11: 0001 x10: > > > > > > [5.601152] x9 : x8 : 800010015038 > > > > > > [5.601154] x7 : 0001 x6 : 80001217b368 > > > > > > [5.601157] x5 : x4 : 004c > > > > > > [5.601159] x3 : x2 : 8000113b4ac0 > > > > > > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > > > > > > [5.601164] Call trace: > > > > > > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > > > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > > > > > > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > > > > > > [5.601182] v
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道： > > 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 Jian-Hong) if > > > you > > > want. > > > > That would be great, although given the potentially inconsistent > > 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 exactly > > the same patches to the same base etc. > > So I sent a new iteration yesterday, and of course forgot to cc you... Sorry > for > that. > > I've pushed my current branch here: > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms Thanks to Maxime! I have tried your repository on branch rpi4-kms. The DRM VC4 is used! But got some issues: 1. Some weird error message in dmesg. Not sure it is related, or not [5.219321] [drm:vc5_hdmi_init_resources] *ERROR* Failed to get HDMI state machine clock https://gist.github.com/starnight/3f317dca121065a361cf08e91225e389 2. The screen flashes suddenly sometimes. 3. The higher resolutions, like 1920x1080 ... are lost after hot re-plug HDMI cable (HDMI0) Jian-Hong Pan
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Maxime Ripard 於 2020年6月2日 週二 下午7:04寫道： > > Hi, > > On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote: > > Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道： > > > > > > 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 > > > > > Jian-Hong) if you > > > > > want. > > > > > > > > That would be great, although given the potentially inconsistent > > > > 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 exactly > > > > the same patches to the same base etc. > > > > > > So I sent a new iteration yesterday, and of course forgot to cc you... > > > Sorry for > > > that. > > > > > > I've pushed my current branch here: > > > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms > > > > Thanks to Maxime! > > > > I have tried your repository on branch rpi4-kms. The DRM VC4 is used! > > But got some issues: > > 1. Some weird error message in dmesg. Not sure it is related, or not > > [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 making > another attempt later on, which succeeds. > > > 2. The screen flashes suddenly sometimes. I append drm.debug=0x3 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 1666 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=584, dev=0xe200, auth=1, DRM_IOCTL_MODE_CURSOR Jun 01 15:22:42 endless kernel: [drm:drm_ioctl] pid=584, dev=0xe200, auth=1, 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 1666 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.0059.94 1920x1080i60.0050.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1152x864 75.00 1280x720 60.0050.0059.94 1440x576 50.00 1024x768 75.0370.0760.00 1440x480 60.0059.94 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.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.0059.94 1920x1080i60.0050.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1152x864 75.00 1280x720 60.0050.0059.94 1440x576 50.00 1024x768 75.0370.0760.00 1440x480 60.0059.94 832x624 74.55 800x600 72.1975.00
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
On Mon, May 04, 2020 at 02:35:08PM +0800, Jian-Hong Pan wrote: > Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > > > Hi, > > > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > > > Hi Maxime, > > > > > > Thanks for your V2 patch series! I'm testing it. > > > > > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly and > > > built. > > > System can boot into console text mode, but no graphic UI. > > > > > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > > > > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > > > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi' > > > already present! > > > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> fef00700.hdmi > > > mapping ok > > > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > > > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > > > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > > > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' already > > > present! > > > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> fef05700.hdmi > > > mapping ok > > > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > > > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > > > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > > > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > > > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > > > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops) > > > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops) > > > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops) > > > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops) > > > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops) > > > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 > > > ) > > > [5.589297] fb0: switching to vc4drmfb from simple > > > [5.589433] Console: switching to colour dummy device 80x25 > > > [5.589481] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 > > > [5.601079] [ cut here ] > > > [5.601095] WARNING: CPU: 2 PID: 127 at > > > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 vc5_hdmi_phy_init+0x7ac/0x2078 > > > [5.601097] Modules linked in: > > > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > > > 5.7.0-rc2-00091-ga181df59a930 #7 > > > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > > > [5.601112] Workqueue: events deferred_probe_work_func > > > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > > > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > > > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > [5.601124] sp : 80001217b410 > > > [5.601126] x29: 80001217b410 x28: ec6370f0 > > > [5.601129] x27: f650d400 x26: 8a50 > > > [5.601132] x25: 8000113b4ac0 x24: 2060 > > > [5.601135] x23: 0a50 x22: 0300 > > > [5.601137] x21: 08d9ee20 x20: ec535080 > > > [5.601140] x19: 00010989e7c0 x18: > > > [5.601142] x17: 0001 x16: 5207 > > > [5.601145] x15: 4932ad293c92 x14: 0137 > > > [5.601147] x13: 800010015000 x12: 0001 > > > [5.601150] x11: 0001 x10: > > > [5.601152] x9 : x8 : 800010015038 > > > [5.601154] x7 : 0001 x6 : 80001217b368 > > > [5.601157] x5 : x4 : 004c > > > [5.601159] x3 : x2 : 8000113b4ac0 > > > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > > > [5.601164] Call trace: > > > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > > > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > > > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > > > [5.601182] vc4_atomic_commit+0x1e0/0x200 > > > [5.601185] drm_atomic_commit+0x4c/0x60 > > > [5.601190] drm_client_modeset_commit_atomic.isra.0+0x17c/0x238 > > > [5.601192] drm_client_modeset_commit_locked+0x5c/0x198 > > > [5.601195] drm_client_modeset_commit+0x30/0x58 > > > [5.601201] drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xe0 > > > [5.601204] drm_fb_helper_set_par+0x30/0x68 > > > [5.601208] fbcon_init+0x3d4/0x598 > > > [5.601212] visual_init+0xb0/0x108 > > > [5.601214] do_bind_con_driver+0x1d0/0x3a8 > > > [5.601217] do_take_over_console+0x144/0x208 > > > [5.601219] do_fbcon_takeover+0x68/0xd8 > > > [5.601222] fbcon_fb_registered+0x100/0x118 > > > [5.601226] r
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Maxime Ripard 於 2020年5月8日 週五 上午1:22寫道： > > On Mon, May 04, 2020 at 02:35:08PM +0800, Jian-Hong Pan wrote: > > Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > > > > > Hi, > > > > > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > > > > Hi Maxime, > > > > > > > > Thanks for your V2 patch series! I'm testing it. > > > > > > > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly and > > > > built. > > > > System can boot into console text mode, but no graphic UI. > > > > > > > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > > > > > > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > > > > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent > > > > 'vc4-hdmi' already present! > > > > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> fef00700.hdmi > > > > mapping ok > > > > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > > > > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > > > > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > > > > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' already > > > > present! > > > > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> fef05700.hdmi > > > > mapping ok > > > > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > > > > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > > > > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > > > > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > > > > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > > > > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops) > > > > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops) > > > > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops) > > > > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops) > > > > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops) > > > > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 > > > > ) > > > > [5.589297] fb0: switching to vc4drmfb from simple > > > > [5.589433] Console: switching to colour dummy device 80x25 > > > > [5.589481] [drm] Supports vblank timestamp caching Rev 2 > > > > (21.10.2013). > > > > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 > > > > [5.601079] [ cut here ] > > > > [5.601095] WARNING: CPU: 2 PID: 127 at > > > > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 vc5_hdmi_phy_init+0x7ac/0x2078 > > > > [5.601097] Modules linked in: > > > > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > > > > 5.7.0-rc2-00091-ga181df59a930 #7 > > > > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > > > > [5.601112] Workqueue: events deferred_probe_work_func > > > > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > > > > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > > > > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > [5.601124] sp : 80001217b410 > > > > [5.601126] x29: 80001217b410 x28: ec6370f0 > > > > [5.601129] x27: f650d400 x26: 8a50 > > > > [5.601132] x25: 8000113b4ac0 x24: 2060 > > > > [5.601135] x23: 0a50 x22: 0300 > > > > [5.601137] x21: 08d9ee20 x20: ec535080 > > > > [5.601140] x19: 00010989e7c0 x18: > > > > [5.601142] x17: 0001 x16: 5207 > > > > [5.601145] x15: 4932ad293c92 x14: 0137 > > > > [5.601147] x13: 800010015000 x12: 0001 > > > > [5.601150] x11: 0001 x10: > > > > [5.601152] x9 : x8 : 800010015038 > > > > [5.601154] x7 : 0001 x6 : 80001217b368 > > > > [5.601157] x5 : x4 : 004c > > > > [5.601159] x3 : x2 : 8000113b4ac0 > > > > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > > > > [5.601164] Call trace: > > > > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > > > > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > > > > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > > > > [5.601182] vc4_atomic_commit+0x1e0/0x200 > > > > [5.601185] drm_atomic_commit+0x4c/0x60 > > > > [5.601190] drm_client_modeset_commit_atomic.isra.0+0x17c/0x238 > > > > [5.601192] drm_client_modeset_commit_locked+0x5c/0x198 > > > > [5.601195] drm_client_modeset_commit+0x30/0x58 > > > > [5.601201] drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xe0 > > > > [5.601204] drm_fb_helper_set_par+0x30/0x68 > > > > [5.601208] fbcon_init+0x3d4/0x598 > > > > [5.601212] visual_init+0xb0/0x108 > > > > [5
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > Hi, > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > > Hi Maxime, > > > > Thanks for your V2 patch series! I'm testing it. > > > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly and built. > > System can boot into console text mode, but no graphic UI. > > > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi' > > already present! > > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> fef00700.hdmi > > mapping ok > > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' already > > present! > > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> fef05700.hdmi > > mapping ok > > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops) > > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops) > > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops) > > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops) > > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops) > > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 ) > > [5.589297] fb0: switching to vc4drmfb from simple > > [5.589433] Console: switching to colour dummy device 80x25 > > [5.589481] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 > > [5.601079] [ cut here ] > > [5.601095] WARNING: CPU: 2 PID: 127 at > > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 vc5_hdmi_phy_init+0x7ac/0x2078 > > [5.601097] Modules linked in: > > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > > 5.7.0-rc2-00091-ga181df59a930 #7 > > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > > [5.601112] Workqueue: events deferred_probe_work_func > > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > [5.601124] sp : 80001217b410 > > [5.601126] x29: 80001217b410 x28: ec6370f0 > > [5.601129] x27: f650d400 x26: 8a50 > > [5.601132] x25: 8000113b4ac0 x24: 2060 > > [5.601135] x23: 0a50 x22: 0300 > > [5.601137] x21: 08d9ee20 x20: ec535080 > > [5.601140] x19: 00010989e7c0 x18: > > [5.601142] x17: 0001 x16: 5207 > > [5.601145] x15: 4932ad293c92 x14: 0137 > > [5.601147] x13: 800010015000 x12: 0001 > > [5.601150] x11: 0001 x10: > > [5.601152] x9 : x8 : 800010015038 > > [5.601154] x7 : 0001 x6 : 80001217b368 > > [5.601157] x5 : x4 : 004c > > [5.601159] x3 : x2 : 8000113b4ac0 > > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > > [5.601164] Call trace: > > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > > [5.601182] vc4_atomic_commit+0x1e0/0x200 > > [5.601185] drm_atomic_commit+0x4c/0x60 > > [5.601190] drm_client_modeset_commit_atomic.isra.0+0x17c/0x238 > > [5.601192] drm_client_modeset_commit_locked+0x5c/0x198 > > [5.601195] drm_client_modeset_commit+0x30/0x58 > > [5.601201] drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xe0 > > [5.601204] drm_fb_helper_set_par+0x30/0x68 > > [5.601208] fbcon_init+0x3d4/0x598 > > [5.601212] visual_init+0xb0/0x108 > > [5.601214] do_bind_con_driver+0x1d0/0x3a8 > > [5.601217] do_take_over_console+0x144/0x208 > > [5.601219] do_fbcon_takeover+0x68/0xd8 > > [5.601222] fbcon_fb_registered+0x100/0x118 > > [5.601226] register_framebuffer+0x1f4/0x338 > > [5.601229] __drm_fb_helper_initial_config_and_unlock+0x2f8/0x4a0 > > [5.601232] drm_fbdev_client_hotplug+0xd4/0x1b0 > > [5.601235] drm_fbdev_generic_setup+0xb0/0x130 > > [5.601238] vc4_drm_bind+0
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Jian-Hong Pan 於 2020年5月8日 週五 下午2:20寫道： > > Maxime Ripard 於 2020年5月8日 週五 上午1:22寫道： > > > > On Mon, May 04, 2020 at 02:35:08PM +0800, Jian-Hong Pan wrote: > > > Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > > > > > > > Hi, > > > > > > > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > > > > > Hi Maxime, > > > > > > > > > > Thanks for your V2 patch series! I'm testing it. > > > > > > > > > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly and > > > > > built. > > > > > System can boot into console text mode, but no graphic UI. > > > > > > > > > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > > > > > > > > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > > > > > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent > > > > > 'vc4-hdmi' already present! > > > > > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> > > > > > fef00700.hdmi mapping ok > > > > > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > > > > > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > > > > > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > > > > > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' > > > > > already present! > > > > > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> > > > > > fef05700.hdmi mapping ok > > > > > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > > > > > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > > > > > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > > > > > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > > > > > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > > > > > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops > > > > > vc4_crtc_ops) > > > > > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops > > > > > vc4_crtc_ops) > > > > > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops > > > > > vc4_crtc_ops) > > > > > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops > > > > > vc4_crtc_ops) > > > > > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops > > > > > vc4_crtc_ops) > > > > > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 > > > > > ) > > > > > [5.589297] fb0: switching to vc4drmfb from simple > > > > > [5.589433] Console: switching to colour dummy device 80x25 > > > > > [5.589481] [drm] Supports vblank timestamp caching Rev 2 > > > > > (21.10.2013). > > > > > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 > > > > > [5.601079] [ cut here ] > > > > > [5.601095] WARNING: CPU: 2 PID: 127 at > > > > > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > [5.601097] Modules linked in: > > > > > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > > > > > 5.7.0-rc2-00091-ga181df59a930 #7 > > > > > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > > > > > [5.601112] Workqueue: events deferred_probe_work_func > > > > > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > > > > > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > > [5.601124] sp : 80001217b410 > > > > > [5.601126] x29: 80001217b410 x28: ec6370f0 > > > > > [5.601129] x27: f650d400 x26: 8a50 > > > > > [5.601132] x25: 8000113b4ac0 x24: 2060 > > > > > [5.601135] x23: 0a50 x22: 0300 > > > > > [5.601137] x21: 08d9ee20 x20: ec535080 > > > > > [5.601140] x19: 00010989e7c0 x18: > > > > > [5.601142] x17: 0001 x16: 5207 > > > > > [5.601145] x15: 4932ad293c92 x14: 0137 > > > > > [5.601147] x13: 800010015000 x12: 0001 > > > > > [5.601150] x11: 0001 x10: > > > > > [5.601152] x9 : x8 : 800010015038 > > > > > [5.601154] x7 : 0001 x6 : 80001217b368 > > > > > [5.601157] x5 : x4 : 004c > > > > > [5.601159] x3 : x2 : 8000113b4ac0 > > > > > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > > > > > [5.601164] Call trace: > > > > > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > > > > > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > > > > > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > > > > > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > > > > > [5.601182] vc4_atomic_commit+0x1e0/0x200 > > > > > [5.601185] drm_atomic_commit+0x4c/0x60 > > > > > [5.601190] drm_client_modeset_commit_atomic.isra.0+0x17c/0x238 > > > > > [5.601192] drm_client_modeset_commit_locked+0x5c/0x198 > > > > > [5.601195] drm_client_
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi, On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan wrote: > Hi Maxime, > > Thanks for your V2 patch series! I'm testing it. > > This patch series is applied upon mainline kernel 5.7-rc2 cleanly and built. > System can boot into console text mode, but no graphic UI. > > Get the error in vc5_hdmi_phy_init(), and full dmesg is at [1]: > > [5.587543] vc4_hdmi fef00700.hdmi: Unknown register ID 46 > [5.587700] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi' > already present! > [5.588070] vc4_hdmi fef00700.hdmi: vc4-hdmi-hifi <-> fef00700.hdmi > mapping ok > [5.588076] vc4_hdmi fef00700.hdmi: ASoC: no DMI vendor name! > [5.588263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops) > [5.588299] vc4_hdmi fef05700.hdmi: Unknown register ID 46 > [5.588373] debugfs: Directory 'vc4-hdmi' with parent 'asoc' already > present! > [5.588673] vc4_hdmi fef05700.hdmi: vc4-hdmi-hifi <-> fef05700.hdmi > mapping ok > [5.588677] vc4_hdmi fef05700.hdmi: ASoC: no DMI vendor name! > [5.588809] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops) > [5.588854] vc4-drm gpu: bound fe806000.vec (ops vc4_vec_ops) > [5.588897] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops) > [5.588934] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops) > [5.588990] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops) > [5.589030] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops) > [5.589074] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops) > [5.589106] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops) > [5.589145] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops) > [5.589294] checking generic (3e513000 6d8c00) vs hw (0 ) > [5.589297] fb0: switching to vc4drmfb from simple > [5.589433] Console: switching to colour dummy device 80x25 > [5.589481] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [5.589816] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 > [5.601079] [ cut here ] > [5.601095] WARNING: CPU: 2 PID: 127 at > drivers/gpu/drm/vc4/vc4_hdmi_phy.c:413 vc5_hdmi_phy_init+0x7ac/0x2078 > [5.601097] Modules linked in: > [5.601103] CPU: 2 PID: 127 Comm: kworker/2:1 Not tainted > 5.7.0-rc2-00091-ga181df59a930 #7 > [5.601105] Hardware name: Raspberry Pi 4 Model B (DT) > [5.601112] Workqueue: events deferred_probe_work_func > [5.601116] pstate: 2005 (nzCv daif -PAN -UAO) > [5.601119] pc : vc5_hdmi_phy_init+0x7ac/0x2078 > [5.601123] lr : vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > [5.601124] sp : 80001217b410 > [5.601126] x29: 80001217b410 x28: ec6370f0 > [5.601129] x27: f650d400 x26: 8a50 > [5.601132] x25: 8000113b4ac0 x24: 2060 > [5.601135] x23: 0a50 x22: 0300 > [5.601137] x21: 08d9ee20 x20: ec535080 > [5.601140] x19: 00010989e7c0 x18: > [5.601142] x17: 0001 x16: 5207 > [5.601145] x15: 4932ad293c92 x14: 0137 > [5.601147] x13: 800010015000 x12: 0001 > [5.601150] x11: 0001 x10: > [5.601152] x9 : x8 : 800010015038 > [5.601154] x7 : 0001 x6 : 80001217b368 > [5.601157] x5 : x4 : 004c > [5.601159] x3 : x2 : 8000113b4ac0 > [5.601162] x1 : 8000120c5f44 x0 : dc8984ff > [5.601164] Call trace: > [5.601169] vc5_hdmi_phy_init+0x7ac/0x2078 > [5.601172] vc4_hdmi_encoder_enable+0x1b8/0x1ac0 > [5.601176] drm_atomic_helper_commit_modeset_enables+0x224/0x248 > [5.601179] vc4_atomic_complete_commit+0x400/0x558 > [5.601182] vc4_atomic_commit+0x1e0/0x200 > [5.601185] drm_atomic_commit+0x4c/0x60 > [5.601190] drm_client_modeset_commit_atomic.isra.0+0x17c/0x238 > [5.601192] drm_client_modeset_commit_locked+0x5c/0x198 > [5.601195] drm_client_modeset_commit+0x30/0x58 > [5.601201] drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xe0 > [5.601204] drm_fb_helper_set_par+0x30/0x68 > [5.601208] fbcon_init+0x3d4/0x598 > [5.601212] visual_init+0xb0/0x108 > [5.601214] do_bind_con_driver+0x1d0/0x3a8 > [5.601217] do_take_over_console+0x144/0x208 > [5.601219] do_fbcon_takeover+0x68/0xd8 > [5.601222] fbcon_fb_registered+0x100/0x118 > [5.601226] register_framebuffer+0x1f4/0x338 > [5.601229] __drm_fb_helper_initial_config_and_unlock+0x2f8/0x4a0 > [5.601232] drm_fbdev_client_hotplug+0xd4/0x1b0 > [5.601235] drm_fbdev_generic_setup+0xb0/0x130 > [5.601238] vc4_drm_bind+0x184/0x1a0 > [5.601241] try_to_bring_up_master+0x168/0x1c8 > [5.601244] __component_add+0xa4/0x170 > [5.601246] component_add+0x14/0x20 > [5.601248] vc4_vec_dev_probe+0x20/0x30 > [
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Maxime Ripard 於 2020年6月29日 週一 下午10:21寫道： > > Hi! > > On Fri, Jun 05, 2020 at 04:44:51PM +0800, Jian-Hong Pan wrote: > > Maxime Ripard 於 2020年6月2日 週二 下午7:04寫道： > > > > > > Hi, > > > > > > On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote: > > > > Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道： > > > > > > > > > > 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 > > > > > > > Jian-Hong) if you > > > > > > > want. > > > > > > > > > > > > That would be great, although given the potentially inconsistent > > > > > > 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 exactly > > > > > > the same patches to the same base etc. > > > > > > > > > > So I sent a new iteration yesterday, and of course forgot to cc > > > > > you... Sorry for > > > > > that. > > > > > > > > > > I've pushed my current branch here: > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms > > > > > > > > Thanks to Maxime! > > > > > > > > I have tried your repository on branch rpi4-kms. The DRM VC4 is used! > > > > But got some issues: > > > > 1. Some weird error message in dmesg. Not sure it is related, or not > > > > [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 making > > > another attempt later on, which succeeds. > > > > > > > 2. The screen flashes suddenly sometimes. > > > > I append drm.debug=0x3 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 1666 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=584, dev=0xe200, > > auth=1, DRM_IOCTL_MODE_CURSOR > > Jun 01 15:22:42 endless kernel: [drm:drm_ioctl] pid=584, dev=0xe200, > > auth=1, 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 1666 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.0059.94 > >1920x1080i60.0050.0059.94 > >1680x1050 59.88 > >1280x1024 75.0260.02 > >1440x900 59.90 > >1280x960 60.00 > >1152x864 75.00 > >1280x720 60.0050.0059.94 > >1440x576 50.00 > >1024x768 75.0370.0760.00 > >1440x480 60.0059.94 > >832x624 74.55 > >800x600 72.1975.0060.3256.25 > >720x576 50.00 > >720x480 60.0059.94 > >640x480 75.0072.8166.6760.0059.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, maxi
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi! On Fri, Jun 05, 2020 at 04:44:51PM +0800, Jian-Hong Pan wrote: > Maxime Ripard 於 2020年6月2日 週二 下午7:04寫道： > > > > Hi, > > > > On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote: > > > Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道： > > > > > > > > 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 > > > > > > Jian-Hong) if you > > > > > > want. > > > > > > > > > > That would be great, although given the potentially inconsistent > > > > > 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 exactly > > > > > the same patches to the same base etc. > > > > > > > > So I sent a new iteration yesterday, and of course forgot to cc you... > > > > Sorry for > > > > that. > > > > > > > > I've pushed my current branch here: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms > > > > > > Thanks to Maxime! > > > > > > I have tried your repository on branch rpi4-kms. The DRM VC4 is used! > > > But got some issues: > > > 1. Some weird error message in dmesg. Not sure it is related, or not > > > [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 making > > another attempt later on, which succeeds. > > > > > 2. The screen flashes suddenly sometimes. > > I append drm.debug=0x3 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 1666 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=584, dev=0xe200, > auth=1, DRM_IOCTL_MODE_CURSOR > Jun 01 15:22:42 endless kernel: [drm:drm_ioctl] pid=584, dev=0xe200, > auth=1, 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 1666 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.0059.94 >1920x1080i60.0050.0059.94 >1680x1050 59.88 >1280x1024 75.0260.02 >1440x900 59.90 >1280x960 60.00 >1152x864 75.00 >1280x720 60.0050.0059.94 >1440x576 50.00 >1024x768 75.0370.0760.00 >1440x480 60.0059.94 >832x624 74.55 >800x600 72.1975.0060.3256.25 >720x576 50.00 >720x480 60.0059.94 >640x480 75.0072.8166.6760.0059.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.0059.94 >1920x1080i60.0050.0059.94
Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin
Hi, On Tue, Jun 30, 2020 at 04:26:20PM +0800, Jian-Hong Pan wrote: > Maxime Ripard 於 2020年6月29日 週一 下午10:21寫道： > > > > Hi! > > > > On Fri, Jun 05, 2020 at 04:44:51PM +0800, Jian-Hong Pan wrote: > > > Maxime Ripard 於 2020年6月2日 週二 下午7:04寫道： > > > > > > > > Hi, > > > > > > > > On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote: > > > > > Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道： > > > > > > > > > > > > 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 > > > > > > > > Jian-Hong) if you > > > > > > > > want. > > > > > > > > > > > > > > That would be great, although given the potentially inconsistent > > > > > > > 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 > > > > > > > exactly > > > > > > > the same patches to the same base etc. > > > > > > > > > > > > So I sent a new iteration yesterday, and of course forgot to cc > > > > > > you... Sorry for > > > > > > that. > > > > > > > > > > > > I've pushed my current branch here: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/log/?h=rpi4-kms > > > > > > > > > > Thanks to Maxime! > > > > > > > > > > I have tried your repository on branch rpi4-kms. The DRM VC4 is used! > > > > > But got some issues: > > > > > 1. Some weird error message in dmesg. Not sure it is related, or not > > > > > [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 making > > > > another attempt later on, which succeeds. > > > > > > > > > 2. The screen flashes suddenly sometimes. > > > > > > I append drm.debug=0x3 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 1666 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=584, dev=0xe200, > > > auth=1, DRM_IOCTL_MODE_CURSOR > > > Jun 01 15:22:42 endless kernel: [drm:drm_ioctl] pid=584, dev=0xe200, > > > auth=1, 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 1666 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.0059.94 > > >1920x1080i60.0050.0059.94 > > >1680x1050 59.88 > > >1280x1024 75.0260.02 > > >1440x900 59.90 > > >1280x960 60.00 > > >1152x864 75.00 > > >1280x720 60.0050.0059.94 > > >1440x576 50.00 > > >1024x768 75.0370.0760.00 > > >1440x480 60.0059.94 > > >832x624 74.55 > > >800x600 72.1975.0060.3256.25 > > >720x576 50.00 > > >720x480 60.0059.94 > > >640x480
