From: "hans.zhang" <hans.zhang@cixtech.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: bhelgaas@google.com, cix-kernel-upstream@cixtech.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Chen <peter.chen@cixtech.com>,
ChunHao Lin <hau@realtek.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
nic_swsd@realtek.com, netdev@vger.kernel.org
Subject: Re: [PATCH] PCI: Add PCI quirk to disable L0s ASPM state for RTL8125 2.5GbE Controller
Date: Thu, 6 Mar 2025 11:32:04 +0800 [thread overview]
Message-ID: <84a00461-b8fa-48d0-9049-9a34abfe87a3@cixtech.com> (raw)
In-Reply-To: <20250305222016.GA316198@bhelgaas>
On 2025/3/6 06:20, Bjorn Helgaas wrote:
> Sounds like this should be a documented erratum. Realtek folks? Or
> maybe an erratum on the other end of the link, which looks like a CIX
> Root Port:
>
> https://admin.pci-ids.ucw.cz/read/PC/1f6c/0001
Hi Bjorn,
Name: CIX P1 CD8180 PCI Express Root Port
0000:90:00.0 PCI bridge [0604]: Device [1f6c:0001]
0001:60:00.0 PCI bridge [0604]: Device [1f6c:0001]
0002:00:00.0 PCI bridge [0604]: Device [1f6c:0001]
0003:30:00.0 PCI bridge [0604]: Device [1f6c:0001]
This URL does not appear right, how should be changed, is it you? Or can
you tell me who I should call to change it?
The correct answer is:
0000:90:00.0 PCI bridge [0604]: Device [1f6c:0001]
0001:C0:00.0 PCI bridge [0604]: Device [1f6c:0001]
0002:60:00.0 PCI bridge [0604]: Device [1f6c:0001]
0003:30:00.0 PCI bridge [0604]: Device [1f6c:0001]
0004:00:00.0 PCI bridge [0604]: Device [1f6c:0001]
The domain might be random, so whichever controller probes first, it's
assigned first. The URL currently shows the BDF with one controller
missing. That's the order in which we're going to controller probe.
Best regards,
Hans
next prev parent reply other threads:[~2025-03-06 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:30 [PATCH] PCI: Add PCI quirk to disable L0s ASPM state for RTL8125 2.5GbE Controller hans.zhang
2025-03-05 22:20 ` Bjorn Helgaas
2025-03-06 3:16 ` hans.zhang
2025-03-06 3:32 ` hans.zhang [this message]
2025-03-06 16:28 ` Bjorn Helgaas
2025-03-07 1:38 ` hans.zhang
2025-03-06 23:00 ` Heiner Kallweit
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=84a00461-b8fa-48d0-9049-9a34abfe87a3@cixtech.com \
--to=hans.zhang@cixtech.com \
--cc=bhelgaas@google.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=hau@realtek.com \
--cc=helgaas@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=peter.chen@cixtech.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