From: Kenneth Crudup <kenny@panix.com>
To: Jameson Thies <jthies@google.com>,
heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: dmitry.baryshkov@oss.qualcomm.com, bleung@chromium.org,
gregkh@linuxfoundation.org, akuchynski@chromium.org,
abhishekpandit@chromium.org, sebastian.reichel@collabora.com,
linux-pm@vger.kernel.org, Kenneth C <kenny@panix.com>
Subject: Re: [PATCH 0/6] UCSI Power Supply Updates and Bug Fixes
Date: Mon, 13 Oct 2025 14:02:26 -0700 [thread overview]
Message-ID: <92c821fb-537a-40e6-98fc-616941b57778@panix.com> (raw)
In-Reply-To: <20251007000007.3724229-1-jthies@google.com>
On 10/6/25 17:00, Jameson Thies wrote:
> This series includes the following minor changes to power supply
> handling by the UCSI driver.
...
> base-commit: e40b984b6c4ce3f80814f39f86f87b2a48f2e662
I wanted to let you know that on my Dell XPS-9320, this patchset ended
up spamming (i.e., hundreds) my dmesg with the following:
power_supply ucsi-source-psy-USBC000:002: driver reporting unavailable
enum value 7
... which I believe to be POWER_SUPPLY_USB_TYPE_PD_DRP .
In my case it was coming from the call to
power_supply_show_enum_with_available() on/around line 380 in
.../drivers/power/supply/power_supply_sysfs.c ; I'd tried adding
POWER_SUPPLY_USB_TYPE_PD_DRP to con->psy_desc.usb_types in
ucsi_register_port_psy() in
.../drivers/usb/typec/ucsi/psy.c thinking that may fix it with no success.
LMK if you need any further info,
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
next prev parent reply other threads:[~2025-10-13 21:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 0:00 [PATCH 0/6] UCSI Power Supply Updates and Bug Fixes Jameson Thies
2025-10-07 0:00 ` [PATCH 1/6] usb: typec: ucsi: psy: Add power supply status Jameson Thies
2025-10-08 12:53 ` Heikki Krogerus
2025-10-07 0:00 ` [PATCH 2/6] usb: typec: ucsi: psy: Add support for DRP USB type Jameson Thies
2025-10-07 23:50 ` Benson Leung
2025-10-08 13:02 ` Heikki Krogerus
2025-10-13 20:44 ` Jameson Thies
2025-10-07 0:00 ` [PATCH 3/6] usb: typec: ucsi: Report power supply changes on power opmode changes Jameson Thies
2025-10-07 23:51 ` Benson Leung
2025-10-08 13:02 ` Heikki Krogerus
2025-10-07 0:00 ` [PATCH 4/6] usb: typec: ucsi: Report power supply change on sink path change Jameson Thies
2025-10-07 23:52 ` Benson Leung
2025-10-08 13:06 ` Heikki Krogerus
2025-10-13 20:45 ` Jameson Thies
2025-10-07 0:00 ` [PATCH 5/6] usb: typec: ucsi: psy: Set max current to zero when disconnected Jameson Thies
2025-10-07 23:55 ` Benson Leung
2025-10-08 13:08 ` Heikki Krogerus
2025-10-07 0:00 ` [PATCH 6/6] usb: typec: ucsi: pr_swap should check connector_status Jameson Thies
2025-10-07 23:56 ` Benson Leung
2025-10-08 13:10 ` Heikki Krogerus
2025-10-13 20:56 ` Jameson Thies
2025-10-13 7:33 ` [PATCH 0/6] UCSI Power Supply Updates and Bug Fixes Greg KH
2025-10-13 20:59 ` Jameson Thies
2025-10-14 5:19 ` Greg KH
2025-10-13 21:02 ` Kenneth Crudup [this message]
2025-10-13 22:53 ` Jameson Thies
2025-10-13 23:26 ` Kenneth Crudup
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=92c821fb-537a-40e6-98fc-616941b57778@panix.com \
--to=kenny@panix.com \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
/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;
as well as URLs for NNTP newsgroup(s).