From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Ronak Raheja <ronak.raheja@oss.qualcomm.com>,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/3] arm64: dts: qcom: kaanapali: Add USB support for Kaanapali SoC
Date: Mon, 6 Apr 2026 23:22:19 +0530 [thread overview]
Message-ID: <3a415fae-bafc-4e23-bfca-564bff90cf2d@oss.qualcomm.com> (raw)
In-Reply-To: <f971b7d9-8e88-446f-ac93-c3506bca83bb@oss.qualcomm.com>
On 3/30/2026 2:48 PM, Konrad Dybcio wrote:
> On 3/29/26 7:52 PM, Krishna Kurapati wrote:
>> From: Ronak Raheja <ronak.raheja@oss.qualcomm.com>
>>
>> Add the base USB devicetree definitions for Kaanapali platform. The overall
>> chipset contains a single DWC3 USB3 controller (rev. 200a), SS QMP PHY
>> (rev. v8) and M31 eUSB2 PHY.
>>
>> Signed-off-by: Ronak Raheja <ronak.raheja@oss.qualcomm.com>
>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
>> ---
>
> [...]
>
>> + usb: usb@a600000 {
>> + compatible = "qcom,kaanapali-dwc3", "qcom,snps-dwc3";
>> + reg = <0x0 0x0a600000 0x0 0xfc100>;
>
> Following the woes on Hamoa, can the platform suspend and wake up
> succesfully with the flattened DT node?
>
There is a crash on resume when I tested but it comes up even without my
changes:
[ 65.263890] Call trace:
[ 65.266489] kthreads_update_affinity+0x94/0x158 (P)
[ 65.271664] kthreads_online_cpu+0x14/0x84
[ 65.275951] cpuhp_invoke_callback+0xdc/0x1dc
[ 65.280514] cpuhp_thread_fun+0x11c/0x168
[ 65.284717] smpboot_thread_fn+0x1e4/0x24c
[ 65.289019] kthread+0x104/0x124
[ 65.292411] ret_from_fork+0x10/0x20
[ 65.296156] Code: f94002f7 eb1602ff 540003a0 f85f82e8 (b9402d09)
[ 65.302490] ---[ end trace 0000000000000000 ]---
Hence I believe my changes are not causing any crash.
Regards,
Krishna,
next prev parent reply other threads:[~2026-04-06 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 17:52 [PATCH v2 0/3] Add USB support for Kaanapali Krishna Kurapati
2026-03-29 17:52 ` [PATCH v2 1/3] arm64: dts: qcom: kaanapali: Add USB support for Kaanapali SoC Krishna Kurapati
2026-03-30 2:52 ` Jingyi Wang
2026-03-30 9:18 ` Konrad Dybcio
2026-04-06 17:52 ` Krishna Kurapati [this message]
2026-03-29 17:52 ` [PATCH v2 2/3] arm64: dts: qcom: kaanpaali: Add USB support for MTP platform Krishna Kurapati
2026-03-30 9:19 ` Konrad Dybcio
2026-04-03 20:09 ` Akhil P Oommen
2026-04-03 20:20 ` Dmitry Baryshkov
2026-04-04 16:11 ` Akhil P Oommen
2026-04-04 19:31 ` Dmitry Baryshkov
2026-03-29 17:52 ` [PATCH v2 3/3] arm64: dts: qcom: kaanpaali: Add USB support for QRD platform Krishna Kurapati
2026-03-29 18:07 ` Dmitry Baryshkov
2026-03-29 18:15 ` Krishna Kurapati
2026-03-30 11:01 ` Dmitry Baryshkov
2026-03-30 13:21 ` [PATCH v2 0/3] Add USB support for Kaanapali Bjorn Andersson
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=3a415fae-bafc-4e23-bfca-564bff90cf2d@oss.qualcomm.com \
--to=krishna.kurapati@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ronak.raheja@oss.qualcomm.com \
/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