From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Clark <robdclark@gmail.com>
Cc: Caleb Connolly <caleb@connolly.tech>,
saravanak@google.com, John Stultz <john.stultz@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: fw_devlink breakage on SDM845 / a630 with DSI displays
Date: Thu, 20 May 2021 01:00:44 +0300 [thread overview]
Message-ID: <CAA8EJpqyuzEFqcd6YY=GEnjzNBpEndB1GD6A9h7rGK6_yuSbcg@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGvnL9mOp3vKuSvz=KDijtFVMdKCF4BXSLxXeoR38O-SUg@mail.gmail.com>
Hi,
On Wed, 19 May 2021 at 18:36, Rob Clark <robdclark@gmail.com> wrote:
>
> + 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
> fw_devlink
I've had multiple issues with the 5.13-rc1 because of devlinks.
Reverting f7514a6630166a7b566dee9b1af2e87e431959be (of: property:
fw_devlink: Add support for remote-endpoint) made things work for me.
>
> BR,
> -R
>
> On Wed, May 19, 2021 at 8:26 AM Caleb Connolly <caleb@connolly.tech> 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:
> > https://paste.ubuntu.com/p/8kPx4nFGF5/ (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
> >
--
With best wishes
Dmitry
prev parent reply other threads:[~2021-05-19 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aff4807e-e554-2e32-5789-dfaf65128a8e@connolly.tech>
2021-05-19 15:40 ` fw_devlink breakage on SDM845 / a630 with DSI displays Rob Clark
2021-05-19 21:52 ` 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 [this message]
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='CAA8EJpqyuzEFqcd6YY=GEnjzNBpEndB1GD6A9h7rGK6_yuSbcg@mail.gmail.com' \
--to=dmitry.baryshkov@linaro.org \
--cc=amit.pundir@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=caleb@connolly.tech \
--cc=dianders@chromium.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=saravanak@google.com \
--cc=swboyd@chromium.org \
/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).