From: Felipe Balbi <balbi@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>, linux-usb@vger.kernel.org
Cc: John Youn <John.Youn@synopsys.com>
Subject: [3/3] usb: dwc3: gadget: Return correct actual bytes written
Date: Mon, 30 Jul 2018 09:07:48 +0300 [thread overview]
Message-ID: <87d0v5xnm3.fsf@linux.intel.com> (raw)
Hi,
Thinh Nguyen <Thinh.Nguyen@synopsys.com> writes:
> For OUT transfers, the total size (total TRB buffer allocation) must be
> a multiple of MaxPacketSize even if software is expecting a fixed
> non-multiple of MaxPacketSize transfer from the host.
this is the same for dwc3.0 and we already account for that.
> (DWC_usb31 programming guide section 4.2.5)
>
> So, to calculate the actual bytes written (OUT transfer), do:
> actual = round_up(expected_length, MaxPacketSize) - remaining_length
>
> Fixes: e62c5bc57367 ("usb: dwc3: gadget: tracking per-TRB remaining bytes")
> Signed-off-by: Thinh Nguyen <thinhn@synopsys.com>
> ---
> drivers/usb/dwc3/gadget.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> index a5b8387a37ba..9859ca9dff9a 100644
> --- a/drivers/usb/dwc3/gadget.c
> +++ b/drivers/usb/dwc3/gadget.c
> @@ -2319,6 +2319,8 @@ static int dwc3_gadget_ep_cleanup_completed_request(struct dwc3_ep *dep,
> const struct dwc3_event_depevt *event,
> struct dwc3_request *req, int status)
> {
> + unsigned int maxp = usb_endpoint_maxp(dep->endpoint.desc);
> + unsigned int length = req->request.length;
> int ret;
>
> if (req->num_pending_sgs)
> @@ -2335,7 +2337,10 @@ static int dwc3_gadget_ep_cleanup_completed_request(struct dwc3_ep *dep,
> req->zero = false;
> }
>
> - req->request.actual = req->request.length - req->remaining;
> + if (usb_endpoint_dir_out(dep->endpoint.desc))
dep->direction
> + req->request.actual = round_up(length, maxp) - req->remaining;
> + else
> + req->request.actual = length - req->remaining;
this is completely unnecessary. What actual problem are you facing? Care
to share some tracepoint data exposing the issue? How do you reproduce
it? We added the chained TRB at the end to make dwc3 happy, why isn't
that working for dwc31?
next reply other threads:[~2018-07-30 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 6:07 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-28 1:52 [3/3] usb: dwc3: gadget: Return correct actual bytes written 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=87d0v5xnm3.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=John.Youn@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).