public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Youn <John.Youn@synopsys.com>
To: John Keeping <john@metanate.com>, John Youn <John.Youn@synopsys.com>
Cc: Roman Bacik <rbacik@broadcom.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problem with dwc2 gadget isochronous in transfers
Date: Thu, 24 Mar 2016 10:48:46 -0700	[thread overview]
Message-ID: <56F4287E.4000308@synopsys.com> (raw)
In-Reply-To: <20160324113136.15ad2026.john@metanate.com>

On 3/24/2016 4:32 AM, John Keeping wrote:
> Hi,
> 
> I've been trying to use the uac2 gadget function on a Radxa Rock2 board
> which uses the dwc2 driver, but it seems there is a problem with
> isochronous in endpoints (out works fine).
> 
> When trying to use the audio gadget no data is transferred and the other
> end of the link ends up timing out.  With debug logging enabled in dwc2
> the GINTSTS_INCOMPL_SOIN interrupt triggers continuously, as seen in the
> log below (from which I snipped 6,000+ more occurences).  I'm guessing
> the root cause of this relates to the line:
> 
>     [  320.656450] dwc2 ff580000.usb: dwc2_hsotg_epint: EPDisbld
> 
> during the setup phase, but I have no idea why that's happening.
> 


Hi John,

We have a patch series that fixes up the ISOC code and which possibly
addresses the failures here. We hope to submit them for review within
the next week or so.

Appreciate if you would test and report any problems based off of
those patches.

Regards,
John

      reply	other threads:[~2016-03-24 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 11:31 Problem with dwc2 gadget isochronous in transfers John Keeping
2016-03-24 17:48 ` John Youn [this message]

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=56F4287E.4000308@synopsys.com \
    --to=john.youn@synopsys.com \
    --cc=john@metanate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rbacik@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox