From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: PALAK SHAH <palak.shah@raritan.com>,
Maynard CABIENTE <maynard.cabiente@raritan.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: usb: gadget: dwc2: not getting audio data
Date: Tue, 16 May 2023 07:51:07 +0000 [thread overview]
Message-ID: <744c32ed-e8c5-9e02-c778-ec3538c954bb@synopsys.com> (raw)
In-Reply-To: <PAXPR06MB8531D31F642598C1D9B8555B8D749@PAXPR06MB8531.eurprd06.prod.outlook.com>
Hi Palak,
On 5/11/23 17:16, PALAK SHAH wrote:
> Hi Minas,
>
> Can you please respond to this? We need USB Audio Gadget working and we
> cannot proceed without Synopsis support on this.
>
> Thanks,
>
> Palak
>
> *From:* PALAK SHAH
> *Sent:* Tuesday, May 9, 2023 10:52 AM
> *To:* Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>; Maynard
> CABIENTE <maynard.cabiente@raritan.com>
> *Cc:* linux-usb@vger.kernel.org
> *Subject:* RE: usb: gadget: dwc2: not getting audio data
>
> Hi Minas,
>
> I have updated the kernel to 5.10.100. I have done the IP core test and
> all the tests (esp. t15 and t16 for ISOC) pass on our system.
>
> However, I am still seeing the original problem. USB gadget DWC2 driver
> is getting stuck and not getting the transfers completed.
>
> When I am running audio on the host, and trying to capture the data on
> EP1(out) end point -
>
> [ 270.855174] dwc2 ffb40000.usb: dwc2_hsotg_irq: gintsts: 042c8028,
> gintsts & gintmsk: 000c0000, gintmsk: (d08c3c44) retry 8
> [ 270.855189] dwc2 ffb40000.usb: dwc2_hsotg_irq: daint=00020002
> [ 270.855205] dwc2 ffb40000.usb: dwc2_hsotg_epint: ep1(out)
> DxEPINT=0x00000001
> [ 270.855218] dwc2 ffb40000.usb: dwc2_hsotg_epint: XferCompl:
> DxEPCTL=0x800480c8, DXEPTSIZ=11e55680
> [ 270.855238] dwc2 ffb40000.usb: complete: ep 822473bd ep1out, req
> 76bf77e8, 0 => 778da9a8
> [ 270.855260] dwc2 ffb40000.usb: ep1out: req 76bf77e8: 200@1c821d4e,
> noi=0, zero=0, snok=0
> [ 270.855279] dwc2 ffb40000.usb: dwc2_gadget_fill_isoc_desc: Filling ep
> 1, dir out isoc desc # 195
> [ 270.855292] dwc2 ffb40000.usb:
> dwc2_gadget_complete_isoc_request_ddma: compl_desc # 193
>
> [ 270.856242] dwc2 ffb40000.usb: dwc2_hsotg_irq: gintsts: 04288028,
> gintsts & gintmsk: 00080000, gintmsk: (d08c3c44) retry 8
> [ 270.856255] dwc2 ffb40000.usb: dwc2_hsotg_irq: daint=00020000
> [ 270.856268] dwc2 ffb40000.usb: dwc2_hsotg_epint: ep1(out)
> DxEPINT=0x00000001
> [ 270.856282] dwc2 ffb40000.usb: dwc2_hsotg_epint: XferCompl:
> DxEPCTL=0x800480c8, DXEPTSIZ=11dd5620
> [ 270.856311] dwc2 ffb40000.usb: complete: ep 822473bd ep1out, req
> 5af4a660, 0 => 778da9a8
> [ 270.856346] dwc2 ffb40000.usb: ep1out: req 5af4a660: 200@f8820950,
> noi=0, zero=0, snok=0
> [ 270.856371] dwc2 ffb40000.usb: dwc2_gadget_fill_isoc_desc: Filling ep
> 1, dir out isoc desc # 196
> [ 270.856398] dwc2 ffb40000.usb:
> dwc2_gadget_complete_isoc_request_ddma: compl_desc # 194
>
> [ 281.700537] dwc2 ffb40000.usb: dwc2_hsotg_irq: daint=00020002
> [ 281.700552] dwc2 ffb40000.usb: dwc2_hsotg_epint: ep1(out)
> DxEPINT=0x00000010
> [ 281.700564] dwc2 ffb40000.usb:
> dwc2_gadget_handle_out_token_ep_disabled: target_frame = 0x000013d0
> [ 281.700580] dwc2 ffb40000.usb: dwc2_gadget_fill_isoc_desc: Filling ep
> 1, dir out isoc desc # 0
> [ 281.700594] dwc2 ffb40000.usb: dwc2_gadget_fill_isoc_desc: Filling ep
> 1, dir out isoc desc # 1
>
> At 270 seconds, the request #194 was completed and request #196 was
> queued. But right after that, there was a 11 second gap and the request
> #195 was never completed.
>
> For some unknown reason, the DWC2 core just stops. There is nothing in
> our system that causes it to get stuck. The interrupts are not disabled.
> The USB sniffer data shows that the data is coming in. However, dwc2 is
> not running.
> After the time gap, everything stop working.
>
> I have attached the log file here. Can you please help me fix this dwc2
> core issue?
>
> Thanks,
> Palak
>
>
Based on your usbtest successful results for ISOCs, both core and dwc2
driver works OK.
As I recommended earlier, please try:
1. Depend on which uac(uac1 or uac2) you use, increase
UAC1/2_DEF_REQ_NUM 2 to 32
2. Change descriptor DMA (DDMA) mode to buffer DMA (BDMA) mode
Thanks,
Minas
next prev parent reply other threads:[~2023-05-16 7:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR0601MB25868E34AF4BA6CEAFE06F5F8DA39@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2023-02-22 6:39 ` usb: gadget: dwc2: not getting audio data Minas Harutyunyan
[not found] ` <HE1PR0601MB2586BFAE94813BA86BAB12708DAA9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2023-02-23 6:31 ` Minas Harutyunyan
[not found] ` <HE1PR0601MB25868FC836C3CD2D07B342958DAB9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2023-02-24 10:32 ` Minas Harutyunyan
2023-02-27 2:02 ` Palak SHAH
2023-02-27 10:18 ` Minas Harutyunyan
[not found] ` <HE1PR0601MB2586DB1CA3D0B4B45E7720A68DAF9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2023-03-01 19:29 ` Palak SHAH
2023-03-02 21:38 ` Palak SHAH
2023-03-03 4:35 ` Minas Harutyunyan
2023-03-06 16:25 ` Palak SHAH
2023-03-07 4:30 ` Minas Harutyunyan
2023-03-08 21:42 ` Palak SHAH
2023-03-09 10:03 ` Minas Harutyunyan
2023-03-09 16:21 ` Palak SHAH
2023-03-10 9:03 ` Minas Harutyunyan
2023-04-06 1:42 ` PALAK SHAH
2023-04-06 4:56 ` Minas Harutyunyan
2023-04-06 18:06 ` PALAK SHAH
[not found] ` <PAXPR06MB85319DCC50F69D0790D5F4198D719@PAXPR06MB8531.eurprd06.prod.outlook.com>
[not found] ` <PAXPR06MB8531E23298F9BA26C1E651AC8D769@PAXPR06MB8531.eurprd06.prod.outlook.com>
[not found] ` <PAXPR06MB8531BF29DA170252843DD5598D769@PAXPR06MB8531.eurprd06.prod.outlook.com>
[not found] ` <PAXPR06MB8531D31F642598C1D9B8555B8D749@PAXPR06MB8531.eurprd06.prod.outlook.com>
2023-05-16 7:51 ` Minas Harutyunyan [this message]
2023-05-16 7:53 ` Minas Harutyunyan
2023-05-16 20:43 ` PALAK SHAH
2023-05-17 6:04 ` Minas Harutyunyan
2023-05-17 19:02 ` PALAK SHAH
2023-05-18 11:22 ` Minas Harutyunyan
2023-05-18 18:32 ` PALAK SHAH
2023-05-19 13:22 ` Minas Harutyunyan
[not found] ` <PAXPR06MB85314C9FAD4BFEA5ED1B6F828D0DA@PAXPR06MB8531.eurprd06.prod.outlook.com>
2023-08-14 14:47 ` PALAK SHAH
2023-08-15 8:44 ` Minas Harutyunyan
[not found] ` <PAXPR06MB85318E88964FE24F74139C678D14A@PAXPR06MB8531.eurprd06.prod.outlook.com>
2023-08-25 18:32 ` PALAK SHAH
2023-08-28 10:46 ` Minas Harutyunyan
[not found] <HE1PR0601MB2586962582F222B5B889416A8D1B9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
[not found] ` <AS8PR06MB7976A91E44D7DCDAACC723F7971B9@AS8PR06MB7976.eurprd06.prod.outlook.com>
[not found] ` <HE1PR0601MB258625B74749B2DB1242E0048D1B9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
[not found] ` <HE1PR0601MB2586E4A641ECA0D0D043A3798D1D9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
[not found] ` <HE1PR0601MB258685C64D46C08C978C37EB8D1D9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2022-12-09 11:32 ` Minas Harutyunyan
[not found] ` <HE1PR0601MB25861FC1248FF0A61DDBC8F58D1C9@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2022-12-12 12:27 ` Minas Harutyunyan
[not found] ` <HE1PR0601MB2586D03B6D11FDF5F513E2488DE29@HE1PR0601MB2586.eurprd06.prod.outlook.com>
[not found] ` <HE1PR0601MB2586AFC1102D078A26615CBC8DE29@HE1PR0601MB2586.eurprd06.prod.outlook.com>
2022-12-14 6:11 ` Minas Harutyunyan
2022-12-15 21:16 ` Palak SHAH
2022-12-16 7:03 ` Minas Harutyunyan
2023-01-06 21:37 ` Palak SHAH
2023-01-12 10:52 ` Minas Harutyunyan
2023-01-12 20:22 ` Palak SHAH
2023-01-13 8:08 ` Minas Harutyunyan
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=744c32ed-e8c5-9e02-c778-ec3538c954bb@synopsys.com \
--to=minas.harutyunyan@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=maynard.cabiente@raritan.com \
--cc=palak.shah@raritan.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