All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222021] Not charging via USB C after Kernel update "underpowered" Dell XPS + workaround
Date: Fri, 18 Sep 2026 16:18:42 +0000	[thread overview]
Message-ID: <bug-222021-208809-VFMe2YHq0a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222021-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222021

Lovekesh Solanki (lovekeshsolanki00@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lovekeshsolanki00@gmail.com

--- Comment #2 from Lovekesh Solanki (lovekeshsolanki00@gmail.com) ---
I wonder if this could be a firmware side issue, but you said this started
after a kernel update so I guess git bisection is useful.

When you do test mainline and bisect, could you also test this attached patch?
I suppose when UCSI_GET_PDOS fails  we could reset PPM and retry the read once.
Also, did you perform a firmware or bios update around same time?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-09-18 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 17:52 [Bug 222021] New: Not charging via USB C after Kernel update "underpowered" Dell XPS + workaround bugzilla-daemon
2026-09-18  6:17 ` [Bug 222021] " bugzilla-daemon
2026-09-18 16:18 ` bugzilla-daemon [this message]
2026-09-18 16:20 ` bugzilla-daemon
2026-09-19  8:00 ` bugzilla-daemon

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=bug-222021-208809-VFMe2YHq0a@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.