From 31232de07ef2bd97ff67625976eecd97eeb1bd3d Mon Sep 17 00:00:00 2001 From: Marek Vasut Date: Mon, 6 Apr 2020 14:29:44 +0200 Subject: usb: Keep async schedule running only across mass storage xfers Rather than keeping the asynchronous schedule running always, keep it running only across USB mass storage transfers for now, as it seems that keeping it running all the time interferes with certain control transfers during device enumeration. Note that running the async schedule all the time should not be an issue, especially on EHCI HCD, as that one implements most of the transfers using async schedule. Note that we have usb_disable_asynch(), which however is utterly broken. The usb_disable_asynch() blocks the USB core from doing async transfers by setting a global flag. The async schedule should however be disabled per USB controller. Moreover, setting a global flag does not prevent the controller from using the async schedule, which e.g. the EHCI HCD does. This patch implements additional callback to the controller, which permits it to lock the async schedule and keep it running across multiple transfers. Once the schedule is unlocked, it must also be disabled. This thus prevents the async schedule from running outside of the USB mass storage transfers. Signed-off-by: Marek Vasut Cc: Lukasz Majewski Cc: Tom Rini Tested-by: Tom Rini [omap3_beagle, previously failing] --- common/usb.c | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'common/usb.c') diff --git a/common/usb.c b/common/usb.c index 349e838f1d5..686f09a77d1 100644 --- a/common/usb.c +++ b/common/usb.c @@ -172,6 +172,12 @@ int usb_detect_change(void) return change; } +/* Lock or unlock async schedule on the controller */ +__weak int usb_lock_async(struct usb_device *dev, int lock) +{ + return 0; +} + /* * disables the asynch behaviour of the control message. This is used for data * transfers that uses the exclusiv access to the control and bulk messages. -- cgit v1.2.3