From: Prashanth K <quic_prashk@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<cros-qcom-dts-watchers@chromium.org>,
Prashanth K <quic_prashk@quicinc.com>
Subject: [PATCH v3 01/19] arm64: dts: qcom: Disable USB U1/U2 entry for SM8350
Date: Wed, 18 Dec 2024 15:56:49 +0530 [thread overview]
Message-ID: <20241218102707.76272-2-quic_prashk@quicinc.com> (raw)
In-Reply-To: <20241218102707.76272-1-quic_prashk@quicinc.com>
From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Disable U1 and U2 power-saving states to improve stability of USB.
These low-power link states, designed to reduce power consumption
during idle periods, can cause issues in latency-sensitive or high
throughput use cases. Over the years, some of the issues seen are
as follows:
1. In device mode of operation, when UVC is active, enabling U1/U2
is sometimes causing packets drops due to delay in entry/exit of
intermittent these low power states. These packet drops are often
reflected as missed isochronous transfers, as the controller wasn't
able to send packet in that microframe interval and hence glitches
are seen on the final transmitted video output.
2. On older targets like SM8150/SM8250/SM8350, there have been
throughput issues seen during tethering use cases.
Disabling these intermittent power states enhances device stability
without affecting power usage.
Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Signed-off-by: Prashanth K <quic_prashk@quicinc.com>
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8350.dtsi b/arch/arm64/boot/dts/qcom/sm8350.dtsi
index 877905dfd861..e8f9d8bab309 100644
--- a/arch/arm64/boot/dts/qcom/sm8350.dtsi
+++ b/arch/arm64/boot/dts/qcom/sm8350.dtsi
@@ -2409,6 +2409,8 @@ usb_1_dwc3: usb@a600000 {
iommus = <&apps_smmu 0x0 0x0>;
snps,dis_u2_susphy_quirk;
snps,dis_enblslpm_quirk;
+ snps,dis-u1-entry-quirk;
+ snps,dis-u2-entry-quirk;
phys = <&usb_1_hsphy>, <&usb_1_qmpphy QMP_USB43DP_USB3_PHY>;
phy-names = "usb2-phy", "usb3-phy";
@@ -2485,6 +2487,8 @@ usb_2_dwc3: usb@a800000 {
iommus = <&apps_smmu 0x20 0x0>;
snps,dis_u2_susphy_quirk;
snps,dis_enblslpm_quirk;
+ snps,dis-u1-entry-quirk;
+ snps,dis-u2-entry-quirk;
phys = <&usb_2_hsphy>, <&usb_2_qmpphy>;
phy-names = "usb2-phy", "usb3-phy";
};
--
2.25.1
next prev parent reply other threads:[~2024-12-18 10:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 10:26 [PATCH v3 00/19] Disable USB U1/U2 entry for QC targets Prashanth K
2024-12-18 10:26 ` Prashanth K [this message]
2024-12-18 10:26 ` [PATCH v3 02/19] arm64: dts: qcom: Disable USB U1/U2 entry for SM8450 Prashanth K
2024-12-18 10:26 ` [PATCH v3 03/19] arm64: dts: qcom: Disable USB U1/U2 entry for SM8150 Prashanth K
2024-12-18 10:26 ` [PATCH v3 04/19] arm64: dts: qcom: Disable USB U1/U2 entry for SM6125 Prashanth K
2024-12-18 10:26 ` [PATCH v3 05/19] arm64: dts: qcom: Disable USB U1/U2 entry for SM8250 Prashanth K
2024-12-18 10:26 ` [PATCH v3 06/19] arm64: dts: qcom: Disable USB U1/U2 entry for SM6350 Prashanth K
2024-12-18 10:26 ` [PATCH v3 07/19] arm64: dts: qcom: Disable USB U1/U2 entry for SC7280 Prashanth K
2024-12-18 10:26 ` [PATCH v3 08/19] arm64: dts: qcom: Disable USB U1/U2 entry for SA8775P Prashanth K
2024-12-18 10:26 ` [PATCH v3 09/19] arm64: dts: qcom: Disable USB U1/U2 entry for SDM630 Prashanth K
2024-12-18 10:26 ` [PATCH v3 10/19] arm64: dts: qcom: Disable USB U1/U2 entry for SDM845 Prashanth K
2024-12-18 10:26 ` [PATCH v3 11/19] arm64: dts: qcom: Disable USB U1/U2 entry for SDX75 Prashanth K
2024-12-18 10:27 ` [PATCH v3 12/19] ARM: dts: qcom: Disable USB U1/U2 entry for SDX65 Prashanth K
2024-12-18 10:27 ` [PATCH v3 13/19] ARM: dts: qcom: Disable USB U1/U2 entry for SDX55 Prashanth K
2024-12-18 10:27 ` [PATCH v3 14/19] arm64: dts: qcom: Disable USB U1/U2 entry for QCS404 Prashanth K
2024-12-18 10:27 ` [PATCH v3 15/19] arm64: dts: qcom: Disable USB U1/U2 entry for SC7180 Prashanth K
2024-12-18 10:27 ` [PATCH v3 16/19] arm64: dts: qcom: Disable USB U1/U2 entry for X1E80100 Prashanth K
2024-12-18 10:27 ` [PATCH v3 17/19] arm64: dts: qcom: Disable USB U1/U2 entry for QDU1000 Prashanth K
2024-12-18 10:27 ` [PATCH v3 18/19] arm64: dts: qcom: Disable USB U1/U2 entry for SC8280XP Prashanth K
2024-12-18 10:27 ` [PATCH v3 19/19] arm64: dts: qcom: Disable USB U1/U2 entry for SC8180X Prashanth K
2024-12-18 11:27 ` [PATCH v3 00/19] Disable USB U1/U2 entry for QC targets Dmitry Baryshkov
2024-12-18 11:48 ` Prashanth K
2024-12-19 3:07 ` Dmitry Baryshkov
2024-12-19 4:17 ` Prashanth K
2024-12-19 13:14 ` Dmitry Baryshkov
2024-12-20 4:24 ` Prashanth K
2024-12-23 14:39 ` Konrad Dybcio
2024-12-26 4:43 ` Bjorn Andersson
2024-12-26 4:55 ` Prashanth K
2024-12-30 13:33 ` Konrad Dybcio
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=20241218102707.76272-2-quic_prashk@quicinc.com \
--to=quic_prashk@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®