From: Johan Hovold <johan@kernel.org>
To: Clayton Craft <clayton@craftyguy.net>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: pmic_glink_altmode: fix spurious DP hotplug events
Date: Wed, 26 Mar 2025 15:43:15 +0100 [thread overview]
Message-ID: <Z-QSg7LH8u7uAfLg@hovoldconsulting.com> (raw)
In-Reply-To: <Z-JqCUu13US1E5wY@hovoldconsulting.com>
On Tue, Mar 25, 2025 at 09:32:10AM +0100, Johan Hovold wrote:
> On Mon, Mar 24, 2025 at 10:05:44AM -0700, Clayton Craft wrote:
> > On 3/24/25 06:24, Johan Hovold wrote:
> > > The PMIC GLINK driver is currently generating DisplayPort hotplug
> > > notifications whenever something is connected to (or disconnected from)
> > > a port regardless of the type of notification sent by the firmware.
> > >
> > > These notifications are forwarded to user space by the DRM subsystem as
> > > connector "change" uevents:
>
> > > ---
> > >
> > > Clayton reported seeing display flickering with recent RC kernels, which
> > > may possibly be related to these spurious events being generated with
> > > even greater frequency.
> > >
> > > That still remains to be fully understood, but the spurious events, that
> > > on the X13s are generated every 90 seconds, should be fixed either way.
> >
> > When a display/dock (which has ethernet) is connected, I see this
> > hotplug change event 2 times (every 30 seconds) which I think you said
> > this is expected now?
>
> I didn't realise you were also using a display/dock. Bjorn mentioned
> that he has noticed issues with one of his monitors (e.g. built-in hub
> reenumerating repeatedly iirc) which may be related.
>
> I see these pairs of identical notification when connecting the stock
> charger to one of the ports directly, and I noticed that they repeat
> every 90 seconds here. After plugging and unplugging a bunch of devices
> I think they stopped at one point, but they were there again after a
> reboot.
>
> So there's something going on with the PMIC GLINK firmware or driver on
> the X13s. I did not see these repeated messages on the T14s with just a
> charger (and I don't have a dock to test with).
With this patch enabling UCSI on sc8280xp:
https://lore.kernel.org/lkml/20250326124944.6338-1-johan+linaro@kernel.org/
most of the periodic orientation notifications for the port with the
charger connected appears to be gone on the X13s (note that the T14s
already has UCSI enabled).
I get one to three notification 90 seconds after boot with the charger
connected (and two notifications when reconnecting it) but that appears
to be it.
Perhaps you can give that one a try with your docks and monitors as
well, Clayton and Bjorn.
> > Not sure about you seeing it every 90s vs my 30s... anyways, I no longer
> > see these events when a PD charger is connected though, so this patch
> > seems to help with that!
>
> Just so I understand you correctly here, you're no longer seeing the
> repeated uevents with this patch? Both when using a dock and when using
> a charger directly?
>
> Did it help with the display flickering too? Was that only on the
> external display?
Johan
next prev parent reply other threads:[~2025-03-26 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 13:24 [PATCH] soc: qcom: pmic_glink_altmode: fix spurious DP hotplug events Johan Hovold
2025-03-24 17:05 ` Clayton Craft
2025-03-25 8:32 ` Johan Hovold
2025-03-26 14:43 ` Johan Hovold [this message]
2025-04-01 18:18 ` Clayton Craft
2025-04-02 7:13 ` Johan Hovold
2025-03-24 19:21 ` Konrad Dybcio
2025-03-25 8:40 ` Johan Hovold
2025-03-25 11:29 ` Konrad Dybcio
2025-05-09 22:13 ` Bjorn Andersson
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=Z-QSg7LH8u7uAfLg@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=clayton@craftyguy.net \
--cc=johan+linaro@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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