if we don't set DMA address to invalid when unmapping, we might fall in a situation where request buffer can't be mapped to DMA again. Signed-off-by: Felipe Balbi <balbi@xxxxxx> --- this is in my dwc3 branch, will go to Greg on my pull request for -next merge window around rc4 or rc5. drivers/usb/dwc3/gadget.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index 2ee6714..7fa996e 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -87,6 +87,7 @@ void dwc3_unmap_buffer_from_dma(struct dwc3_request *req) dma_sync_single_for_cpu(dwc->dev, req->request.dma, req->request.length, req->direction ? DMA_TO_DEVICE : DMA_FROM_DEVICE); + req->request.dma = DMA_ADDR_INVALID; } } -- 1.7.6.396.ge0613 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
