On 7/28/2026 10:09 PM, Fabio Estevam wrote: > Caution: This is an external email. Please take care when clicking links or > opening attachments. When in doubt, report the message using the 'Report this > email' button > > > Hi Joseph, > > On Mon, Jul 27, 2026 at 3:07 AM Joseph Guo <[email protected]> wrote: > >> Sure I understand the bootph- properties are accepted upstream. I'm happy to >> upstream them. >> I prefer to keep the alias into u-boot.dtsi because only u-boot read that >> alias to assgin the fixed sequence to netc PCI host controller. It is no >> needed by kernel. >> Is it okay for you? > > I accept the u-boot.dtsi changes, but please send them upstream. > > The aliases node can also be upstreamed. There is no reason for Linux > and U-Boot dts to deviate on this area,
Hi Fabio, On i.MX95, `netc_bus0`/`netc_bus1` are internal pseudo-PCI buses used by the NETC subsystem for register access — they are not real external PCIe root complexes. Without explicit ordering, `netc_bus0`/`netc_bus1` may be enumerated before or interleaved with the real external PCIe root complex, making it difficult to predictably identify and target the true PCIe interface (e.g., for NVMe, PCIe Ethernet, or other add-in cards) in boot scripts and environment variables. The `pci0`/`pci1` aliases fix the enumeration order in U-Boot only. Linux does not use `pci` aliases for bus ordering. In kernel, it use 'linux,pci-domain = <0>;' instead. I prefer keep the alias in u-boot.dtsi instead of upstream. -- Best Regards, Joseph
