mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vladyslav Tymoshchuk <tvlad744@gmail.com>
To: Joonhoe Kim <26rote@gmail.com>, Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Johan Hovold <johan@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Casey Connolly <casey.connolly@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vladyslav Tymoshchuk <tvlad744@gmail.com>
Subject: Re: [PATCH RFC] usb: typec: ucsi: Schedule connector worker on freezable workqueue
Date: Thu, 22 Oct 2026 20:19:07 +0300	[thread overview]
Message-ID: <20261022171907.2021-1-tvlad744@gmail.com> (raw)
In-Reply-To: <20261020132432.998-1-26rote@gmail.com>

Hi Joonhoe, Abel,

On Tue, 20 Oct 2026 22:24:30 +0900, Joonhoe Kim wrote:
> 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.

I have sent an RFC for that rework:

  https://lore.kernel.org/all/20261022164151.592-1-tvlad744@gmail.com/

pmic_glink holds the notifications back from ->prepare() on, and
passes them on from system_freezable_wq after resume, for all its
clients. For a notification that arrives during system sleep, the
UCSI connector work then runs only after the devices it calls into
have resumed, so this patch would not be needed. A notification can
still wake up the system, if the client's device may wake up the
system.

On SM8750 the series avoids the reset on an unplug during
suspend-to-idle, also with wakeup disabled for both clients, on a
kernel without the dwc3-qcom fix.

Joonhoe, if you can test it on your board, that would show whether it
also covers the FSA4480 case. It is on top of next-20261021; if it
does not apply to your tree, I can send it rebased on v7.3-rc5.

Thanks,
Vladyslav

(I used an AI assistant, Claude, for the analysis and to draft this
mail; the tests ran on my device.)

      reply	other threads:[~2026-10-22 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 11:45 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
2026-10-22 17:19         ` Vladyslav Tymoshchuk [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=20261022171907.2021-1-tvlad744@gmail.com \
    --to=tvlad744@gmail.com \
    --cc=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 \
    /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

all inboxes | Powered by JetHome®