From: Stefan Wahren <stefan.wahren@i2se.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>
Cc: devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D
Date: Fri, 13 Mar 2020 14:59:14 +0100 [thread overview]
Message-ID: <bb2c7d99-06b1-d222-7f69-8ce91157bde5@i2se.com> (raw)
In-Reply-To: <9e685fce547d808f269e59e2290331e75c66f3e4.camel@suse.de>
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
>
next prev parent reply other threads:[~2020-03-13 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 17:32 [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D Nicolas Saenz Julienne
2020-03-03 18:17 ` Stefan Wahren
2020-03-03 18:37 ` Nicolas Saenz Julienne
2020-03-03 19:24 ` Stefan Wahren
2020-03-05 10:44 ` Nicolas Saenz Julienne
2020-03-06 20:33 ` Stefan Wahren
2020-03-09 15:41 ` Stefan Wahren
2020-03-09 19:22 ` Nicolas Saenz Julienne
2020-03-13 13:59 ` Stefan Wahren [this message]
2020-03-26 12:24 ` Nicolas Saenz Julienne
2020-03-26 17:24 ` Stefan Wahren
2020-03-27 0:35 ` Florian Fainelli
2020-03-27 10:41 ` Nicolas Saenz Julienne
2020-03-27 11:24 ` Stefan Wahren
2020-03-27 12:58 ` Nicolas Saenz Julienne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb2c7d99-06b1-d222-7f69-8ce91157bde5@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nsaenzjulienne@suse.de \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).