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: Sat, 22 Aug 2026 09:27:28 +0200 [thread overview]
Message-ID: <cb989d6a-19e6-47f9-b656-9790c19ad875@nabladev.com> (raw)
In-Reply-To: <8bdf6062-8ec2-4c30-8463-0368d3a0f1ce@oldschoolsolutions.biz>
On 8/21/26 9:20 PM, Jens Glathe wrote:
Hello Jens,
>>> 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
>
> I did the test: switch patch, revert f576c75f95a5, mux patch. Afterwards
> let it run on the zoo here... ps883x devices are unaffected and work
> well, and your proposed mux patch appears to fix the problem with the
> gpio-sbu-mux, too. So it would be a good idea to do this instead of
> f576c75f95a5.
>
> Tested on:
>
> Lenovo IdeaCeentre mini 01q8x10 (ps8833)
>
> Lenovo Thinkpad T14s G6 21N1 (ps8830)
>
> Lenovo Ideapad Slim5 14q8x9 (gpio mux)
>
> Lenovo Ideapad 5 2in1 14q8x9 (gpio mux)
>
> Microsoft Windows Dev Kit 2023 (sc8280xp, gpio mux)
>
> Tested-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Thank you for testing , I have submitted:
https://lore.kernel.org/linux-usb/20260822072556.490594-1-marex@nabladev.com/
next prev parent reply other threads:[~2026-08-22 7:27 UTC|newest]
Thread overview: 11+ 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
2026-08-21 19:20 ` Jens Glathe
2026-08-22 7:27 ` Marek Vasut [this message]
2026-08-18 17:01 ` Jens Glathe
2026-08-24 11:44 ` 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=cb989d6a-19e6-47f9-b656-9790c19ad875@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