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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [RFT PATCH 1/2] arm64: dts: qcom: ipq5018: Correct USB DWC3 wrapper interrupts
Date: Sat, 10 Jan 2026 13:11:21 -0600 [thread overview]
Message-ID: <176807228459.3708332.1322342442812092208.b4-ty@kernel.org> (raw)
In-Reply-To: <20260106185123.19929-3-krzysztof.kozlowski@oss.qualcomm.com>
On Tue, 06 Jan 2026 19:51:24 +0100, Krzysztof Kozlowski wrote:
> Interrupts for DWC3 node were completely mixed up - SPI interrupt 62 is
> not listed in reference manual at all. It was also causing dtbs_check
> warnings:
>
> ipq5018-rdp432-c2.dtb: usb@8af8800 (qcom,ipq5018-dwc3): interrupt-names:0: 'pwr_event' was expected
> ipq5018-rdp432-c2.dtb: usb@8af8800 (qcom,ipq5018-dwc3): interrupt-names: ['hs_phy_irq'] is too short
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: ipq5018: Correct USB DWC3 wrapper interrupts
commit: d106f9681d1952b7c19726b0713cee6ae11211f5
[2/2] arm64: dts: qcom: ipq9574: Complete USB DWC3 wrapper interrupts
commit: bd2dc325db8c8cb29b65b0c636e31babc2bfeddf
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-01-10 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 18:51 [RFT PATCH 1/2] arm64: dts: qcom: ipq5018: Correct USB DWC3 wrapper interrupts Krzysztof Kozlowski
2026-01-06 18:51 ` [RFT PATCH 2/2] arm64: dts: qcom: ipq9574: Complete " Krzysztof Kozlowski
2026-01-08 5:43 ` Kathiravan Thirumoorthy
2026-01-09 4:11 ` Kathiravan Thirumoorthy
2026-01-08 9:42 ` [RFT PATCH 1/2] arm64: dts: qcom: ipq5018: Correct " George Moussalem
2026-01-10 19:11 ` 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=176807228459.3708332.1322342442812092208.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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