From: sashiko-bot@kernel.org
To: "Jacob Riff" <jacob@riff.dk>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: retry init only while the PPM is not ready
Date: Sat, 31 Oct 2026 03:36:45 +0000 [thread overview]
Message-ID: <sashiko-outbox-191723@kernel.org> (raw)
In-Reply-To: <20261031032400.38349-1-jacob@riff.dk>
> Commit 254261381538 ("usb: typec: ucsi: retry init when the PPM
> answers early commands incorrectly") makes ucsi_init_work() retry
> ucsi_init() on -ENODEV and -EINVAL, a hundred times over ten seconds,
> to cover a PPM that is not ready to answer commands correctly for a
> short window during boot.
>
> It catches more than that. ucsi_register_port() also fails with
> -ENODEV when no USB role switch is available, and logs that at error
> level, so every retry runs it again and logs it again. Where a machine
> without a usable role switch used to log
>
> ucsi_acpi USBC000:00: error -ENODEV: con1: failed to get usb role switch
> ucsi_acpi USBC000:00: error -ENODEV: PPM init failed
>
> it now logs a hundred and one copies of the first line, followed by
> [ ... ]
>
> Fixes: 254261381538 ("usb: typec: ucsi: retry init when the PPM answers early commands incorrectly")
> Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
> Closes: https://lore.kernel.org/r/CAHk-=wjGk9rBTphk1OAwcqGAE1__KJgMr3B-8X4hKFPX8Wm=BQ@mail.gmail.com
> Signed-off-by: Jacob Riff <jacob@riff.dk>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261031032400.38349-1-jacob@riff.dk?part=1
prev parent reply other threads:[~2026-10-31 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 13:50 [GIT PULL] USB/Thunderbolt driver updates for 7.4-rc1 Greg KH
2026-10-25 1:50 ` pr-tracker-bot
2026-10-31 1:28 ` Linus Torvalds
2026-10-31 3:23 ` Jacob Riff
2026-10-31 3:24 ` [PATCH] usb: typec: ucsi: retry init only while the PPM is not ready Jacob Riff
2026-10-31 3:36 ` sashiko-bot [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=sashiko-outbox-191723@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jacob@riff.dk \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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