VS request completed with status -18.

[Gladsonba]

We are using zynq Ultrascale + MPSoC with custom board.
Our board has 2 USB ports(Host 2.0 and device 3.0), 2 SDI(one input and another output).
Kernel version on board is 4.19.0 and In host PC 5.4.0-58-generic.
Final project according to customers requirement is Streaming 1080p video taking input from SDI and taking output from USB UVC(device).
Currently We are trying with connecting C922 Pro Stream Webcam to USB(host) port.This creates /dev/video0 node.
Then modprobe g_webcam. This creates /dev/video1.
Using the application https://github.com/peterbay/uvc-gadget. At host side /dev/video0 is created.
When I try to display using application such as guvcview, at the device side, getting below attached log.
I need some more input so that I can move forward with this project.
From host side:
ffplay /dev/video0
Dequeued v4l2 buffer contains corrupted data (0 bytes).
From device:
[ 1563.216999] VS request completed with status -18.
[ 1563.229986] VS request completed with status -18.
UVC: Possible USB shutdown requested from Host, seen during VIDI[ 1563.234674] VS request completed with status -18.
OC_DQBUF
select timeout
[ 1573.292465] dwc3 fe200000.dwc3: request 00000000af72569b was not queued to ep2in
[ 1573.299868] dwc3 fe200000.dwc3: request 00000000bbc4cf8d was not queued to ep2in
[ 1573.307273] dwc3 fe200000.dwc3: request 00000000849239a7 was not queued to ep2in
[ 1573.314668] dwc3 fe200000.dwc3: request 0000000023561ba0 was not queued to ep2in
UVC: Stopping video stream.
USBGITLOG.txt

[66cavy]

Hello, I'm using zynq to implement UVC. The underlying USB3.0 hardware has been enabled. Please refer to the official tutorial given by Xilinx：”https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/2046001302/Building+Linux+usb+device+drivers+with+2021.1#UVC-Gadget“；
But the results I got are inconsistent with those in the tutorial. Figure 1 shows the results of the tutorial, and Figure 2 shows the results I produced according to the tutorial. Why is this?
picture 1：

picture 2：The process will be stuck in "v4l2:2 buffers allocated", and there will be no change