summaryrefslogtreecommitdiffstats
path: root/drivers/remoteproc/qcom_common.h
diff options
context:
space:
mode:
authorSerge Semin <Sergey.Semin@baikalelectronics.ru>2020-12-10 09:50:06 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-12-28 15:55:37 +0100
commitce722da66d3e9384aa2de9d33d584ee154e5e157 (patch)
treec65f815cd5b4b9222d7cd8971367307a19f7071e /drivers/remoteproc/qcom_common.h
parentUSB: yurex: fix control-URB timeout handling (diff)
downloadlinux-ce722da66d3e9384aa2de9d33d584ee154e5e157.tar.xz
linux-ce722da66d3e9384aa2de9d33d584ee154e5e157.zip
usb: dwc3: ulpi: Use VStsDone to detect PHY regs access completion
In accordance with [1] the DWC_usb3 core sets the GUSB2PHYACCn.VStsDone bit when the PHY vendor control access is done and clears it when the application initiates a new transaction. The doc doesn't say anything about the GUSB2PHYACCn.VStsBsy flag serving for the same purpose. Moreover we've discovered that the VStsBsy flag can be cleared before the VStsDone bit. So using the former as a signal of the PHY control registers completion might be dangerous. Let's have the VStsDone flag utilized instead then. [1] Synopsys DesignWare Cores SuperSpeed USB 3.0 xHCI Host Controller Databook, 2.70a, December 2013, p.388 Fixes: 88bc9d194ff6 ("usb: dwc3: add ULPI interface support") Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru> Link: https://lore.kernel.org/r/20201210085008.13264-2-Sergey.Semin@baikalelectronics.ru Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/remoteproc/qcom_common.h')
0 files changed, 0 insertions, 0 deletions