All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Samuel Čavoj" <samuel@cavoj.net>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: introduce read_explicit operation
Date: Tue, 4 Apr 2023 16:02:18 +0300	[thread overview]
Message-ID: <ZCwf2rvsoFjH5D91@kuha.fi.intel.com> (raw)
In-Reply-To: <3525bf85c78a5805c4b4bff42dd49c39@cavoj.net>

Hi Sam,

On Sat, Apr 01, 2023 at 08:06:57PM +0200, Samuel Čavoj wrote:
> > 
> > Okay... Did you see those errors with your original patch?
> 
> I'm pretty sure that it's the same, yeah. The specific error is
> one (or a seemingly random sequence) of the following:
> 
> - con2: failed to register partner alt modes (-22)
> - con2: failed to register partner alt modes (-5)
> - GET_CURRENT_CAM command failed (also caused by a -22 from exec_command)
> 
> Doesn't occur with nothing or only a charger plugged in. Once I plug
> a USB-C to DP adapter or a cheap USB-C hub (with an internal DP->HDMI
> converter, USB3 hub and GbE in one of the hub ports), the errors
> randomly show up when reloading the module or when plugging in once
> already loaded. Not consistent at all.
> 
> So seems to be alt-mode related. Will probably need some more
> investigation on my part, unless you've got any ideas off the
> bat.

The alt mode stuff is very annoying with UCSI. I think Windows is only
interested in the connector alt modes. With the partner alt modes the
responses differ on almost every system, and several platforms
actually never return anything when you request the partner alt modes
with GET_ALTERNATE_MODES.

But I think we can move forward with this fix. I'll send it tomorrow.

Br,

-- 
heikki

      reply	other threads:[~2023-04-04 13:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 23:39 [PATCH] usb: typec: ucsi: introduce read_explicit operation Samuel Čavoj
2023-01-21  7:17 ` Greg KH
2023-01-24 11:21   ` Heikki Krogerus
2023-03-08 16:17     ` Heikki Krogerus
2023-03-16 13:08       ` Heikki Krogerus
2023-03-18  2:04         ` Samuel Čavoj
2023-03-29 23:48           ` Samuel Čavoj
2023-03-30 14:06             ` Heikki Krogerus
2023-04-01 18:06               ` Samuel Čavoj
2023-04-04 13:02                 ` Heikki Krogerus [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=ZCwf2rvsoFjH5D91@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=samuel@cavoj.net \
    /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.