All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Robinson <pbrobinson@gmail.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: stefan.wahren@i2se.com, Peter Mattern <pmattern@arcor.de>,
	dri-devel@lists.freedesktop.org
Subject: Re: drm/vc4: module dysfunctional on Raspberry Pi 3B as of 5.18.0
Date: Wed, 8 Jun 2022 16:14:22 +0100	[thread overview]
Message-ID: <CALeDE9OyJtvRGnN80JNW3AwwgAa_h_bs8GTLJzo06WK-o+_7Ng@mail.gmail.com> (raw)
In-Reply-To: <20220608143605.x4arwudst3nqeg7b@houat>

Hi Maxime,

> > > As of Linux 5.18.0, module vc4 apparently isn't working on Raspberry Pi
> > > 3B any more.
> > >
> > > If a monitor is attached to the device, the boot messages show up as
> > > usual, but right when KMS starts, the screen turns black. Similarly, the
> > > screen also turns black when the module is blacklisted at boot time and
> > > loaded from the running system.
> > > The problem looks quite similar to the one posted some months ago in [1].
>
> If I understand you properly, it results in a blank screen if the
> monitor is connected, but the system is still responsive?

Yes, it boots fine, I see all serial console output and the module
loads etc, without a screen I didn't notice the issue

> If so, it's a very different problem than the link you provided, since
> it was occurring when no monitor was connected and resulted in a total
> system hang.
>
> > > Unfortunately, looking through systemd's journal didn't seem to yield
> > > any real hint. Nevertheless, the results from grepping vc4 are
> >
> > I'm seeing the same issue with vc4 on a RPi3 on 5.18.1 on Fedora so
> > can confirm the regression. Maxime would know what might be up here?
>
> I tested on 5.18 on my 3B and it works well. Could you paste your kernel
> configuration and config.txt somewhere?

It boots with output on 5.17.13, and not on 5.18. The config is at the
following link (Fedora config). The config.txt is below.
https://pbrobinson.fedorapeople.org/config-5.18.2-201.fc36.armv7hl

===
# Raspberry Pi 2
[pi2]
kernel=rpi2-u-boot.bin
dtoverlay=upstream

# Raspberry Pi 3
[pi3]
kernel=rpi3-u-boot.bin
dtoverlay=upstream

# Raspberry Pi 4
[pi4]
kernel=rpi4-u-boot.bin
dtoverlay=upstream-pi4

# Default Fedora configs for all Raspberry Pi Revisions
[all]
# Enable UART
# Only enable UART if you're going to use it as it has speed implications
# Serial console is ttyS0 on RPi3 and ttyAMA0 on all other variants
# u-boot will auto detect serial and pass corrent options to kernel if enabled
# Speed details: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=141195

# Terrible hack to work around U-Boot issues on most devices
enable_uart=1

# Early boot delay in the hope monitors are initialised enough to provide EDID
bootcode_delay=1

# We need this to be 32Mb to support VCHI services and drivers which use them
# but this isn't used by mainline VC4 driver so reduce to lowest supported value
# You need to set this to at least 80 for using the camera
gpu_mem=32

# Use eXtended firmware by default
start_x=1

# Stop the RPi turning on HDMI monitors on reboot
hdmi_ignore_cec_init=1

# New option to allow the firmware to load upstream dtb
# Will allow things like camera, touchscreen etc to work OOTB
upstream_kernel=1
===

  reply	other threads:[~2022-06-08 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 18:01 drm/vc4: module dysfunctional on Raspberry Pi 3B as of 5.18.0 Peter Mattern
2022-06-08 13:10 ` Peter Robinson
2022-06-08 14:36   ` Maxime Ripard
2022-06-08 15:14     ` Peter Robinson [this message]
2022-06-08 15:36       ` Maxime Ripard
2022-06-09  9:23         ` Maxime Ripard
2022-06-09 11:49           ` Peter Robinson
2022-06-09 13:37           ` Peter Mattern
2022-06-08 22:47     ` Stefan Wahren
2022-06-09 11:52       ` Peter Robinson
2022-06-09 21:33         ` Stefan Wahren
2022-06-10 20:06           ` Stefan Wahren
2022-06-10 22:02           ` Peter Robinson
2022-06-09 13:08     ` Peter Mattern
2022-06-05 23:57 Stefan Wahren
2022-06-09 12:49 Peter Mattern

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=CALeDE9OyJtvRGnN80JNW3AwwgAa_h_bs8GTLJzo06WK-o+_7Ng@mail.gmail.com \
    --to=pbrobinson@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maxime@cerno.tech \
    --cc=pmattern@arcor.de \
    --cc=stefan.wahren@i2se.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.