From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
manivannan.sadhasivam@oss.qualcomm.com,
Bjorn Andersson <andersson@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>, Eric Biggers <ebiggers@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>,
Michal Simek <michal.simek@amd.com>, Sven Peter <sven@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable PCIe hotplug support
Date: Wed, 29 Jul 2026 19:29:02 +0530 [thread overview]
Message-ID: <45c1f8fd-1fba-44a1-8b4a-ff718f387927@oss.qualcomm.com> (raw)
In-Reply-To: <47cb0376-a4db-428c-9f61-341b134a8b97@oss.qualcomm.com>
On 7/29/2026 11:32 AM, Krzysztof Kozlowski wrote:
> On 28/07/2026 18:07, Krishna Chaitanya Chundru wrote:
>> Enable CONFIG_HOTPLUG_PCI_PCIE to support native PCIe hotplug
>> controllers on arm64 platforms.
> Which ones benefit from this? Why do we want it in our development
> defconfig?
Sorry I should have added all the details in the commit.
Qualcomm platforms like Glymur and Hamoa have PCIe root ports/root complexes
with native hotplug capability (including USB4
PCIe tunneling ports), so CONFIG_HOTPLUG_PCI_PCIE is needed for hotplug to
work on them. We'd like it on by default in our
development defconfig so it works out of the box during bring-up/testing
without every developer needing to enable it
manually.
- Krishna chaitanya.
> Best regards,
> Krzysztof
prev parent reply other threads:[~2026-07-29 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 16:07 Krishna Chaitanya Chundru
2026-07-29 6:02 ` Krzysztof Kozlowski
2026-07-29 13:59 ` Krishna Chaitanya Chundru [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=45c1f8fd-1fba-44a1-8b4a-ff718f387927@oss.qualcomm.com \
--to=krishna.chundru@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=ebiggers@kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=michal.simek@amd.com \
--cc=sven@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®