From: Saravana Kannan <firstname.lastname@example.org> To: Rob Clark <email@example.com> Cc: Caleb Connolly <firstname.lastname@example.org>, John Stultz <email@example.com>, Amit Pundir <firstname.lastname@example.org>, Bjorn Andersson <email@example.com>, Douglas Anderson <firstname.lastname@example.org>, Stephen Boyd <email@example.com>, linux-arm-msm <firstname.lastname@example.org> Subject: Re: fw_devlink breakage on SDM845 / a630 with DSI displays Date: Wed, 19 May 2021 14:52:53 -0700 [thread overview] Message-ID: <CAGETcx-2TySe=w1qAbtj2AJu6fNo_gaYnyP6GN150ShT1TvDfA@mail.gmail.com> (raw) In-Reply-To: <CAF6AEGvnL9mOp3vKuSvz=KDijtFVMdKCF4BXSLxXeoR38O-SUg@mail.gmail.com> On Wed, May 19, 2021 at 8:36 AM Rob Clark <email@example.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 > > BR, > -R > > On Wed, May 19, 2021 at 8:26 AM Caleb Connolly <firstname.lastname@example.org> 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. > > Hi Caleb, Is this a device that's supported upstream? If so, can you please point me to the DTS file that corresponds to this board? Also, can you please change all the dev_dbg to dev_info in these functions and give me the full boot log? device_link_add() device_links_check_suppliers() Can you also tell what device are not probing with fw_devlink=on that might be probing with fw_devlink=permissive? You should be able to compare /<debugfs>/devices_deferred to figure that out. Thanks, Saravana
next prev parent reply other threads:[~2021-05-19 21:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> 2021-05-19 15:40 ` Rob Clark 2021-05-19 21:52 ` Saravana Kannan [this message] 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: 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='CAGETcx-2TySe=w1qAbtj2AJu6fNo_gaYnyP6GN150ShT1TvDfA@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: fw_devlink breakage on SDM845 / a630 with DSI displays' \ /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
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).