From: Alan Stern <stern@rowland.harvard.edu>
To: Ray Chi <raychi@google.com>
Cc: gregkh@linuxfoundation.org, mathias.nyman@intel.com,
badhri@google.com, albertccwang@google.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] usb: core: add a hook to check port init status
Date: Tue, 16 Aug 2022 09:53:53 -0400 [thread overview]
Message-ID: <YvuhcUx9R8Rdyfr4@rowland.harvard.edu> (raw)
In-Reply-To: <20220816083854.1491886-2-raychi@google.com>
On Tue, Aug 16, 2022 at 04:38:53PM +0800, Ray Chi wrote:
> This patch add a hook to check the port init status. Currently, only
> usbcore knows port init status even if the result is bad. It will cause
> a USB host keep doing USB enumeration for a long time when the USB host
> connects to a broken USB accessory.
>
> The hc_driver could use the hook to know port init status and do possible
> error handling according to platform requirements or limitations.
>
> Signed-off-by: Ray Chi <raychi@google.com>
> ---
> drivers/usb/core/hub.c | 14 ++++++++++++++
> include/linux/usb/hcd.h | 8 ++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index 2633acde7ac1..6ce6092816cb 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -4855,6 +4865,10 @@ hub_port_init(struct usb_hub *hub, struct usb_device *udev, int port1,
> buf->bMaxPacketSize0;
> kfree(buf);
>
> + retval = hub_port_check_init_status(udev, r);
> + if (retval < 0)
> + goto fail;
For future reference, you should be aware that this code won't get
executed if do_new_scheme is false.
Alan Stern
next prev parent reply other threads:[~2022-08-16 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:38 [PATCH 0/2] Provide " Ray Chi
2022-08-16 8:38 ` [PATCH 1/2] usb: core: add " Ray Chi
2022-08-16 13:53 ` Alan Stern [this message]
2022-08-16 8:38 ` [PATCH 2/2] usb: xhci: add check_init_status hook support Ray Chi
2022-08-16 8:57 ` Greg KH
2022-08-22 15:42 ` Ray Chi
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=YvuhcUx9R8Rdyfr4@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=albertccwang@google.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=raychi@google.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®