All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Huber <ulrich@huberulrich.de>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: ucsi_acpi GET_CONNECTOR_STATUS failed (-5)
Date: Wed, 25 Aug 2021 15:53:28 +0200	[thread overview]
Message-ID: <0e77017d-9358-a691-6293-234fcbab6a31@huberulrich.de> (raw)
In-Reply-To: <YSX7hZnCoFSXTFJe@kuha.fi.intel.com>

Hi Heikki,
Thanks for the quick answer.
> Thanks for the report. Can you test this with kernel v5.10?

I tested kernel v5.10 and could not reproduce this specific error. 
Instead I received the following warning on a single occasion:

ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes

Right before I received this warning, I plugged in and immediately 
unplugged the charging cable again. So I might have disrupted the driver 
during the retrieval of the new device state.

> I'm wondering if commit 217504a05532 ("usb: typec: ucsi: Work around
> PPM losing change information") causes that GET_CONNECTOR_STATUS
> failure.

Quite interesting, as I thought this as the most likely culprit as well 
when I took a look at the driver.

As I have to build the kernel v5.14-rc7 manually to include another 
bugfix, I'll throw in a few more debug messages to find out which step 
fails and if possible to get some more details on the cause. Could you 
point me to things I should take a look at, to narrow down the issue?

Thanks,

Ulrich


  reply	other threads:[~2021-08-25 13:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 14:29 ucsi_acpi GET_CONNECTOR_STATUS failed (-5) Ulrich Huber
2021-08-25  8:12 ` Heikki Krogerus
2021-08-25 13:53   ` Ulrich Huber [this message]
2021-08-25 18:37     ` Ulrich Huber
2021-08-26 14:25       ` Heikki Krogerus
2021-08-26 19:50         ` Ulrich Huber
2021-08-28  9:48           ` Heikki Krogerus
2021-08-29 11:02             ` Ulrich Huber
2021-09-09 12:19               ` Heikki Krogerus
2021-09-09 12:24                 ` Ulrich Huber
2021-09-13 13:32                   ` Heikki Krogerus

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=0e77017d-9358-a691-6293-234fcbab6a31@huberulrich.de \
    --to=ulrich@huberulrich.de \
    --cc=heikki.krogerus@linux.intel.com \
    --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.