diff options
| author | Wesley Cheng <quic_wcheng@quicinc.com> | 2023-05-31 15:27:18 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-06-23 09:55:09 +0200 |
| commit | fb2ce17874cf3c3c183e5fd75144ffbe2313bf31 (patch) | |
| tree | 70e89dc2fee4e4c3fc7b7e4d3eeaca5116222a21 /drivers/nvdimm | |
| parent | 256a02e2caa3c606b84a40e8035e240beb93e67b (diff) | |
| download | linux-fb2ce17874cf3c3c183e5fd75144ffbe2313bf31.tar.gz linux-fb2ce17874cf3c3c183e5fd75144ffbe2313bf31.tar.bz2 linux-fb2ce17874cf3c3c183e5fd75144ffbe2313bf31.zip | |
usb: host: xhci: Do not re-initialize the XHCI HC if being removed
During XHCI resume, if there was a host controller error detected the
routine will attempt to re-initialize the XHCI HC, so that it can return
back to an operational state. If the XHCI host controller is being
removed, this sequence would be already handled within the XHCI halt path,
leading to a duplicate set of reg ops/calls. In addition, since the XHCI
bus is being removed, the overhead added in restarting the HCD is
unnecessary. Check for the XHC state before setting the reinit_xhc
parameter, which is responsible for triggering the restart.
Signed-off-by: Wesley Cheng <quic_wcheng@quicinc.com>
Message-ID: <20230531222719.14143-2-quic_wcheng@quicinc.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/nvdimm')
0 files changed, 0 insertions, 0 deletions