From: Yang Su <yang.su@linux.alibaba.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] PCI: Use pci_bridge_wait_for_secondary_bus after SBR instead of ssleep(1)
Date: Wed, 17 Aug 2022 22:30:10 +0800 [thread overview]
Message-ID: <cover.1660746147.git.yang.su@linux.alibaba.com> (raw)
In pci_reset_secondary_bus(), ssleep(1) is too long for PCIe.
So use pci_bridge_wait_for_secondary_bus after SBR.
Yang Su (1):
PCI: Use pci_bridge_wait_for_secondary_bus after SBR instead of
ssleep(1)
drivers/pci/pci.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
--
2.19.1.6.gb485710b
next reply other threads:[~2022-08-17 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 14:30 Yang Su [this message]
2022-08-17 14:30 ` [PATCH 1/1] PCI: Use pci_bridge_wait_for_secondary_bus after SBR instead of ssleep(1) Yang Su
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=cover.1660746147.git.yang.su@linux.alibaba.com \
--to=yang.su@linux.alibaba.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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.