archive mirror
 help / color / mirror / Atom feed
From: Rob Clark <>
To: Caleb Connolly <>
Cc:, John Stultz <>,
	Amit Pundir <>,
	Bjorn Andersson <>,
	Douglas Anderson <>,
	Stephen Boyd <>,
	linux-arm-msm <>
Subject: Re: fw_devlink breakage on SDM845 / a630 with DSI displays
Date: Wed, 19 May 2021 08:40:02 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

+ some more folks and msm list..

I suppose I didn't hit this because CONFIG_FBDEV_EMULATION is not
normally enabled for CrOS.. but I'm not really to familiar with


On Wed, May 19, 2021 at 8:26 AM Caleb Connolly <> wrote:
> Hi,
> Since -rc1 I've been hit by some DRM breakage in freedreno which happens
> when fw_devlink=on. It seems to cause some clocks (rcg) to get stuck and
> break DSI displays, here's a full log from the OnePlus 6:
> (that is with
> "deferred_probe_timeout") The PocoPhone F1 also seems to be affected by
> this.
> The display will still come up after pressing the power button a few
> times, although it will be incredibly slow.
> It's worth noting that the issue only happens with
> CONFIG_FBDEV_EMULATION is enabled, I've previously required this to see
> kernel logs during boot and general boot splash with postmarketOS.
> Without it the display will be stuck on the bootloader splash until I
> press the power button and cause it to update once UI (like Phosh) has
> started (though this has been the case for quite some time).
> I'd appreciate any help with debugging / resolving this issue, I'm
> afraid I haven't been able to determine much from some brief digging.
> --
> Kind Regards,
> Caleb

       reply	other threads:[~2021-05-19 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-05-19 15:40 ` Rob Clark [this message]
2021-05-19 21:52   ` fw_devlink breakage on SDM845 / a630 with DSI displays Saravana Kannan
2021-05-19 22:42     ` Caleb Connolly
2021-05-20  0:06       ` Saravana Kannan
2021-05-20  0:17         ` Caleb Connolly
2021-06-11 22:52         ` Caleb Connolly
2021-06-16 19:49           ` Saravana Kannan
2021-05-19 22:00   ` Dmitry Baryshkov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \

* 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).