From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Prashanth K <prashanth.k@oss.qualcomm.com>
Cc: cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/5] Add snps,dis_u3_susphy_quirk for some QC targets
Date: Mon, 21 Apr 2025 09:25:31 -0500 [thread overview]
Message-ID: <174524552575.708487.5624208070172830014.b4-ty@kernel.org> (raw)
In-Reply-To: <20250325123019.597976-1-prashanth.k@oss.qualcomm.com>
On Tue, 25 Mar 2025 18:00:14 +0530, Prashanth K wrote:
> 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. More
> info about the crash at [1].
>
> [...]
Applied, thanks!
[1/5] arm64: dts: qcom: sm8150: Add snps,dis_u3_susphy_quirk
commit: 9bdbd5286ea597db6131c197ae9ee8614cce1890
[2/5] arm64: dts: qcom: sm8350: Add snps,dis_u3_susphy_quirk
commit: a7dac91e56ae58e1479002e5b94fab73039f2e29
[3/5] arm64: dts: qcom: sm8450: Add snps,dis_u3_susphy_quirk
commit: 9588f10adb5b67bea7eeebed2490c20dfbe82e77
[4/5] arm64: dts: qcom: qcs615: Add snps,dis_u3_susphy_quirk
commit: ad2011e02dab5ccc9f38848a3d909855a4ae7c8f
[5/5] arm64: dts: qcom: qdu1000: Add snps,dis_u3_susphy_quirk
commit: 25eee6c64376fcdc375b97c7e1f105e132654563
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-04-21 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 12:30 [PATCH v1 0/5] Add snps,dis_u3_susphy_quirk for some QC targets Prashanth K
2025-03-25 12:30 ` [PATCH v1 1/5] arm64: dts: qcom: sm8150: Add snps,dis_u3_susphy_quirk Prashanth K
2025-03-25 12:30 ` [PATCH v1 2/5] arm64: dts: qcom: sm8350: " Prashanth K
2025-03-25 12:30 ` [PATCH v1 3/5] arm64: dts: qcom: sm8450: " Prashanth K
2025-03-25 12:30 ` [PATCH v1 4/5] arm64: dts: qcom: qcs615: " Prashanth K
2025-03-25 12:30 ` [PATCH v1 5/5] arm64: dts: qcom: qdu1000: " Prashanth K
2025-03-25 14:41 ` [PATCH v1 0/5] Add snps,dis_u3_susphy_quirk for some QC targets Konrad Dybcio
2025-03-25 15:01 ` Prashanth K
2025-03-25 16:31 ` Konrad Dybcio
2025-03-25 22:10 ` Bjorn Andersson
2025-03-26 6:08 ` Prashanth K
2025-03-26 13:17 ` Konrad Dybcio
2025-03-26 0:21 ` Dmitry Baryshkov
2025-03-26 5:22 ` Krishna Kurapati
2025-03-26 14:35 ` Dmitry Baryshkov
2025-04-21 14:25 ` Bjorn Andersson [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=174524552575.708487.5624208070172830014.b4-ty@kernel.org \
--to=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=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prashanth.k@oss.qualcomm.com \
--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