From 9eb34f92600e3379b8cfeba3d3ce28dd39ae4ebc Mon Sep 17 00:00:00 2001 From: Rune Paamand Date: Wed, 8 Jan 2020 12:34:42 +0100 Subject: [PATCH] Fixed ambiguity of "read" vs "write". --- .../content/winusb/nf-winusb-winusb_readisochpipeasap.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sdk-api-src/content/winusb/nf-winusb-winusb_readisochpipeasap.md b/sdk-api-src/content/winusb/nf-winusb-winusb_readisochpipeasap.md index 124e914e5132..8c3c1212b78c 100644 --- a/sdk-api-src/content/winusb/nf-winusb-winusb_readisochpipeasap.md +++ b/sdk-api-src/content/winusb/nf-winusb-winusb_readisochpipeasap.md @@ -111,8 +111,8 @@ If the caller sets ContinueStream to TRUE, The transfer fails if Winusb.s WinUsb_ReadIsochPipeAsap allows the USB driver stack to choose the starting frame number for the transfer. If one or more transfers are already pending on the endpoint, the transfer will be scheduled for the frame number immediately following the last frame number of the last currently pending transfer. -WinUsb_ReadIsochPipeAsap packetizes the transfer buffer so that in each interval, the host can send the maximum bytes allowed per interval. The maximum bytes is as specified by the endpoint descriptor for full and high-speed endpoints, and endpoint companion descriptor for SuperSpeed endpoints. -If the caller submits multiple write requests to stream data to the device, the transfer size should be a multiple of the maximum bytes per interval (as returned by WinUsb_QueryPipeEx) * 8 / interval. +WinUsb_ReadIsochPipeAsap packetizes the transfer buffer so that in each interval, the host can receive the maximum bytes allowed per interval. The maximum bytes is as specified by the endpoint descriptor for full and high-speed endpoints, and endpoint companion descriptor for SuperSpeed endpoints. +If the caller submits multiple read requests to stream data from the device, the transfer size should be a multiple of the maximum bytes per interval (as returned by WinUsb_QueryPipeEx) * 8 / interval.