From: Prashanth K <prashanth.k@oss.qualcomm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Kees Bakker <kees@ijzerbout.nl>,
William McVicker <willmcvicker@google.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Prashanth K <prashanth.k@oss.qualcomm.com>
Subject: [PATCH v2 0/3] Fixes for USB3 CV Chapter 9.15 tests
Date: Tue, 22 Apr 2025 16:02:28 +0530 [thread overview]
Message-ID: <20250422103231.1954387-1-prashanth.k@oss.qualcomm.com> (raw)
While performing USB3 Command Verifier Chapter 9 tests, failures
were observed during 9.15 ("Function Remote Wakeup Enabled Test").
This is due to the following reasons,
1. Interfaces were incorrectly reporting as remote wakeup capable
when host requested GET_STATUS.
2. Remote wakeup failures from DWC3 driver due to timeouts.
Address them through this series.
Changes in v2:
- Don't advertise func wakeup capability if USB_CONFIG_ATT_WAKEUP
is not set in bmAttributes.
- Refactored func wakeup logic in linksts_change_interrupt().
Prashanth K (3):
usb: gadget: f_ecm: Add get_status callback
usb: gadget: Use get_status callback to set remote wakeup capability
usb: dwc3: gadget: Make gadget_wakeup asynchronous
drivers/usb/dwc3/core.h | 4 ++
drivers/usb/dwc3/gadget.c | 60 +++++++++++------------------
drivers/usb/gadget/composite.c | 12 +++---
drivers/usb/gadget/function/f_ecm.c | 7 ++++
4 files changed, 39 insertions(+), 44 deletions(-)
--
2.25.1
next reply other threads:[~2025-04-22 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 10:32 Prashanth K [this message]
2025-04-22 10:32 ` [PATCH v2 1/3] usb: gadget: f_ecm: Add get_status callback Prashanth K
2025-04-22 22:13 ` Thinh Nguyen
2025-04-22 10:32 ` [PATCH v2 2/3] usb: gadget: Use get_status callback to set remote wakeup capability Prashanth K
2025-04-22 22:15 ` Thinh Nguyen
2025-04-22 10:32 ` [PATCH v2 3/3] usb: dwc3: gadget: Make gadget_wakeup asynchronous Prashanth K
2025-04-22 22:11 ` Thinh Nguyen
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=20250422103231.1954387-1-prashanth.k@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=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