From: Hans Zhang <18255117159@163.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, thomas.richard@bootlin.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
rockswang7@gmail.com
Subject: Re: [PATCH] PCI: cadence: Fixed cdns_pcie_host_link_setup return value.
Date: Fri, 20 Dec 2024 15:27:22 +0800 [thread overview]
Message-ID: <44c74561-a4db-4550-a07e-67f51556dd03@163.com> (raw)
In-Reply-To: <20241219133545.jiyqdzbkpwfu2rcv@thinkpad>
On 12/19/24 08:35, Manivannan Sadhasivam wrote:
>> We have 5 PCIe controllers, and if a few of them are not connected to the
>> device. And it will affect the boot time.
>>
>
> Why are you enabling all controllers? Can't you just enable the ones you know
> the endpoints are going to be connected? I'm just trying to see if we can avoid
> having a quirk.
Our SOC has a PC product situation, and there may be PCIe slots on the
PCB, but the device may not be plugged in. So we need to enable all ports.
> If you do not know, then you need to introduce a quirk for your platform.
> But that requires your controller driver to be upstreamed. We cannot provide
> hooks for downstream drivers in upstream.
Our controller driver currently has no plans for upstream and needs to
wait for notification from the boss.
Regards
Hans
next prev parent reply other threads:[~2024-12-20 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 8:14 Hans Zhang
2024-12-19 8:33 ` Siddharth Vadapalli
2024-12-19 8:49 ` Hans Zhang
2024-12-19 8:59 ` Siddharth Vadapalli
[not found] ` <f2c8be62-7ff6-f0d0-f34a-ddb6915df0a4@163.com>
2024-12-19 9:49 ` Manivannan Sadhasivam
2024-12-19 10:29 ` Hans Zhang
2024-12-19 11:20 ` Manivannan Sadhasivam
2024-12-19 11:46 ` Hans Zhang
2024-12-19 13:35 ` Manivannan Sadhasivam
2024-12-20 7:27 ` Hans Zhang [this message]
2024-12-20 12:32 ` Manivannan Sadhasivam
2024-12-21 14:47 ` Hans Zhang
2024-12-19 10:04 ` Hans Zhang
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=44c74561-a4db-4550-a07e-67f51556dd03@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=rockswang7@gmail.com \
--cc=s-vadapalli@ti.com \
--cc=thomas.richard@bootlin.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 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®