lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 21 Sep 2021 02:15:43 +0530
From:   Amit Pundir <>
To:     Wesley Cheng <>
Cc:     Felipe Balbi <>,
        Greg Kroah-Hartman <>,
        Andy Gross <>,
        Bjorn Andersson <>,
        Rob Herring <>,
        Jack Pham <>,
        Thinh Nguyen <>,
        John Stultz <>,, lkml <>,
        linux-arm-msm <>,
        dt <>
Subject: dwc3-qcom: tx-fifo-resize regression on Poco F1 (sdm845) with v5.15-rc1

Hi Wesley, All,

I see a reboot loop on Xiaomi Pocophone F1 (sdm845) with TX FIFO
resize patches which landed in v5.15-rc1. Upstream commit cefdd52fa045
"usb: dwc3: dwc3-qcom: Enable tx-fifo-resize property by default" to
be specific, which switched on this feature by default.

At times the phone crashes into the fastboot mode after the reboot
loop, but mostly end up booting to UI after a while. This is what it
looks like

PocoF1 does support TX fifo resizing as I can see that in the
downstream dts. So maybe it is the tx-fifo-max-num which need to be
adjusted for the device? I couldn't find the tx-fifo-max-num
equivalent in the downstream tree though

Curious if you had any ideas what might be going wrong? For now I'll
keep digging around tx-fifo-max-num, but I figured I'd ask just in
case it's obvious to you.

Amit Pundir

Powered by blists - more mailing lists