From: Vivian Wang <wangruikang@iscas.ac.cn>
To: Yixun Lan <dlan@gentoo.org>, 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: Tue, 3 Mar 2026 17:54:48 +0800 [thread overview]
Message-ID: <ded1cb94-8484-4ea3-ba7a-22fa76547db9@iscas.ac.cn> (raw)
In-Reply-To: <20260302074235-GYB288339@gentoo.org>
On 3/2/26 15:42, Yixun Lan wrote:
> 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..
For example systemd-udevd provides the interface name based on the
segment group / domain number, so if you add an additional PCIe network
card, the name of the network interface will flip between enP0p1s0 and
enP1p1s0, which is a bit inconvenient.
This isn't inherently a problem (these things were never as predictible
as they wanted anyway) but a convenience would still be nice.
Vivian "dramforever" Wang
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-03-03 9:55 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
2026-03-03 9:54 ` Vivian Wang [this message]
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=ded1cb94-8484-4ea3-ba7a-22fa76547db9@iscas.ac.cn \
--to=wangruikang@iscas.ac.cn \
--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@gentoo.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