From: Prashanth K <prashanth.k@oss.qualcomm.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Bakker <kees@ijzerbout.nl>,
William McVicker <willmcvicker@google.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH v1 3/3] usb: dwc3: gadget: Make gadget_wakeup asynchronous
Date: Thu, 10 Apr 2025 11:18:22 +0530 [thread overview]
Message-ID: <bbe1af12-3aaf-4382-b8c8-5d645ea9d906@oss.qualcomm.com> (raw)
In-Reply-To: <20250409215151.thkmgzyeohyxhslh@synopsys.com>
On 10-04-25 03:21 am, Thinh Nguyen wrote:
> On Wed, Apr 09, 2025, Prashanth K wrote:
>>
>>
>> On 09-04-25 06:13 am, Thinh Nguyen wrote:
>>> On Tue, Apr 08, 2025, Prashanth K wrote:
>>>>
>>>>
>>>> On 08-04-25 05:08 am, Thinh Nguyen wrote:
>>>>> On Thu, Apr 03, 2025, Prashanth K wrote:
>>>
>>>>>> @@ -4398,6 +4371,21 @@ static void dwc3_gadget_linksts_change_interrupt(struct dwc3 *dwc,
>>>>>> }
>>>>>>
>>>>>> dwc->link_state = next;
>>>>>> +
>>>>>> + /* Proceed with func wakeup if any interfaces that has requested */
>>>>>> + while (dwc->func_wakeup_pending && (next == DWC3_LINK_STATE_U0)) {
>>>>>> + if (dwc->func_wakeup_pending & BIT(0)) {
>>>>>> + ret = dwc3_send_gadget_generic_command(dwc, DWC3_DGCMD_DEV_NOTIFICATION,
>>>>>> + DWC3_DGCMDPAR_DN_FUNC_WAKE |
>>>>>> + DWC3_DGCMDPAR_INTF_SEL(intf_id));
>>>>>> + if (ret)
>>>>>> + dev_err(dwc->dev, "function remote wakeup failed for %d, ret:%d\n",
>>>>>> + intf_id, ret);
>>>>>> + }
>>>>>> + dwc->func_wakeup_pending >>= 1;
>>>>>
>>>>> This would break the bitmap of dwc->func_wakeup_pending. Perhaps we can
>>>>> use ffs(x) to properly find and clear the interface ID from the bitmap
>>>>> one at a time.
>>>>>
>>>> Yes, we can use ffs(x). But I didn't understand how this would break
>>>> bitmap of dwc->func_wakeup_pending.
>>>>
>>>
>>> Since you're sending device notification to all the wakeup armed
>>> interfaces and not reusing the func_wakeup_pending afterward, the result
>>> of what you're doing here will be the same.
>>>
>>> IMHO, for clarity, what I was suggesting is to revise the logic to
>>> preserve the dwc->func_wakeup_pending bitmap instead of shifting and
>>> overwriting it, causing the bitmap to no longer match the intf_id. We
>>> get the intf_id from the bitmap and clear the intf_id bit from the
>>> bitmap as we go.
>>>
>> The above logic works, but as you suggested I'll refactor it using
>> ffs(x) and clear the intf_id directly (instead of shifting).
>>
>> Does this look good?
>
> It looks great!
>
>>
>> /* Proceed with func wakeup if any interfaces that has requested */
>> while (dwc->func_wakeup_pending && (next == DWC3_LINK_STATE_U0)) {
>> intf_id = ffs(dwc->func_wakeup_pending);
>> if (intf_id)
>> ret = dwc3_send_gadget_generic_command(dwc, DWC3_DGCMD_DEV_NOTIFICATION,
>> DWC3_DGCMDPAR_DN_FUNC_WAKE |
>> DWC3_DGCMDPAR_INTF_SEL(intf_id - 1));
>> if (ret)
>> dev_err(dwc->dev, "function remote wakeup failed for %d, ret:%d\n",
>> intf_id, ret);
>> }
>> dwc->func_wakeup_pending &= ~(1 << (intf_id - 1));
>
>
> Some minor revision. How does this look? (not tested)
>
> while (dwc->func_wakeup_pending && (next == DWC3_LINK_STATE_U0)) {
> intf_id = ffs(dwc->func_wakeup_pending) - 1;
> ret = dwc3_send_gadget_generic_command(dwc, DWC3_DGCMD_DEV_NOTIFICATION,
> DWC3_DGCMDPAR_DN_FUNC_WAKE |
> DWC3_DGCMDPAR_INTF_SEL(intf_id));
> if (ret)
> dev_err(dwc->dev, "Failed to send DN wake for intf %d\n", intf_id);
>
> dwc->func_wakeup_pending &= ~BIT(intf_id);
> }
>
> Thanks,
> Thinh
Good suggestion, ideally it should work, I'll test and add it in v2.
Thanks,
Prashanth K
prev parent reply other threads:[~2025-04-10 5:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 11:08 [PATCH v1 0/3] Fixes for USB3 CV Chapter 9.15 tests Prashanth K
2025-04-03 11:08 ` [PATCH v1 1/3] usb: gadget: f_ecm: Add get_status callback Prashanth K
2025-04-08 1:08 ` Thinh Nguyen
2025-04-08 5:05 ` Prashanth K
2025-04-09 0:56 ` Thinh Nguyen
2025-04-03 11:08 ` [PATCH v1 2/3] usb: gadget: Use get_status callback to set remote wakeup capability Prashanth K
2025-04-08 1:18 ` Thinh Nguyen
2025-04-08 5:06 ` Prashanth K
2025-04-09 0:55 ` Thinh Nguyen
2025-04-09 4:22 ` Prashanth K
2025-04-09 22:05 ` Thinh Nguyen
2025-04-09 22:12 ` Thinh Nguyen
2025-04-10 6:08 ` Prashanth K
2025-04-11 1:00 ` Thinh Nguyen
2025-04-03 11:08 ` [PATCH v1 3/3] usb: dwc3: gadget: Make gadget_wakeup asynchronous Prashanth K
2025-04-07 23:38 ` Thinh Nguyen
2025-04-08 5:34 ` Prashanth K
2025-04-09 0:43 ` Thinh Nguyen
2025-04-09 4:15 ` Prashanth K
2025-04-09 21:51 ` Thinh Nguyen
2025-04-10 5:48 ` Prashanth K [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=bbe1af12-3aaf-4382-b8c8-5d645ea9d906@oss.qualcomm.com \
--to=prashanth.k@oss.qualcomm.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=kees@ijzerbout.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=stable@kernel.org \
--cc=willmcvicker@google.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