Linux USB
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "David Vornholt" <dv@etik.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: typec: ucsi: Stop a power level change notification storm
Date: Sat, 10 Oct 2026 18:50:48 +0000	[thread overview]
Message-ID: <sashiko-outbox-166841@kernel.org> (raw)
In-Reply-To: <20261010183917.146821-1-dv@etik.com>

> From: David Vornholt <david@vornholt.online>
> 
> On a Lenovo ThinkPad X1 Carbon Gen 13 (BIOS N4BET78W 1.48, EC N4BHT61W
> 1.41, UCSI 1.0) with an HP E273m monitor connected, the PPM keeps
> signaling a Negotiated Power Level Change although the power contract
> stays the same, and signals it again right after it has been
> acknowledged:
> 
>   ucsi_connector_change: port1 status: change=0040, opmode=3,
>     connected=1, sourcing=0, partner_flags=2, partner_type=4,
>     request_data_obj=1304b12c, BC status=2
> 
> This repeats about seven times a second for as long as the monitor stays
> connected. Since commit a0d4618788f2 ("usb: typec: ucsi: Workaround for
> missed op_mode change"), every Negotiated Power Level Change is handled
> [ ... ]
> The ports, the partner and its 5 V/3 A power supply stay registered.
> 
> Fixes: c1b0bc2dabfa ("usb: typec: Add support for UCSI interface")
> Cc: stable@vger.kernel.org
> Signed-off-by: David Vornholt <david@vornholt.online>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261010183917.146821-1-dv@etik.com?part=1


      reply	other threads:[~2026-10-10 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 18:39 [PATCH v2] usb: typec: ucsi: Stop a power level change notification storm David Vornholt
2026-10-10 18:50 ` 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-166841@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dv@etik.com \
    --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