From: "Arnd Bergmann" <arnd@arndb.de>
To: "Vignesh Raghavendra" <vigneshr@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Achal Verma" <a-verma1@ti.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Mark Brown" <broonie@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>, "Nishanth Menon" <nm@ti.com>,
"Milind Parab" <mparab@cadence.com>,
"Swapnil Kashinath Jakhade" <sjakhade@cadence.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: enable PCIe controller on TI platforms
Date: Tue, 09 May 2023 10:28:19 +0200 [thread overview]
Message-ID: <63dc3d1b-ba17-48ee-a02e-83b2903e360a@app.fastmail.com> (raw)
In-Reply-To: <de6432db-0da0-b535-1f44-04541116be8b@ti.com>
On Tue, May 9, 2023, at 10:08, Vignesh Raghavendra wrote:
> Also, see [0] for history. We really want these to be
> modules unless its necessary for bootup.
>
> You may want to revive [1] and get it to mainline
>
> [0]
> https://lore.kernel.org/linux-arm-kernel/CAK8P3a2VSBvOn1o+q1PYZaQ6LS9U4cz+DZGuDbisHkwNs2dAAw@mail.gmail.com/
> [1]
> https://lore.kernel.org/linux-arm-kernel/20230110153805.GA1505901@bhelgaas/
Agreed, that seems simple enough. Ideally these should even
be removable modules, not just single-load but unremovable.
Doing that may require changes to the cadence PCIe host
code if that does not support unloading yet (I have not
checked), but should not require any changes to the core
PCIe host code that supports loadable/removable modules.
Arnd
next prev parent reply other threads:[~2023-05-09 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 6:34 Achal Verma
2023-05-09 6:39 ` Krzysztof Kozlowski
2023-05-09 8:08 ` Vignesh Raghavendra
2023-05-09 8:28 ` Arnd Bergmann [this message]
2023-05-09 9:19 ` [EXTERNAL] " Verma, Achal
2023-05-09 9:31 ` Krzysztof Kozlowski
2023-05-09 10:02 ` Verma, Achal
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=63dc3d1b-ba17-48ee-a02e-83b2903e360a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=a-verma1@ti.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mparab@cadence.com \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=quic_bjorande@quicinc.com \
--cc=rafal@milecki.pl \
--cc=sjakhade@cadence.com \
--cc=vigneshr@ti.com \
--cc=will@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®