Re: [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D
From: Stefan Wahren
Date: Fri Mar 13 2020 - 09:59:35 EST
Hi Nicolas,
Am 09.03.20 um 20:22 schrieb Nicolas Saenz Julienne:
> Hi Stefan,
>
> On Mon, 2020-03-09 at 16:41 +0100, Stefan Wahren wrote:
>> Hi Nicolas,
>>
>> On 06.03.20 21:33, Stefan Wahren wrote:
>>> Hi Nicolas,
>>>
>>> Am 05.03.20 um 11:44 schrieb Nicolas Saenz Julienne:
>>>> Hi Stefan,
>>>>
>>>> On Tue, 2020-03-03 at 20:24 +0100, Stefan Wahren wrote:
>>>>>>>> Note: I tested this on RPi3b, RPi3a+ and RPi2b.
>>>>>>> as i already wrote this prevent X to start on current Raspbian on my
>>>>>>> Raspberry Pi 3A+ (multi_v7_defconfig, no u-boot). We must be careful
>>>>>>> here.
>>>>>>>
>>>>>>> I will take a look at the debug UART. Maybe there are more helpful
>>>>>>> information.
>>>>>> It seems we're seeing different things, I tested this on raspbian
>>>>>> (multi_v7_defconfig) and on arm64. I'll try again from scratch
>>>>>> tomorrow.
>>>>> My modifications to the Raspbian image (from 13.2.2020) are little:
>>>>>
>>>>> - specify devicetree to config.txt
>>>>> - change console to ttyS1 and remove "silent" in cmdline.txt
>>>>> - rename all original kernel7*.img
>>>>> - copy dtb and kernel7.img to boot partition
>>>>> - copy kernel modules to root partition
>>>> Would you mind retesting with the latest linux-next? I validated an image
>>>> based
>>>> on 5.6.0-rc4-next-20200305-00001-g285a7a64cd56 and a fresh raspbian
>>>> download on
>>>> RPi3a+ without X issues.
>>> i retested with todays linux-next and the issue persists on my RPi 3A+ /
>>> HP ZR2440w with this patch applied.
>> I tested my display with a RPI 3B, 3B+ and a Zero W. All of them had the
>> same issue. Btw i used this display the last years for testing the
>> Raspberry Pi.
>>
>> After that i connected the RPI 3B to my TV screen and it works with the
>> patch applied.
> Thanks for taking the time on this. I guess all we have left is looking deeper
> into it. I'll add it to my backlog for now.
i've a small progress on this issue. Without this patch applied the
simple framebuffer driver seems to win against vc4 ( = "good case" ):
[ÂÂÂ 13.400] (II) systemd-logind: logind integration requires -keeptty
and -keeptty was not provided, disabling logind integration
[ÂÂÂ 13.402] (II) no primary bus or device found
[ÂÂÂ 13.402] (II) LoadModule: "glx"
[ÂÂÂ 13.405] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ÂÂÂ 13.465] (II) Module glx: vendor="X.Org Foundation"
[ÂÂÂ 13.465] ÂÂÂ compiled for 1.20.4, module version = 1.0.0
[ÂÂÂ 13.465] ÂÂÂ ABI class: X.Org Server Extension, version 10.0
[ÂÂÂ 13.465] (II) LoadModule: "fbturbo"
[ÂÂÂ 13.466] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ÂÂÂ 13.470] (II) Module fbturbo: vendor="X.Org Foundation"
[ÂÂÂ 13.470] ÂÂÂ compiled for 1.20.3, module version = 0.5.1
[ÂÂÂ 13.470] ÂÂÂ Module class: X.Org Video Driver
[ÂÂÂ 13.470] ÂÂÂ ABI class: X.Org Video Driver, version 24.0
[ÂÂÂ 13.470] (II) FBTURBO: driver for framebuffer: fbturbo
[ÂÂÂ 13.517] (WW) Falling back to old probe method for fbturbo
[ÂÂÂ 13.518] (II) Loading sub module "fbdevhw"
[ÂÂÂ 13.518] (II) LoadModule: "fbdevhw"
[ÂÂÂ 13.518] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ÂÂÂ 13.523] (II) Module fbdevhw: vendor="X.Org Foundation"
[ÂÂÂ 13.523] ÂÂÂ compiled for 1.20.4, module version = 0.0.2
[ÂÂÂ 13.523] ÂÂÂ ABI class: X.Org Video Driver, version 24.0
[ÂÂÂ 13.524] (II) FBTURBO(0): using /dev/fb0
[ÂÂÂ 13.524] (II) FBTURBO(0): Creating default Display subsection in
Screen section
ÂÂÂ "Default Screen Section" for depth/fbbpp 24/32
[ÂÂÂ 13.524] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[ÂÂÂ 13.524] (==) FBTURBO(0): RGB weight 888
[ÂÂÂ 13.524] (==) FBTURBO(0): Default visual is TrueColor
[ÂÂÂ 13.524] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ÂÂÂ 13.524] (II) FBTURBO(0): hardware: simple (video memory: 9000kB)
With the patch applied vc4 wins, but mode setting seems to fail:
[ÂÂÂ 13.596] (II) systemd-logind: logind integration requires -keeptty
and -keeptty was not provided, disabling logind integration
[ÂÂÂ 13.599] (II) xfree86: Adding drm device (/dev/dri/card0)
[ÂÂÂ 13.606] (II) no primary bus or device found
[ÂÂÂ 13.607] ÂÂÂ falling back to /sys/devices/platform/soc/soc:gpu/drm/card0
[ÂÂÂ 13.607] (II) LoadModule: "glx"
[ÂÂÂ 13.613] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ÂÂÂ 13.674] (II) Module glx: vendor="X.Org Foundation"
[ÂÂÂ 13.674] ÂÂÂ compiled for 1.20.4, module version = 1.0.0
[ÂÂÂ 13.674] ÂÂÂ ABI class: X.Org Server Extension, version 10.0
[ÂÂÂ 13.674] (II) LoadModule: "fbturbo"
[ÂÂÂ 13.675] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ÂÂÂ 13.679] (II) Module fbturbo: vendor="X.Org Foundation"
[ÂÂÂ 13.679] ÂÂÂ compiled for 1.20.3, module version = 0.5.1
[ÂÂÂ 13.679] ÂÂÂ Module class: X.Org Video Driver
[ÂÂÂ 13.679] ÂÂÂ ABI class: X.Org Video Driver, version 24.0
[ÂÂÂ 13.679] (II) FBTURBO: driver for framebuffer: fbturbo
[ÂÂÂ 13.689] (WW) Falling back to old probe method for fbturbo
[ÂÂÂ 13.689] (II) Loading sub module "fbdevhw"
[ÂÂÂ 13.689] (II) LoadModule: "fbdevhw"
[ÂÂÂ 13.690] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ÂÂÂ 13.692] (II) Module fbdevhw: vendor="X.Org Foundation"
[ÂÂÂ 13.692] ÂÂÂ compiled for 1.20.4, module version = 0.0.2
[ÂÂÂ 13.693] ÂÂÂ ABI class: X.Org Video Driver, version 24.0
[ÂÂÂ 13.693] (II) FBTURBO(0): using /dev/fb0
[ÂÂÂ 13.693] (II) FBTURBO(0): Creating default Display subsection in
Screen section
ÂÂÂ "Default Screen Section" for depth/fbbpp 16/16
[ÂÂÂ 13.693] (==) FBTURBO(0): Depth 16, (==) framebuffer bpp 16
[ÂÂÂ 13.693] (==) FBTURBO(0): RGB weight 565
[ÂÂÂ 13.693] (==) FBTURBO(0): Default visual is TrueColor
[ÂÂÂ 13.693] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ÂÂÂ 13.693] (II) FBTURBO(0): hardware: vc4drmfb (video memory: 675kB)
could you please confirm which driver is actually working on X with this
patch applied in your case?
Regards
Stefan
>
> Regards,
> Nicolas
>