From: "Verma, Achal" <a-verma1@ti.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Vignesh Raghavendra" <vigneshr@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>, Achal Verma <a-verma1@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: enable PCIe controller on TI platforms
Date: Tue, 9 May 2023 15:32:15 +0530 [thread overview]
Message-ID: <35f0c8d0-6681-4fb7-5f80-646687225d14@ti.com> (raw)
In-Reply-To: <2880d5bb-61ce-a4d7-f870-b5549a5d88f2@linaro.org>
On 5/9/2023 3:01 PM, Krzysztof Kozlowski wrote:
> On 09/05/2023 11:19, Verma, Achal wrote:
>>
>> Hello,
>> On 5/9/2023 1:58 PM, Arnd Bergmann wrote:
>>> 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
>> So, my understanding is that following change is expected
>> +CONFIG_PCIE_CADENCE=m
>> +CONFIG_PCIE_CADENCE_HOST=m
>> +CONFIG_PCIE_CADENCE_EP=m
>> +CONFIG_PCI_J721E=m
>> +CONFIG_PCI_J721E_HOST=m
>> +CONFIG_PCI_J721E_EP=m
>> +CONFIG_PCI_EPF_NTB=m
>>
>> I also want to inform that pci_j721e.c is a single file with both host
>> and EP functionality, last attempt to build it as modules depending on
>> host or EP selected failed because of symbols dependency.
>> Refactoring of pci_j721e.c into common, host and EP specific files could
>> work similar to the Cadence driver, So I will follow this way and push
>> the changes.
>>
>> Please let me know if there are concerns.
>
> Aren't HOST and EP just customizing main module?
Current pci-j721e driver is composed of host specific and endpoint
specific code encapsulated in switch case and shared required common
code, last attempt of putting endpoint and host specific code inside EP
and HOST CONFIGS respectively failed (also reported by kernel test bot)
when tried with different combinations of Y/M/N along with CADENCE
driver on which pci-j721e depends, So only way is to break main module
into common, host and endpoint files.
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2023-05-09 10:02 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
2023-05-09 9:19 ` [EXTERNAL] " Verma, Achal
2023-05-09 9:31 ` Krzysztof Kozlowski
2023-05-09 10:02 ` Verma, Achal [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=35f0c8d0-6681-4fb7-5f80-646687225d14@ti.com \
--to=a-verma1@ti.com \
--cc=arnd@arndb.de \
--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®