Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2EE462550C2; Mon, 9 Jun 2025 13:45:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1749476711; cv=none; b=aZqx7an08dyWpn0QYfoa/nZNzcQnoxT7bjMmG5O+WhoymE2IW11YnOBmt/cb72nMHbLQrA1XHD/vPp0qKN3h7mSnsLn27LhYIfiv3dA7exBJcjvMtWQr4Fhv4RYvwo2l7XeyFX7fHU9kehSFwEpjl5LrvpPucFKyCuo/efDhel4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1749476711; c=relaxed/simple; bh=ZaFox6XoUC+UN13Ol6isfzjWCIb9kpqGOuujsSRcObk=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=X0jRs27I8VxT4rSQpIquL+0lg9JI9syd5xRiPJ7KKhBrJv5cv/DG37WRqqMFNNpsKE7x5GYOvRwEP7Df1J23aCnqmq3oJBAXXNLsjmh+pePA1B3Jv+Wo8JuOD+XfUu7uqNm74BQ7KaC63XCrIUtpVMw66neEtc0Y5NZm+YFBW0M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Vg2H8mZp; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Vg2H8mZp" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F14DEC4CEED; Mon, 9 Jun 2025 13:45:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1749476709; bh=ZaFox6XoUC+UN13Ol6isfzjWCIb9kpqGOuujsSRcObk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Vg2H8mZpJ9gallejvJSVeif71ia8uVHVw9iSaOX/uT5Kbz8G4HYgs8RBCIKl0cnwi N9Rnb+uIsV2Enn+FeWOkwDjhRG6MswcmPF2E4rFXe8fyvJ8X3Dw3Dj6WWGwtrXTBym RS76HfL/z+tEIT4++jFryLzWRZpCmyXWYdhq9AmLh+vKpiQS8VrBz1WyVtg+Skmdt3 u4EZQv9828m1LKhY5qs0NvSPgUKQAkngyIOwuLxlpwzxRTye7SnvuYCNd+iPlN70VX M4sJmRhCuM3VWJXlSE6tj61YBhp9wauLAebCgfzQXtlX1FDbL0BLJbdoGx/3LrWHoE L8u8ma5KA52rQ== From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Michael Grzeschik , Heikki Krogerus , Greg Kroah-Hartman , Sasha Levin , linux-usb@vger.kernel.org Subject: [PATCH AUTOSEL 6.15 35/35] usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set Date: Mon, 9 Jun 2025 09:43:51 -0400 Message-Id: <20250609134355.1341953-35-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250609134355.1341953-1-sashal@kernel.org> References: <20250609134355.1341953-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.15.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Michael Grzeschik [ Upstream commit 0f7bbef1794dc87141897f804e5871a293aa174b ] Since the typec connectors can have many muxes or switches for different lanes (sbu, usb2, usb3) going into different modal states (usb2, usb3, audio, debug) all of them will be called on typec_switch_set and typec_mux_set. But not all of them will be handling the expected mode. If one of the mux or switch will come back with EOPTNOSUPP this is no reason to stop running through the next ones. Therefor we skip this particular error value and continue calling the next. Signed-off-by: Michael Grzeschik Reviewed-by: Heikki Krogerus Link: https://lore.kernel.org/r/20250404-ml-topic-typec-mux-v1-1-22c0526381ba@pengutronix.de Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin --- This appears to be a recent Linux kernel tree. Let me simulate what the issue would be by looking at the original problematic code. Based on the commit diff provided, the issue is: **Original problematic code:** ```c ret = sw_dev->set(sw_dev, orientation); if (ret) return ret; ``` **Fixed code:** ```c ret = sw_dev->set(sw_dev, orientation); if (ret && ret != -EOPNOTSUPP) return ret; ``` Now I can analyze this commit properly: **Analysis:** **YES** - This commit should be backported to stable kernel trees. **Detailed Analysis:** 1. **Bug Description**: The commit fixes a functional bug where multiple USB Type-C muxes/switches connected to a single connector would fail to be configured if any one of them returned `-EOPNOTSUPP` (Operation Not Supported). This is a common scenario in modern Type-C connectors that have separate muxes for different signal paths (SBU, USB2, USB3, etc.). 2. **Specific Code Changes**: - In `typec_switch_set()` at line 217: Changes `if (ret)` to `if (ret && ret != -EOPNOTSUPP)` - In `typec_mux_set()` at line 381: Changes `if (ret)` to `if (ret && ret != -EOPNOTSUPP)` 3. **Problem Impact**: Before this fix, when `typec_set_orientation()` or `typec_set_mode()` were called: - The functions would iterate through all mux/switch devices - If ANY mux returned `-EOPNOTSUPP` (which is legitimate - some muxes only handle specific modes), the entire operation would fail - This prevented other muxes that COULD handle the mode from being configured - Result: Type-C connectors with multiple muxes would not work properly 4. **Risk Assessment**: - **Very Low Risk**: The change only affects error handling logic - **Minimal Code Change**: Only two lines changed, both adding the same condition - **Backward Compatible**: Does not change API or behavior for successful cases - **Well-Contained**: Limited to the USB Type-C mux subsystem 5. **Stable Tree Criteria Met**: - ✅ **Important Bug Fix**: Fixes functional issues with Type-C connectors - ✅ **Minimal Risk**: Very small, contained change - ✅ **No New Features**: Pure bug fix, no new functionality - ✅ **Clear Side Effects**: No unintended side effects beyond fixing the issue - ✅ **Affects Users**: Type-C devices with multiple muxes (common in modern systems) would malfunction 6. **Evidence from Mux Drivers**: The examination of actual mux drivers like `fsa4480.c` and `gpio-sbu-mux.c` shows they legitimately return `-EOPNOTSUPP` for unsupported modes, confirming this is expected behavior that should not abort the entire chain. 7. **Comparison to Similar Commits**: Unlike the provided reference commits which were mostly cleanups or minor features (all marked NO for backport), this addresses a clear functional bug affecting real- world hardware configurations. This commit follows the stable tree rules perfectly: it's an important bugfix with minimal risk that affects users with multi-mux Type-C hardware configurations. drivers/usb/typec/mux.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/usb/typec/mux.c b/drivers/usb/typec/mux.c index 49926d6e72c71..182c902c42f61 100644 --- a/drivers/usb/typec/mux.c +++ b/drivers/usb/typec/mux.c @@ -214,7 +214,7 @@ int typec_switch_set(struct typec_switch *sw, sw_dev = sw->sw_devs[i]; ret = sw_dev->set(sw_dev, orientation); - if (ret) + if (ret && ret != -EOPNOTSUPP) return ret; } @@ -378,7 +378,7 @@ int typec_mux_set(struct typec_mux *mux, struct typec_mux_state *state) mux_dev = mux->mux_devs[i]; ret = mux_dev->set(mux_dev, state); - if (ret) + if (ret && ret != -EOPNOTSUPP) return ret; } -- 2.39.5