From: Ye Li <ye.li@nxp.com>
To: lukma@denx.de, mkorpershoek@kernel.org, u-boot@lists.denx.de
Cc: festevam@gmail.com, peng.fan@nxp.com, uboot-imx@nxp.com,
ye.li@oss.nxp.com, xu.yang_2@nxp.com, jason.he_1@nxp.com
Subject: [PATCH 2/3] usb: ci_udc: Update usb request status
Date: Fri, 22 May 2026 15:55:11 +0800 [thread overview]
Message-ID: <20260522075512.1291485-2-ye.li@nxp.com> (raw)
In-Reply-To: <20260522075512.1291485-1-ye.li@nxp.com>
usb request status is not set in ci_udc driver. However
in ci_ep_dequeue, it checks the request status for executing
complete callback, so upper layer is not able to free these
enqueued requests when calling usb_ep_dequeue.
Signed-off-by: Ye Li <ye.li@nxp.com>
---
drivers/usb/gadget/ci_udc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/gadget/ci_udc.c b/drivers/usb/gadget/ci_udc.c
index a62e5ea5658..0baad83ef90 100644
--- a/drivers/usb/gadget/ci_udc.c
+++ b/drivers/usb/gadget/ci_udc.c
@@ -680,6 +680,8 @@ static int ci_ep_queue(struct usb_ep *ep,
if (ret)
return ret;
+ req->status = -EINPROGRESS;
+
DBG("ept%d %s pre-queue req %p, buffer %p\n",
num, in ? "in" : "out", ci_req, ci_req->hw_buf);
list_add_tail(&ci_req->queue, &ci_ep->queue);
@@ -754,6 +756,7 @@ static void handle_ep_complete(struct ci_ep *ci_ep)
ci_ep_submit_next_request(ci_ep);
ci_req->req.actual = ci_req->req.length - len;
+ ci_req->req.status = 0;
ci_debounce(ci_req, in);
DBG("ept%d %s req %p, complete %x\n",
--
2.37.1
next prev parent reply other threads:[~2026-05-22 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 7:55 [PATCH 1/3] usb: ci_udc: set correct ep type in ep_enable() Ye Li
2026-05-22 7:55 ` Ye Li [this message]
2026-06-16 9:15 ` [PATCH 2/3] usb: ci_udc: Update usb request status Mattijs Korpershoek
2026-05-22 7:55 ` [PATCH 3/3] usb: ci_udc: verify all dtds are inactive before completing request Ye Li
2026-06-16 9:30 ` Mattijs Korpershoek
2026-06-16 9:05 ` [PATCH 1/3] usb: ci_udc: set correct ep type in ep_enable() Mattijs Korpershoek
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=20260522075512.1291485-2-ye.li@nxp.com \
--to=ye.li@nxp.com \
--cc=festevam@gmail.com \
--cc=jason.he_1@nxp.com \
--cc=lukma@denx.de \
--cc=mkorpershoek@kernel.org \
--cc=peng.fan@nxp.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=xu.yang_2@nxp.com \
--cc=ye.li@oss.nxp.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 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.