Linux USB
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Jie Deng <dengjie03@kylinos.cn>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
	mathias.nyman@intel.com, linux-usb@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: Restore MSI/MSI-X reinitialization on resume for RESET_ON_RESUME hosts
Date: Fri, 31 Jul 2026 12:57:37 +0200	[thread overview]
Message-ID: <20260731125737.073cedb3.michal.pecio@gmail.com> (raw)
In-Reply-To: <d71b1b08-eae8-4e0a-a58f-bbd6b131d5cd@kylinos.cn>

On Fri, 31 Jul 2026 15:38:22 +0800, Jie Deng wrote:
> The S3 test script is as follows:
> #! /bin/bash
> #
> for i in $(seq 1 $1); do
>      echo "the $i th s3" > /dev/ttyAMA0
>      echo "the $i th s3"
>      rtcwake -m mem -s 20
>      sleep 15
> done

That's simple enough, I could run it for a few hours on x86 PC with
a few different PCIe xHCI cards.

Just in case, are some USB devices supposed to be connected, or not
connected, or maybe it's known to make no difference?

You mentioned that the problem occurs both in D3cold and D3hot, on
my system I'm not sure if D3hot is possible with S3 so I would end
up with D3cold or use s2idle instead of S3.

I recall that in D3cold most of my PCIe cards don't supply AUX power
to the xHCI. Was AUX power supplied to these chips in your tests?
If so, I may be forced to use s2idle. Or maybe will just try both.

Regards,
Michal

      reply	other threads:[~2026-07-31 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  9:02 [PATCH] usb: xhci: Restore MSI/MSI-X reinitialization on resume for RESET_ON_RESUME hosts Jie Deng
2026-07-27 14:19 ` Mathias Nyman
2026-07-30  2:24   ` Jie Deng
2026-07-30  4:48     ` Michal Pecio
2026-07-31  7:38       ` Jie Deng
2026-07-31 10:57         ` Michal Pecio [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=20260731125737.073cedb3.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=dengjie03@kylinos.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=mathias.nyman@linux.intel.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