From: Felipe Balbi <balbi@kernel.org>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>Minas
Harutyunyan <Minas.Harutyunyan@synopsys.com>,
Roger Quadros <rogerq@ti.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [v2] usb: dwc3: Prevent indefinite sleep in _dwc3_set_mode during suspend/resume
Date: Tue, 10 Apr 2018 10:31:13 +0300 [thread overview]
Message-ID: <87r2nnldq6.fsf@linux.intel.com> (raw)
Hi,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> writes:
>>>>>>> Actually to fix this issue I updated condition of wait function
>>>>>>> from:
>>>>>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING)
>>>>>>> to:
>>>>>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING & DWC3_EP_ENABLED)
>>>>>>
>>>>>> you're not fixing anything. You're, essentially, removing the entire
>>>>>> end transfer pending logic.
>>>>> yes, you are right, but how to overcome this infinite loop? Replace
>>>>> wait_event_lock_irq() by wait_event_interruptible_lock_irq_timeout()?
>>>>
>>>> The best way here would be to figure why we're missing command complete
>>>> IRQ in those cases. According to documentation, we *should* receive that
>>>> interrupt, so why is it missing?
>>>>
>>>
>>> Additional info on test. Core configuration is HS only mode, test speed
>>> HS, core version v2.90a. Maybe it will help to understand cause of issue.
>>> BTW, currently to pass above describe ISOC OUT test we just commented
>>> wait_event_lock_irq() in dwc3_gadget_ep_dequeue() function and
>>> successfully received request completion in function driver.
>>> Thanks,
>>> Minas
>>>
>>
>> One more info: while function driver call dequeue, host periodically
>> send control read command to get status of test from function - test In
>> Progress or Finished.
>> Thanks,
>> Minas
>>
>
> Your last dwc3 patch series allow us to successfully dequeuing remaining
> requests without falling in to infinite loop.
that's cool, thanks :-) I'll just fix the documentation bug I introduced
heh :-)
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@kernel.org>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
Roger Quadros <rogerq@ti.com>
Cc: "linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: dwc3: Prevent indefinite sleep in _dwc3_set_mode during suspend/resume
Date: Tue, 10 Apr 2018 10:31:13 +0300 [thread overview]
Message-ID: <87r2nnldq6.fsf@linux.intel.com> (raw)
In-Reply-To: <410670D7E743164D87FA6160E7907A560113AE789A@am04wembxb.internal.synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
Hi,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> writes:
>>>>>>> Actually to fix this issue I updated condition of wait function
>>>>>>> from:
>>>>>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING)
>>>>>>> to:
>>>>>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING & DWC3_EP_ENABLED)
>>>>>>
>>>>>> you're not fixing anything. You're, essentially, removing the entire
>>>>>> end transfer pending logic.
>>>>> yes, you are right, but how to overcome this infinite loop? Replace
>>>>> wait_event_lock_irq() by wait_event_interruptible_lock_irq_timeout()?
>>>>
>>>> The best way here would be to figure why we're missing command complete
>>>> IRQ in those cases. According to documentation, we *should* receive that
>>>> interrupt, so why is it missing?
>>>>
>>>
>>> Additional info on test. Core configuration is HS only mode, test speed
>>> HS, core version v2.90a. Maybe it will help to understand cause of issue.
>>> BTW, currently to pass above describe ISOC OUT test we just commented
>>> wait_event_lock_irq() in dwc3_gadget_ep_dequeue() function and
>>> successfully received request completion in function driver.
>>> Thanks,
>>> Minas
>>>
>>
>> One more info: while function driver call dequeue, host periodically
>> send control read command to get status of test from function - test In
>> Progress or Finished.
>> Thanks,
>> Minas
>>
>
> Your last dwc3 patch series allow us to successfully dequeuing remaining
> requests without falling in to infinite loop.
that's cool, thanks :-) I'll just fix the documentation bug I introduced
heh :-)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-04-10 7:31 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 7:31 Felipe Balbi [this message]
2018-04-10 7:31 ` [PATCH v2] usb: dwc3: Prevent indefinite sleep in _dwc3_set_mode during suspend/resume Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2018-04-10 6:29 [v2] " Minas Harutyunyan
2018-04-10 6:29 ` [PATCH v2] " Minas Harutyunyan
2018-03-19 13:53 [v2] " Minas Harutyunyan
2018-03-19 13:53 ` [PATCH v2] " Minas Harutyunyan
2018-03-19 11:36 [v2] " Minas Harutyunyan
2018-03-19 11:36 ` [PATCH v2] " Minas Harutyunyan
2018-03-19 8:54 [v2] " Felipe Balbi
2018-03-19 8:54 ` [PATCH v2] " Felipe Balbi
2018-03-17 6:33 [v2] " Minas Harutyunyan
2018-03-17 6:33 ` [PATCH v2] " Minas Harutyunyan
2018-03-16 12:25 [v2] " Felipe Balbi
2018-03-16 12:25 ` [PATCH v2] " Felipe Balbi
2018-03-16 11:43 [v2] " Minas Harutyunyan
2018-03-16 11:43 ` [PATCH v2] " Minas Harutyunyan
2018-03-16 11:03 [v2] " Roger Quadros
2018-03-16 11:03 ` [PATCH v2] " Roger Quadros
2018-03-16 11:00 [v2] " Felipe Balbi
2018-03-16 11:00 ` [PATCH v2] " Felipe Balbi
2018-03-16 10:34 [v2] " Roger Quadros
2018-03-16 10:34 ` [PATCH v2] " Roger Quadros
2018-03-09 12:47 [v2] " Roger Quadros
2018-03-09 12:47 ` [PATCH v2] " Roger Quadros
2018-03-09 10:39 Felipe Balbi
2018-03-09 10:39 ` [PATCH] " Felipe Balbi
2018-03-09 10:36 Felipe Balbi
2018-03-09 10:36 ` [PATCH] " Felipe Balbi
2018-03-09 9:49 Roger Quadros
2018-03-09 9:49 ` [PATCH] " Roger Quadros
2018-03-09 9:26 Roger Quadros
2018-03-09 9:26 ` [PATCH] " Roger Quadros
2018-03-09 9:23 Felipe Balbi
2018-03-09 9:23 ` [PATCH] " Felipe Balbi
2018-03-09 9:19 Roger Quadros
2018-03-09 9:19 ` [PATCH] " Roger Quadros
2018-03-05 11:27 Felipe Balbi
2018-03-05 11:27 ` [PATCH] " Felipe Balbi
2018-03-05 11:25 Felipe Balbi
2018-03-05 11:25 ` [PATCH] " Felipe Balbi
2018-03-05 11:25 Baolin Wang
2018-03-05 11:25 ` [PATCH] " Baolin Wang
2018-03-05 11:14 Roger Quadros
2018-03-05 11:14 ` [PATCH] " Roger Quadros
2018-03-05 11:06 Felipe Balbi
2018-03-05 11:06 ` [PATCH] " Felipe Balbi
2018-03-05 11:03 Roger Quadros
2018-03-05 11:03 ` [PATCH] " Roger Quadros
2018-03-05 10:41 Baolin Wang
2018-03-05 10:41 ` [PATCH] " Baolin Wang
2018-03-05 9:45 Roger Quadros
2018-03-05 9:45 ` [PATCH] " Roger Quadros
2018-03-05 8:49 Felipe Balbi
2018-03-05 8:49 ` [PATCH] " Felipe Balbi
2018-02-28 9:59 Roger Quadros
2018-02-28 9:59 ` [PATCH] " Roger Quadros
2018-02-28 9:55 Roger Quadros
2018-02-28 9:55 ` [PATCH] " Roger Quadros
2018-02-28 7:53 Felipe Balbi
2018-02-28 7:53 ` [PATCH] " Felipe Balbi
2018-02-28 3:04 Baolin Wang
2018-02-28 3:04 ` [PATCH] " Baolin Wang
2018-02-27 11:22 Roger Quadros
2018-02-27 11:22 ` [PATCH] " Roger Quadros
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=87r2nnldq6.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.