From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: "Zengtao \(B\)" <prime.zeng@hisilicon.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: usb: dwc3: gadget: issue a stop command for ISOC endpoint
Date: Thu, 25 Apr 2019 16:03:49 +0300 [thread overview]
Message-ID: <878svys0cq.fsf@linux.intel.com> (raw)
(please, avoid top-posting)
Hi,
"Zengtao (B)" <prime.zeng@hisilicon.com> writes:
> Hi balbi:
>
> I got this issue in the UVC application, and I think this issue still exist in the
> latest dwc3 driver.
>
> And we should issue an stop command and the queue is empty when it's
> ISOC transfer, otherwise we will end up with MISS ISOC error for all the
> upcoming transfers.
>
> So I think you can test the UVC application with the latest driver.
right. Then what do I do? How do you load the driver, how do you start
the application? When do you plug the cable?
Please, provide exact steps so I can try to replicate the problem.
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: "Zengtao \(B\)" <prime.zeng@hisilicon.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: RE: [PATCH] usb: dwc3: gadget: issue a stop command for ISOC endpoint
Date: Thu, 25 Apr 2019 16:03:49 +0300 [thread overview]
Message-ID: <878svys0cq.fsf@linux.intel.com> (raw)
Message-ID: <20190425130349.iUrnb7scAIcAh7gJ9ifC_YS_BsVpQ15wZEy134BLlZ8@z> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED24E7D8F2@dggemm526-mbx.china.huawei.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
(please, avoid top-posting)
Hi,
"Zengtao (B)" <prime.zeng@hisilicon.com> writes:
> Hi balbi:
>
> I got this issue in the UVC application, and I think this issue still exist in the
> latest dwc3 driver.
>
> And we should issue an stop command and the queue is empty when it's
> ISOC transfer, otherwise we will end up with MISS ISOC error for all the
> upcoming transfers.
>
> So I think you can test the UVC application with the latest driver.
right. Then what do I do? How do you load the driver, how do you start
the application? When do you plug the cable?
Please, provide exact steps so I can try to replicate the problem.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2019-04-25 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 13:03 Felipe Balbi [this message]
2019-04-25 13:03 ` [PATCH] usb: dwc3: gadget: issue a stop command for ISOC endpoint Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2019-02-23 9:26 Zengtao (B)
2019-02-23 9:26 ` [PATCH] " Zengtao (B)
2019-01-21 10:02 Zengtao (B)
2019-01-21 10:02 ` [PATCH] " Zeng Tao
2019-01-21 8:16 ` Felipe Balbi
2019-01-21 8:51 ` Zengtao (B)
2019-01-21 8:55 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878svys0cq.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prime.zeng@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.