From: Albert Zhou <albert.zhou.50@gmail.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, lukas@wunner.de,
mika.westerberg@linux.intel.com
Subject: [PATCH v4 2/2] pci: pcie: add dependency info to Kconfig
Date: Tue, 15 Nov 2022 22:38:57 +1100 [thread overview]
Message-ID: <20221115113857.35800-3-albert.zhou.50@gmail.com> (raw)
In-Reply-To: <20221115113857.35800-1-albert.zhou.50@gmail.com>
Thunderbolt/USB4 PCIe tunneling require the Hotplug feature. This is now
recorded in the help message for HOTPLUG_PCI_PCIE. Further, PCIEPORTBUS
and HOTPLUG_PCI_PCIE are defaulted to Y if USB4 is selected.
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Albert Zhou <albert.zhou.50@gmail.com>
---
drivers/pci/pcie/Kconfig | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/pcie/Kconfig b/drivers/pci/pcie/Kconfig
index 788ac8df3f9d..32cc9a31e228 100644
--- a/drivers/pci/pcie/Kconfig
+++ b/drivers/pci/pcie/Kconfig
@@ -4,20 +4,22 @@
#
config PCIEPORTBUS
bool "PCI Express Port Bus support"
+ default y if USB4
help
This enables PCI Express Port Bus support. Users can then enable
support for Native Hot-Plug, Advanced Error Reporting, Power
Management Events, and Downstream Port Containment.
-
#
# Include service Kconfig here
#
config HOTPLUG_PCI_PCIE
bool "PCI Express Hotplug driver"
depends on HOTPLUG_PCI && PCIEPORTBUS
+ default y if USB4
help
Say Y here if you have a motherboard that supports PCI Express Native
- Hotplug
+ Hotplug. Thunderbolt/USB4 PCIe tunneling needs Native PCIe Hotplug to
+ be enabled
When in doubt, say N.
--
2.34.1
next prev parent reply other threads:[~2022-11-15 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 11:38 [PATCH v4 0/2] add hotplug depedency info Albert Zhou
2022-11-15 11:38 ` [PATCH v4 1/2] pci: hotplug: add dependency info to Kconfig Albert Zhou
2022-11-15 11:38 ` Albert Zhou [this message]
2022-11-15 15:29 ` [PATCH v4 0/2] add hotplug depedency info Bjorn Helgaas
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=20221115113857.35800-3-albert.zhou.50@gmail.com \
--to=albert.zhou.50@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@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 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.