[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f9f7514a-8841-43b8-b01e-aef4aceb8d3a@oss.qualcomm.com>
Date: Wed, 28 Jan 2026 21:39:02 +0530
From: Krishna Kurapati <krishna.kurapati@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: qcom: talos: Flatten usb controller
nodes
On 1/28/2026 4:01 PM, Konrad Dybcio wrote:
> On 1/28/26 7:27 AM, Krishna Kurapati wrote:
>> Flatten usb controller nodes and update to using latest bindings
>> and flattened driver approach.
>>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
>> Signed-off-by: Krishna Kurapati <krishna.kurapati@....qualcomm.com>
>> ---
>
> Have you checked whether this brings about the same crash-on-suspend
> issue as it does on Hamoa?
>
> https://lore.kernel.org/linux-arm-msm/71c15a78-7a50-4913-b677-e5308fcabfad@packett.cool/
>
Hi Konrad,
Yes, I did check system suspend use case after flattening and there is
no crash seen.
The only issue I observed (both before and after flattening) is that
waking up from bus suspend, there is an enumeration failure on second
port in host mode, and an xHCI CMD_RUN timeout occurs. The issue is gone
if we keep controller GDSC flags as RET_ON (not the right solution
though). But this issue has nothing to do with flattening. I will sync
up with clocks team and try to fix that host mode issue.
Regards,
Krishna,
Powered by blists - more mailing lists