Linux USB
 help / color / mirror / Atom feed
From: joonhoekim <26rote@gmail.com>
To: Vladyslav Tymoshchuk <tvlad744@gmail.com>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Joonhoe Kim <26rote@gmail.com>,
	heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org,
	andersson@kernel.org, konradybcio@kernel.org, lumag@kernel.org,
	johan@kernel.org, neil.armstrong@linaro.org,
	casey.connolly@linaro.org, linux-arm-msm@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] usb: typec: ucsi: Schedule connector worker on freezable workqueue
Date: Tue, 20 Oct 2026 22:24:30 +0900	[thread overview]
Message-ID: <20261020132432.998-1-26rote@gmail.com> (raw)
In-Reply-To: <20261018150136.5896-1-tvlad744@gmail.com>

From: Joonhoe Kim <26rote@gmail.com>

On Sun, 18 Oct 2026 18:01:36 +0300, Vladyslav Tymoshchuk wrote:
> With the connector work on system_freezable_wq, both unplug runs
> resumed (2 of 2).

Thanks, Vladyslav. So the same connector work runs before the devices
it calls into have resumed, and breaks three different consumers: the
FSA4480 switch here, the PS8830 retimer in Abel's original report, and
the dwc3-qcom role notifier on your board.

Abel, the RFC has not moved since February 2025 and two more boards
now need it. Do you still plan to respin it? On Dmitry's question,
7d0767c5cd87 took the same approach for the altmode worker as a
stop-gap until the PMIC GLINK rework, which may help here too.

For the RFC as posted:

Tested-by: Joonhoe Kim <26rote@gmail.com> # Lenovo Legion Tab Y700 Gen 5 (SM8850)

Thanks,
Joonhoe Kim

      reply	other threads:[~2026-10-20 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 11:45 [PATCH RFC] usb: typec: ucsi: Schedule connector worker on freezable workqueue Abel Vesa
2025-02-05 17:31 ` Dmitry Baryshkov
2026-10-16 12:50 ` Joonhoe Kim
2026-10-18 15:01   ` Vladyslav Tymoshchuk
2026-10-20 13:24     ` joonhoekim [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=20261020132432.998-1-26rote@gmail.com \
    --to=26rote@gmail.com \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=casey.connolly@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=johan@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=tvlad744@gmail.com \
    /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