All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Xiong <wenxiong@linux.ibm.com>
To: Michal Pecio <michal.pecio@gmail.com>
Cc: mathias.nyman@intel.com, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, wenxiong@us.ibm.com,
	Brian King <brking@linux.vnet.ibm.com>,
	Samuel Mendoza-Jonas <sam@mendozajonas.com>,
	Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] xhci: Reset controller on xhci shutdown
Date: Wed, 21 Oct 2026 09:44:20 -0500	[thread overview]
Message-ID: <1850c5305615a1f4edfe213bcb599ff0@linux.ibm.com> (raw)
In-Reply-To: <20261021112705.19fd90b8.michal.pecio@gmail.com>


> In such case your suggestion to PCI reset may be the simplest way out.
> It seems we could either call it always on TI chips, or automatically
> as a fallback when xhci_shutdown() fails to halt the xHC.
> 
> Mathias, any preferences?
> 
(1)my V2: call it always on TI chips in quirks path in 
xhci_pci_shutdown.

(2)Maybe try: call it on TI chips in quirks path in xhci_shutdown when 
failing to halt the xHCI.

Mathias, if you think V2 isn’t good enough, I can regenerate the above 
(2)option as V3.

Thanks,
Wendy





      reply	other threads:[~2026-10-21 14:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 22:25 [PATCH] xhci: Reset controller on xhci shutdown wenxiong
2026-10-01 22:40 ` Mathias Nyman
2026-10-02 14:08   ` Wen Xiong
2026-10-02  8:29 ` Michal Pecio
2026-10-02 14:05   ` Wen Xiong
2026-10-02 14:18     ` Michal Pecio
2026-10-05 13:01       ` Wen Xiong
2026-10-06 10:55         ` Michal Pecio
2026-10-14 20:32           ` Wen Xiong
2026-10-15  8:33             ` Michal Pecio
2026-10-20 20:40               ` Wen Xiong
2026-10-21  9:27                 ` Michal Pecio
2026-10-21 14:44                   ` Wen Xiong [this message]

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=1850c5305615a1f4edfe213bcb599ff0@linux.ibm.com \
    --to=wenxiong@linux.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=michal.pecio@gmail.com \
    --cc=sam@mendozajonas.com \
    --cc=stable@vger.kernel.org \
    --cc=wenxiong@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.