public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 8 Mar 2026 17:18:26 +0800	[thread overview]
Message-ID: <20260308091826-GYA318052@gentoo.org> (raw)
In-Reply-To: <20260307043806.957175-1-amadeus@jmu.edu.cn>

Hi Chukun,

On 12:38 Sat 07 Mar     , Chukun Pan wrote:
> Hi,
> 
> > You describe what's has been done here, but no why?
> 
> Because the PCIe boot order is random, if there are two R8125
> network cards, their interface names will not be fixed.
> 
> For example:
> First boot:
> pcie@ca400000 -> eth2
> pcie@ca800000 -> eth3
> 
> Second boot:
> pcie@ca400000 -> eth3
> pcie@ca800000 -> eth2
> 
Ok, I can understand your problem

> If their PCI domain numbers are fixed, I can fix the interface
> names by matching /sys/devices using a script.
> 
If you want to have a fixed interface name, you could setup a udev
rules according to mac address? something like:

$ cat /etc/udev/rules.d/70-network.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="01:02:03:12:34:56", NAME="eth2"

but, I see no harm to add a pci domain property..

> > Can you add description about why problem with random domain,
> > and the motivation of the change behind?
> 
> Should I improve the commit messages?
> 
Yes, please, thanks

> Thanks,
> Chukun
> 

-- 
Yixun Lan (dlan)

      reply	other threads:[~2026-03-08  9:18 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
2026-03-07  4:38     ` Chukun Pan
2026-03-08  9:18       ` Yixun Lan [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=20260308091826-GYA318052@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