]> www.infradead.org Git - users/jedix/linux-maple.git/commit
arm64: dts: qcom: qdu1000: Add snps,dis_u3_susphy_quirk
authorPratham Pratap <quic_ppratap@quicinc.com>
Tue, 25 Mar 2025 12:30:19 +0000 (18:00 +0530)
committerBjorn Andersson <andersson@kernel.org>
Mon, 21 Apr 2025 13:50:34 +0000 (08:50 -0500)
commit25eee6c64376fcdc375b97c7e1f105e132654563
treef3a9a7ba28beea9cfdab163e1ffba2af46c9556d
parentad2011e02dab5ccc9f38848a3d909855a4ae7c8f
arm64: dts: qcom: qdu1000: Add snps,dis_u3_susphy_quirk

During device mode initialization on certain QC targets, before the
runstop bit is set, sometimes it's observed that the GEVNTADR{LO/HI}
register write fails. As a result, GEVTADDR registers are still 0x0.
Upon setting runstop bit, DWC3 controller attempts to write the new
events to address 0x0, causing an SMMU fault and system crash.

This was initially observed on SM8450 and later reported on few
other targets as well. As suggested by Qualcomm HW team, clearing
the GUSB3PIPECTL.SUSPHY bit resolves the issue by preventing register
write failures. Address this by setting the snps,dis_u3_susphy_quirk
to keep the GUSB3PIPECTL.SUSPHY bit cleared. This change was tested
on multiple targets (SM8350, SM8450 QCS615 etc.) for over an year
and hasn't exhibited any side effects.

Signed-off-by: Pratham Pratap <quic_ppratap@quicinc.com>
Signed-off-by: Prashanth K <prashanth.k@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20250325123019.597976-6-prashanth.k@oss.qualcomm.com
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
arch/arm64/boot/dts/qcom/qdu1000.dtsi