summaryrefslogtreecommitdiffstats
path: root/mm/huge_memory.c
diff options
context:
space:
mode:
authorPrashanth K <quic_prashk@quicinc.com>2024-05-02 10:11:03 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2024-05-10 10:35:56 +0100
commit1d26ba0944d398f88aaf997bda3544646cf21945 (patch)
tree5d01f654c18c38bf5ef21aa059310c14d9c00128 /mm/huge_memory.c
parente4306116b5e93748b3eaa7666aa55c390b48a8f4 (diff)
downloadlinux-stable-1d26ba0944d398f88aaf997bda3544646cf21945.tar.gz
linux-stable-1d26ba0944d398f88aaf997bda3544646cf21945.tar.bz2
linux-stable-1d26ba0944d398f88aaf997bda3544646cf21945.zip
usb: dwc3: Wait unconditionally after issuing EndXfer command
Currently all controller IP/revisions except DWC3_usb3 >= 310a wait 1ms unconditionally for ENDXFER completion when IOC is not set. This is because DWC_usb3 controller revisions >= 3.10a supports GUCTL2[14: Rst_actbitlater] bit which allows polling CMDACT bit to know whether ENDXFER command is completed. Consider a case where an IN request was queued, and parallelly soft_disconnect was called (due to ffs_epfile_release). This eventually calls stop_active_transfer with IOC cleared, hence send_gadget_ep_cmd() skips waiting for CMDACT cleared during EndXfer. For DWC3 controllers with revisions >= 310a, we don't forcefully wait for 1ms either, and we proceed by unmapping the requests. If ENDXFER didn't complete by this time, it leads to SMMU faults since the controller would still be accessing those requests. Fix this by ensuring ENDXFER completion by adding 1ms delay in __dwc3_stop_active_transfer() unconditionally. Cc: stable@vger.kernel.org Fixes: b353eb6dc285 ("usb: dwc3: gadget: Skip waiting for CMDACT cleared during endxfer") Signed-off-by: Prashanth K <quic_prashk@quicinc.com> Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com> Link: https://lore.kernel.org/r/20240502044103.1066350-1-quic_prashk@quicinc.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/huge_memory.c')
0 files changed, 0 insertions, 0 deletions