From: Yixun Lan <dlan@gentoo.org>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, conor+dt@kernel.org,
devicetree@vger.kernel.org, dlan@kernel.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, pjw@kernel.org, robh@kernel.org,
spacemit@lists.linux.dev
Subject: Re: [PATCH 1/1] riscv: dts: spacemit: Add 'linux,pci-domain' to PCIe nodes for K1
Date: Mon, 2 Mar 2026 15:42:35 +0800 [thread overview]
Message-ID: <20260302074235-GYB288339@gentoo.org> (raw)
In-Reply-To: <20260302071502.63672-1-amadeus@jmu.edu.cn>
Hi Chukun,
On 15:15 Mon 02 Mar , Chukun Pan wrote:
> Hi,
>
> > The SpacemiT K1 SoC has 3 PCIe EP controller nodes. Add the
> > 'linux,pci-domain' property to assign a PCI domain number to
> > each of the controllers instead of assigning it randomly.
>
> Does anyone have any thoughts on this?
> Without this patch, the PCI domain number is random.
>
You describe what's has been done here, but no why?
Can you add description about why problem with random domain,
and the motivation of the change behind?
from my understanding of reading DT document, either way seems
fine..
> ```
> /# find /sys/devices -name net
> /sys/devices/platform/soc/soc:pcie-bus/ca800000.pcie/pci0001:00/0001:00:00.0/0001:01:00.0/net
> /sys/devices/platform/soc/soc:pcie-bus/ca400000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/net
>
> /# find /sys/devices -name net
> /sys/devices/platform/soc/soc:pcie-bus/ca800000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/net
> /sys/devices/platform/soc/soc:pcie-bus/ca400000.pcie/pci0001:00/0001:00:00.0/0001:01:00.0/net
> ```
>
> Thanks,
> Chukun
>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-03-02 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 10:00 [PATCH 1/1] riscv: dts: spacemit: Add 'linux,pci-domain' to PCIe nodes for K1 Chukun Pan
2026-03-02 7:15 ` Chukun Pan
2026-03-02 7:42 ` Yixun Lan [this message]
2026-03-03 9:54 ` Vivian Wang
2026-03-07 4:38 ` Chukun Pan
2026-03-08 9:18 ` Yixun Lan
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=20260302074235-GYB288339@gentoo.org \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=amadeus@jmu.edu.cn \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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