From: Felipe Balbi <balbi@kernel.org>
To: kun peng <kunpeng0891@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: usb3.0: dwc3: isoc: missisoc while setting the USB transfer UVC data
Date: Thu, 10 Jun 2021 14:38:07 +0300 [thread overview]
Message-ID: <87eeda0x28.fsf@kernel.org> (raw)
In-Reply-To: <CAJa5FiGTsM3+QS-+9P=8EZbNxZm+MqpPM3P4KU+=nD4KeA-qew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Hi,
kun peng <kunpeng0891@gmail.com> writes:
> On Thu, Jun 10, 2021 at 6:07 PM Felipe Balbi <balbi@kernel.org> wrote:
>>
>> Hi,
>>
>> kun peng <kunpeng0891@gmail.com> writes:
>> > Hi ， I'm using the 4*A53 with DWC3 USB controller, my hardware to work
>> > like a USB camera and so make use of the USB 3.0 UVC gadget driver。
>> > usb3.0 isoc transfer with missisoc -18，larger maxburst is set, the
>> > more -18 appears。
>> > but from trace info, the trb has been put in advance。
>> >
>> > test setting:
>> > dwc3 driver version：5.12
>> > PC： potplayer
>> >
>> > maxpacket : 3072
>> > maxburst : 15
>> > interval : 1
>> > UVC_NUM_REQUESTS: 8
>>
>> sorry, you're running 4.14.74 kernel. That's far too old for this forum
>> to help you. Try reproducing with the latest v5.13-rc kernel.
>>
>> --
>> balbi
>
> thanks for your reply.
>
> my kernel is 4.14, but usb and uvc related driver has been update to
> 5.12.0 linux main line.
> The problem mentioned above is after the update.
right, many other things happen in the framework. You could bisect and
try to find the offending commit, but this forum can't do much to help,
sorry.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2021-06-10 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:52 usb3.0: dwc3: isoc: missisoc while setting the USB transfer UVC data kun peng
2021-06-10 10:06 ` Greg KH
2021-06-10 10:07 ` Felipe Balbi
2021-06-10 11:33 ` kun peng
2021-06-10 11:38 ` Felipe Balbi [this message]
2021-06-10 11:45 ` kun peng
2021-06-10 11:40 ` Greg KH
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=87eeda0x28.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=kunpeng0891@gmail.com \
--cc=linux-usb@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox