From: sashiko-bot@kernel.org
To: "Paul Menzel" <pmenzel@molgen.mpg.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: Do not report surplus partner altmodes as firmware bug
Date: Wed, 04 Nov 2026 00:02:59 +0000 [thread overview]
Message-ID: <sashiko-outbox-196270@kernel.org> (raw)
In-Reply-To: <20261103234750.27510-1-pmenzel@molgen.mpg.de>
> On a Dell XPS 13 9370 (BIOS 1.21.0) with a Dell USB Type-C power adapter
> connected, Linux 7.2.12 logs:
>
> ucsi_acpi USBC000:00: con2: Firmware bug: duplicate partner altmode SVID 0x413c at offset 1, ignoring but please contact the BIOS vendor to fix this issue.
> ucsi_acpi USBC000:00: con2: VDO mismatch: 0x00000001 vs 0x00000002
>
> The port advertises one altmode for the Dell SVID, and the partner two
> Modes, with VDOs 0x00000001 and 0x00000002. Only the first one is
> registered:
>
> /sys/class/typec/port1/port1.2/svid:413c
> /sys/class/typec/port1/port1.2/vdo:0x00000001
> /sys/class/typec/port1-partner/port1-partner.0/svid:413c
> /sys/class/typec/port1-partner/port1-partner.0/vdo:0x00000001
>
> [ ... ]
> all partner altmodes with a per-SVID count, so with altmodes of other
> SVIDs registered first, it printed the VDO of an unrelated altmode.
>
> Fixes: 67c92c6419ea ("usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware")
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103234750.27510-1-pmenzel@molgen.mpg.de?part=1
prev parent reply other threads:[~2026-11-04 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 23:47 [PATCH] usb: typec: ucsi: Do not report surplus partner altmodes as firmware bug Paul Menzel
2026-11-04 0:02 ` 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-196270@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--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