From: Mathias Nyman <mathias.nyman@linux.intel.com>
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, s.shtylyov@omp.ru
Subject: Re: [PATCH v7 1/2] usb: xhci: Add timeout argument in address_device USB HCD callback
Date: Mon, 30 Oct 2023 12:45:54 +0200 [thread overview]
Message-ID: <aa328f6d-be12-45ef-42dd-2b4dc0821771@linux.intel.com> (raw)
In-Reply-To: <20231027152029.104363-1-hgajjar@de.adit-jv.com>
On 27.10.2023 18.20, Hardik Gajjar wrote:
> - The HCD address_device callback now accepts a user-defined timeout value
> in milliseconds, providing better control over command execution times.
> - The default timeout value for the address_device command has been set
> to 5000 ms, aligning with the USB 3.2 specification. However, this
> timeout can be adjusted as needed.
> - The xhci_setup_device function has been updated to accept the timeout
> value, allowing it to specify the maximum wait time for the command
> operation to complete.
> - The hub driver has also been updated to accommodate the newly added
> timeout parameter during the SET_ADDRESS request.
>
> Signed-off-by: Hardik Gajjar <hgajjar@de.adit-jv.com>
For the xhci parts
Reviewed-by: Mathias Nyman <mathias.nyman@linux.intel.com>
next parent reply other threads:[~2023-10-30 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231027152029.104363-1-hgajjar@de.adit-jv.com>
2023-10-30 10:45 ` Mathias Nyman [this message]
2023-11-03 15:18 ` [PATCH v7 1/2] usb: xhci: Add timeout argument in address_device USB HCD callback Hardik Gajjar
2023-11-03 15:26 ` Greg KH
2023-11-03 15:27 ` Greg KH
[not found] ` <20231027152029.104363-2-hgajjar@de.adit-jv.com>
[not found] ` <7cbc1a70-2dcc-4a2a-99e6-fdd92bd5cc9b@rowland.harvard.edu>
2023-11-03 15:15 ` [PATCH v7 2/2] usb: new quirk to reduce the SET_ADDRESS request timeout Hardik Gajjar
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=aa328f6d-be12-45ef-42dd-2b4dc0821771@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--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=s.shtylyov@omp.ru \
--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