From: Greg KH <gregkh@linuxfoundation.org>
To: Kuangyi Chiang <ki.chiang65@gmail.com>
Cc: mathias.nyman@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] xhci: Don't issue Reset Device command to Etron xHCI host
Date: Wed, 19 Jun 2024 08:14:57 +0200 [thread overview]
Message-ID: <2024061903-shadow-pesky-1205@gregkh> (raw)
In-Reply-To: <20240619054808.12861-1-ki.chiang65@gmail.com>
On Wed, Jun 19, 2024 at 01:48:08PM +0800, Kuangyi Chiang wrote:
> Sometimes the hub driver does not recognize the USB device connected
> to the external USB2.0 hub when the system resumes from S4.
>
> This happens when the xHCI driver issue the Reset Device command to
> inform the Etron xHCI host that the USB device has been reset.
>
> Seems that the Etron xHCI host can not perform this command correctly,
> affecting the USB device.
>
> Instead, to avoid this, disabling slot ID and then enabling slot ID
> is a workable solution to replace the Reset Device command.
>
> An easy way to issue these commands in sequence is to call
> xhci_free_dev() and then xhci_alloc_dev().
>
> Applying this patch then the issue is gone.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Kuangyi Chiang <ki.chiang65@gmail.com>
What commit id does this fix?
> ---
> Changes in v2:
> - Change commit log
> - Add a comment for the workaround
> - Revert "global xhci_free_dev()"
> - Remove XHCI_ETRON_HOST quirk bit
>
> drivers/usb/host/xhci.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index 37eb37b0affa..c892750a89c5 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -3682,6 +3682,8 @@ void xhci_free_device_endpoint_resources(struct xhci_hcd *xhci,
> xhci->num_active_eps);
> }
>
> +static void xhci_free_dev(struct usb_hcd *hcd, struct usb_device *udev);
> +
> /*
> * This submits a Reset Device Command, which will set the device state to 0,
> * set the device address to 0, and disable all the endpoints except the default
> @@ -3752,6 +3754,20 @@ static int xhci_discover_or_reset_device(struct usb_hcd *hcd,
> SLOT_STATE_DISABLED)
> return 0;
>
> + if (dev_is_pci(hcd->self.controller) &&
> + to_pci_dev(hcd->self.controller)->vendor == 0x1b6f) {
Odd indentation :(
Also, that's a specific value, shouldn't it be in a #define somewhere?
> + /*
> + * Disabling and then enabling device slot ID to inform xHCI
> + * host that the USB device has been reset.
> + */
> + xhci_free_dev(hcd, udev);
> + ret = xhci_alloc_dev(hcd, udev);
You are relying on the behavior of free/alloc here to disable/enable the
slot id, why not just do that instead? What happens if the free/alloc
call stops doing that? This feels very fragile to me.
> + if (ret == 1)
> + return 0;
> + else
> + return -EINVAL;
Why -EINVAL? What value was wrong?
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-19 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 5:48 [PATCH v2] xhci: Don't issue Reset Device command to Etron xHCI host Kuangyi Chiang
2024-06-19 6:14 ` Greg KH [this message]
2024-06-23 4:39 ` Kuangyi Chiang
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=2024061903-shadow-pesky-1205@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ki.chiang65@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stable@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