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, 2 Apr 2025 09:13:00 +0200 [thread overview]
Message-ID: <Z-zjfLyRjPplXLHV@hovoldconsulting.com> (raw)
In-Reply-To: <7e287401-98c4-413f-8108-134d5e43d279@craftyguy.net>
On Tue, Apr 01, 2025 at 11:18:49AM -0700, Clayton Craft wrote:
> On 3/26/25 07:43, Johan Hovold wrote:
> > On Tue, Mar 25, 2025 at 09:32:10AM +0100, Johan Hovold wrote:
> >> 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.
>
> Sorry for the confusion, let me clarify:
>
> The original issue I reported to you on IRC was *without* a
> dock/external display attached, only a PD adapter was attached. With
> your patch, I no longer see these drm hotplug events in this scenario.
>
> After confirming that your patch resolved the spurious hotplug events
> when using a PD charger, I connected a dock+external display to see if
> the patch caused any regressions there for me. It was here that I
> noticed a periodic hotplug event firing 2 times every 30 seconds was
> still showing up. I don't know if this is expected or not, I've never
> noticed it before because I wasn't monitoring udev events.
Got it, thanks for clarifying.
Did you get a chance to try the patch enabling UCSI and USB-PD? That one
may possibly help with the dock issue:
https://lore.kernel.org/lkml/20250326124944.6338-1-johan+linaro@kernel.org/
> >> Did it help with the display flickering too? Was that only on the
> >> external display?
>
> The flickering was only on the internal display, and your patch here
> seems to have resolved that.
Good. Is there any flickering on either screen when you see the spurious
HP events with the dock?
Johan
next prev parent reply other threads:[~2025-04-02 7:12 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
2025-04-01 18:18 ` Clayton Craft
2025-04-02 7:13 ` Johan Hovold [this message]
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-zjfLyRjPplXLHV@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