Linux USB
 help / color / mirror / Atom feed
From: Marek Vasut <marex@nabladev.com>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-usb@vger.kernel.org, stable@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	kernel@dh-electronics.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: mux: Fix typec_switch_match()
Date: Tue, 18 Aug 2026 19:43:54 +0200	[thread overview]
Message-ID: <71fca17d-9b6b-4c9d-b595-ebd1dc6605de@nabladev.com> (raw)
In-Reply-To: <1aeaa585-79f2-4f43-87b1-2ae3925b176c@oldschoolsolutions.biz>

On 8/18/26 7:05 PM, Jens Glathe wrote:
> Hi Marek,
> 
> On 8/18/26 18:56, Marek Vasut wrote:
>> Hello Sebastian,
> [...]
>> Could you revert f576c75f95a5 ("Revert "usb: typec: mux: avoid 
>> duplicated mux switches"") and apply the following patch (equivalent 
>> to this patch, applies to mux instead of switch) and see if that fixes 
>> the T14s for you too then ? If yes, than, I think this might be the 
>> proper fix rather than the revert:
>>
>> diff --git a/drivers/usb/typec/mux.c b/drivers/usb/typec/mux.c
>> index 4a4297f15aad3..afa6fc1813978 100644
>> --- a/drivers/usb/typec/mux.c
>> +++ b/drivers/usb/typec/mux.c
>> @@ -294,6 +294,8 @@ static void *typec_mux_match(const struct 
>> fwnode_handle *fwnode,
>>
>>         dev = class_find_device(&typec_mux_class, NULL, fwnode,
>>                                 mux_fwnode_match);
>> +       if (!dev)
>> +               return ERR_PTR(-EPROBE_DEFER);
>>
>>         /* Skip duplicates */
>>         for (i = 0; i < TYPEC_MUX_MAX_DEVS; i++)
>> @@ -303,7 +305,7 @@ static void *typec_mux_match(const struct 
>> fwnode_handle *fwnode,
>>                 }
>>
>>
>> -       return dev ? to_typec_mux_dev(dev) : ERR_PTR(-EPROBE_DEFER);
>> +       return to_typec_mux_dev(dev);
>>  }
>>
>>  /**
> 
> I will test that one with the f576c75f95a5 reverted on the x1p and 
> sc8280xp boxes I have here, let's see. T14s G6 shouldn't be affected 
> either way.
> 
> with best regards
Thank you

  reply	other threads:[~2026-08-18 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 18:22 [PATCH] usb: typec: mux: Fix typec_switch_match() Marek Vasut
2026-08-18  8:32 ` Thorsten Leemhuis
2026-08-18  8:58   ` Marek Vasut
2026-08-18 16:24 ` Sebastian Reichel
2026-08-18 16:56   ` Marek Vasut
2026-08-18 17:05     ` Jens Glathe
2026-08-18 17:43       ` Marek Vasut [this message]
2026-08-18 17:01   ` Jens Glathe

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=71fca17d-9b6b-4c9d-b595-ebd1dc6605de@nabladev.com \
    --to=marex@nabladev.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jens.glathe@oldschoolsolutions.biz \
    --cc=kernel@dh-electronics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox