From: William Wu <william.wu@rock-chips.com>
To: gregkh@linuxfoundation.org, stern@rowland.harvard.edu
Cc: Chris.Wulff@biamp.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, william.wu@rock-chips.com,
frank.wang@rock-chips.com, jianwei.zheng@rock-chips.com,
yue.long@rock-chips.com
Subject: [PATCH v2] usb: gadget: f_hid: Fix zero length packet transfer
Date: Tue, 26 Aug 2025 18:28:07 +0800 [thread overview]
Message-ID: <1756204087-26111-1-git-send-email-william.wu@rock-chips.com> (raw)
Set the hid req->zero flag of ep0/in_ep to true by default,
then the UDC drivers can transfer a zero length packet at
the end if the hid transfer with size divisible to EPs max
packet size according to the USB 2.0 spec.
Signed-off-by: William Wu <william.wu@rock-chips.com>
---
Changelog:
v2:
- set req->zero to 1 instead of check whether the length is divisible by the maxpacket
---
drivers/usb/gadget/function/f_hid.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/function/f_hid.c b/drivers/usb/gadget/function/f_hid.c
index 8e1d1e8..307ea56 100644
--- a/drivers/usb/gadget/function/f_hid.c
+++ b/drivers/usb/gadget/function/f_hid.c
@@ -511,7 +511,7 @@ static ssize_t f_hidg_write(struct file *file, const char __user *buffer,
}
req->status = 0;
- req->zero = 0;
+ req->zero = 1;
req->length = count;
req->complete = f_hidg_req_complete;
req->context = hidg;
@@ -967,7 +967,7 @@ static int hidg_setup(struct usb_function *f,
return -EOPNOTSUPP;
respond:
- req->zero = 0;
+ req->zero = 1;
req->length = length;
status = usb_ep_queue(cdev->gadget->ep0, req, GFP_ATOMIC);
if (status < 0)
--
2.0.0
next reply other threads:[~2025-08-26 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 10:28 William Wu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-25 4:14 William Wu
2025-08-25 7:09 ` Greg KH
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=1756204087-26111-1-git-send-email-william.wu@rock-chips.com \
--to=william.wu@rock-chips.com \
--cc=Chris.Wulff@biamp.com \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=jianwei.zheng@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=yue.long@rock-chips.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
all inboxes | Powered by JetHome®