From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-rockchip@lists.infradead.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 2/2] usb: typec: mux: avoid duplicated mux switches
Date: Mon, 23 Feb 2026 17:02:12 +0200 [thread overview]
Message-ID: <aZxr9DBebcQfsQiP@kuha> (raw)
In-Reply-To: <20260213-typec-mux-duplication-fix-v1-2-70076a7c5691@collabora.com>
Fri, Feb 13, 2026 at 08:23:29PM +0100, Sebastian Reichel wrote:
> Some devices use combo PHYs (i.e. USB3 + DisplayPort), which also
> handle the lane muxing. These PHYs are referenced twice from
> the USB-C connector (USB super-speed lines and SBU/AUX lines)
> resulting in the mux being configured twice. Avoid this by
> dropping duplicates.
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
> drivers/usb/typec/mux.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/typec/mux.c b/drivers/usb/typec/mux.c
> index db35b7398343..6a394326f236 100644
> --- a/drivers/usb/typec/mux.c
> +++ b/drivers/usb/typec/mux.c
> @@ -309,9 +309,9 @@ struct typec_mux *fwnode_typec_mux_get(struct fwnode_handle *fwnode)
> {
> struct typec_mux_dev *mux_devs[TYPEC_MUX_MAX_DEVS];
> struct typec_mux *mux;
> + int i, j, k;
> int count;
> int err;
> - int i;
>
> mux = kzalloc(sizeof(*mux), GFP_KERNEL);
> if (!mux)
> @@ -333,6 +333,18 @@ struct typec_mux *fwnode_typec_mux_get(struct fwnode_handle *fwnode)
> }
> }
>
> + /* eliminate duplicates */
> + for (i = 0; i < count; i++) {
> + for (j = i + 1; j < count; j++) {
> + if (mux_devs[j] == mux_devs[i]) {
> + put_device(&mux_devs[j]->dev);
> + for (k = j; k < count; k++)
> + mux_devs[k] = mux_devs[k+1];
> + count--;
> + }
> + }
> + }
The same should work here. My code snippets probable has to be
modified, but the idea should work. The check should be more simple to
do in typec_switch_match().
Br,
--
heikki
prev parent reply other threads:[~2026-02-23 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 19:23 [PATCH 0/2] usb: typec: mux: avoid duplicated mux switches Sebastian Reichel
2026-02-13 19:23 ` [PATCH 1/2] usb: typec: mux: avoid duplicated orientation switches Sebastian Reichel
2026-02-23 14:54 ` Heikki Krogerus
2026-02-13 19:23 ` [PATCH 2/2] usb: typec: mux: avoid duplicated mux switches Sebastian Reichel
2026-02-23 15: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=aZxr9DBebcQfsQiP@kuha \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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