public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	imx@lists.linux.dev, jun.li@nxp.com
Subject: Re: [PATCH v2 2/3] usb: chipidea: udc: limit usb request length to max 16KB
Date: Wed, 25 Sep 2024 20:47:06 +0800	[thread overview]
Message-ID: <20240925124706.GE417263@nchen-desktop> (raw)
In-Reply-To: <20240923081203.2851768-2-xu.yang_2@nxp.com>

On 24-09-23 16:12:02, Xu Yang wrote:
> To let the device controller work properly on short packet limitations,
> one usb request should only correspond to one dTD. Then every dTD will
> set IOC. In theory, each dTD support up to 20KB data transfer if the
> offset is 0. Due to we cannot predetermine the offset, this will limit
> the usb request length to max 16KB. This should be fine since most of
> the user transfer data based on this size policy.
> 
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>

Acked-by: Peter Chen <peter.chen@kernel.org>
> 
> ---
> Changes in v2:
>  - limit request length only when ci->has_short_pkt_limit set
>  - modify commit message
> ---
>  drivers/usb/chipidea/ci.h  | 1 +
>  drivers/usb/chipidea/udc.c | 6 ++++++
>  2 files changed, 7 insertions(+)
> 
> diff --git a/drivers/usb/chipidea/ci.h b/drivers/usb/chipidea/ci.h
> index e4b003d060c2..97437de52ef6 100644
> --- a/drivers/usb/chipidea/ci.h
> +++ b/drivers/usb/chipidea/ci.h
> @@ -25,6 +25,7 @@
>  #define TD_PAGE_COUNT      5
>  #define CI_HDRC_PAGE_SIZE  4096ul /* page size for TD's */
>  #define ENDPT_MAX          32
> +#define CI_MAX_REQ_SIZE	(4 * CI_HDRC_PAGE_SIZE)
>  #define CI_MAX_BUF_SIZE	(TD_PAGE_COUNT * CI_HDRC_PAGE_SIZE)
>  
>  /******************************************************************************
> diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
> index 18c1882cf088..5badb39cb2bf 100644
> --- a/drivers/usb/chipidea/udc.c
> +++ b/drivers/usb/chipidea/udc.c
> @@ -972,6 +972,12 @@ static int _ep_queue(struct usb_ep *ep, struct usb_request *req,
>  		return -EMSGSIZE;
>  	}
>  
> +	if (ci->has_short_pkt_limit &&
> +		hwreq->req.length > CI_MAX_REQ_SIZE) {
> +		dev_err(hwep->ci->dev, "request length too big (max 16KB)\n");
> +		return -EMSGSIZE;
> +	}
> +
>  	/* first nuke then test link, e.g. previous status has not sent */
>  	if (!list_empty(&hwreq->queue)) {
>  		dev_err(hwep->ci->dev, "request already in queue\n");
> -- 
> 2.34.1
> 

  reply	other threads:[~2024-09-25 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23  8:12 [PATCH v2 1/3] usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag Xu Yang
2024-09-23  8:12 ` [PATCH v2 2/3] usb: chipidea: udc: limit usb request length to max 16KB Xu Yang
2024-09-25 12:47   ` Peter Chen [this message]
2024-09-23  8:12 ` [PATCH v2 3/3] usb: chipidea: udc: create bounce buffer for problem sglist entries if possible Xu Yang
2024-10-08 20:27   ` Kees Bakker
2024-10-09  1:49     ` Xu Yang
2024-09-25 12:46 ` [PATCH v2 1/3] usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag Peter Chen

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=20240925124706.GE417263@nchen-desktop \
    --to=peter.chen@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=jun.li@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=xu.yang_2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox