From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Hardik Gajjar <hgajjar@de.adit-jv.com>,
<gregkh@linuxfoundation.org>, <stern@rowland.harvard.edu>,
<mathias.nyman@intel.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<erosca@de.adit-jv.com>
Subject: Re: [PATCH v6] usb: Reduce the 'SET_ADDRESS' request timeout with a new quirk
Date: Thu, 26 Oct 2023 19:00:56 +0300 [thread overview]
Message-ID: <cd598ae5-6eae-8e0b-8295-d98fa5c4b2fd@omp.ru> (raw)
In-Reply-To: <20231026101551.36551-1-hgajjar@de.adit-jv.com>
Hello!
Please don't post the patches as a reply to the other thread, start a new
thread with a new patch version (I thought others would tell you that but nobody
has so far).
And how about changing the wording of the subject to s/th like below?
usb: new quirk to reduce the SET_ADDRESS request timeout
On 10/26/23 1:15 PM, Hardik Gajjar wrote:
> This patch introduces a new USB quirk,
> USB_QUIRK_SHORT_SET_ADDRESS_REQ_TIMEOUT, which modifies the timeout value
> for the 'SET_ADDRESS' request. The standard timeout for USB request/command
The upper case is enough of the emphasis, I don't think the apostrophes
are needed arounnd SET_ADDRESS...
[...]
> Signed-off-by: Hardik Gajjar <hgajjar@de.adit-jv.com>
> ---
[...]
> Changes since version 5:
> - Changed the terminology in USB core driver files from 'command' to 'request'
> as it is more commonly used.
> It's important to note that USB specifications indicate these terms are interchangeable.
Didn't know that... tried to find the proof in the USB specs but haven't
managed to do it...
> For example, USB spec 3.2, section 9.2.6.1, uses the term 'command' in its text
> "USB sets an upper limit of 5 seconds for any command to be processed. "
Hm, indeed; and this wording is even inherited from USB 1.1...
[...]
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index 3c54b218301c..98db92af2cce 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -54,6 +54,19 @@
> #define USB_TP_TRANSMISSION_DELAY_MAX 65535 /* ns */
> #define USB_PING_RESPONSE_TIME 400 /* ns */
>
> +/*
> + * USB 3.2 spec, section 9.2.6.1
> + * USB sets an upper limit of 5000 ms for any command/request
> + * to be processed.
> + */
> +#define USB_DEFAULT_REQUEST_TIMEOUT_MS 5000 /* ms */
> +
> +/*
> + * The SET_ADDRESS request timeout will be 500 ms when
> + * USB_QUIRK_SHORT_SET_ADDRESS_REQ_TIMEOUT enable.
> + */
> +#define USB_SHORT_SET_ADDRESS_REQ_TIMEOUT_MS 500 /* ms */
I don'ts see the _MS-like suffixes in the other timeout #define's there...
[...]
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index e1b1b64a0723..d856c4717ca9 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -3997,12 +3997,18 @@ int xhci_alloc_dev(struct usb_hcd *hcd, struct usb_device *udev)
> return 0;
> }
>
> -/*
> - * Issue an Address Device command and optionally send a corresponding
> - * SetAddress request to the device.
> +/**
> + * xhci_setup_device - issues an Address Device command to assign a unique
> + * USB bus address.
> + * @hcd: USB host controller data structure.
> + * @udev: USB dev structure representing the connected device.
> + * @setup: Enum specifying setup mode: address only or with context.
> + * @timeout_ms: Max wait time (ms) for the command operation to complete.
> + *
> + * Return: 0 if successful; otherwise, negative error code.
I still think the above change should be a separate follow-up (or even
a preceding) patch...
[...]
MBR, Sergey
next prev parent reply other threads:[~2023-10-26 16:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <--in-reply-to=20231006153808.9758-1-hgajjar@de.adit-jv.com>
2023-10-09 16:14 ` [PATCH v2] usb: core: hub: Add quirks for reducing device address timeout Hardik Gajjar
2023-10-09 17:43 ` Greg KH
2023-10-10 10:31 ` Hardik Gajjar
2023-10-10 11:25 ` Greg KH
2023-10-09 19:16 ` Alan Stern
2023-10-10 10:50 ` Hardik Gajjar
2023-10-10 13:40 ` Mathias Nyman
2023-10-11 8:50 ` [PATCH v3] " Hardik Gajjar
2023-10-11 9:02 ` Greg KH
2023-10-11 12:05 ` Hardik Gajjar
2023-10-11 15:23 ` Greg KH
2023-10-11 16:45 ` [PATCH v4] " Hardik Gajjar
2023-10-16 17:58 ` Greg KH
2023-10-17 16:10 ` Hardik Gajjar
2023-10-17 16:53 ` Greg KH
2023-10-17 18:59 ` Alan Stern
2023-10-21 10:15 ` Greg KH
2023-10-23 16:13 ` Hardik Gajjar
2023-10-24 15:44 ` Alan Stern
2023-10-25 14:11 ` [PATCH v5] usb: Reduce 'set_address' command timeout with a new quirk Hardik Gajjar
2023-10-25 14:13 ` Hardik Gajjar
2023-10-25 14:44 ` Alan Stern
2023-10-25 16:00 ` Sergey Shtylyov
2023-10-25 16:16 ` Sergey Shtylyov
2023-10-25 16:16 ` Sergey Shtylyov
2023-10-25 16:40 ` Hardik Gajjar
2023-10-26 10:15 ` [PATCH v6] usb: Reduce the 'SET_ADDRESS' request " Hardik Gajjar
2023-10-26 13:08 ` Mathias Nyman
2023-10-26 16:00 ` Sergey Shtylyov [this message]
2023-10-26 18:34 ` Alan Stern
2023-10-27 9:57 ` Hardik Gajjar
2023-10-11 10:50 ` [PATCH v3] usb: core: hub: Add quirks for reducing device address timeout kernel test robot
2023-10-11 14:15 ` Alan Stern
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=cd598ae5-6eae-8e0b-8295-d98fa5c4b2fd@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=erosca@de.adit-jv.com \
--cc=gregkh@linuxfoundation.org \
--cc=hgajjar@de.adit-jv.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stern@rowland.harvard.edu \
/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®