From: Thomas Gleixner <tglx@linutronix.de>
To: niliqiang <ni_liqiang@126.com>, maz@kernel.org
Cc: ajones@ventanamicro.com, anup@brainfault.org,
apatel@ventanamicro.com, atishp@atishpatra.org, bjorn@kernel.org,
conor+dt@kernel.org, dai.hualiang@zte.com.cn,
deng.weixian@zte.com.cn, devicetree@vger.kernel.org,
frowand.list@gmail.com, guo.chang2@zte.com.cn,
hu.yuye@zte.com.cn, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
liu.qingtao2@zte.com.cn, liu.wenhong35@zte.com.cn,
ni.liqiang@zte.com.cn, ni_liqiang@126.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, robh+dt@kernel.org,
saravanak@google.com, sunilvl@ventanamicro.com,
wu.jiabao@zte.com.cn
Subject: Re: [PATCH v16 6/9] irqchip: Add RISC-V advanced PLIC driver for direct-mode
Date: Tue, 25 Nov 2025 17:42:09 +0100 [thread overview]
Message-ID: <87qztmgj32.ffs@tglx> (raw)
In-Reply-To: <20251125160731.4902-1-ni_liqiang@126.com>
On Wed, Nov 26 2025 at 00:07, niliqiang wrote:
> We've noticed that PCIe enumeration order tends to vary across system reboots (for example: first
> boot showed PC08->PC06->PC10->PC07->PC11->PC09, while second boot showed
> PC09->PC06->PC08->PC11->PC07->PC10), even though the ACPI firmware consistently reports the root
> bridge sequence as PC06->PC07->PC08->PC09->PC10->PC11.
>
> In our testing, we found that adjusting the registration priority of the aplic driver seems to help
> ensure the interrupt controller initializes before PCI enumeration, leading to more consistent
> device ordering.
You're repeating yourself over and over, but you're missing the point.
The ACPI table does not provide a sequence, it provides a collection and
it's nowhere written in stone that this collection has to be processed
in order.
If you want a sequence then put dependencies into the table and be done
with it, no?
Thanks,
tglx
next prev parent reply other threads:[~2025-11-25 16:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 14:02 [PATCH v16 0/9] Linux RISC-V AIA Support Anup Patel
2024-03-07 14:02 ` [PATCH v16 1/9] dt-bindings: interrupt-controller: Add RISC-V incoming MSI controller Anup Patel
2024-03-07 14:03 ` [PATCH v16 2/9] irqchip: Add RISC-V incoming MSI controller early driver Anup Patel
2024-04-19 3:23 ` Eric Cheng
2024-04-19 3:44 ` Anup Patel
2024-04-19 3:55 ` Eric Cheng
2024-03-07 14:03 ` [PATCH v16 3/9] irqchip/riscv-imsic: Add device MSI domain support for platform devices Anup Patel
2024-03-07 14:03 ` [PATCH v16 4/9] irqchip/riscv-imsic: Add device MSI domain support for PCI devices Anup Patel
2024-03-07 14:03 ` [PATCH v16 5/9] dt-bindings: interrupt-controller: Add RISC-V advanced PLIC Anup Patel
2024-03-07 14:03 ` [PATCH v16 6/9] irqchip: Add RISC-V advanced PLIC driver for direct-mode Anup Patel
2025-11-20 14:43 ` niliqiang
2025-11-21 8:50 ` Sunil V L
2025-11-21 13:54 ` niliqiang
2025-11-22 9:37 ` Marc Zyngier
2025-11-25 16:07 ` niliqiang
2025-11-25 16:42 ` Thomas Gleixner [this message]
2025-11-26 16:15 ` niliqiang
2024-03-07 14:03 ` [PATCH v16 7/9] irqchip/riscv-aplic: Add support for MSI-mode Anup Patel
2024-03-07 14:03 ` [PATCH v16 8/9] RISC-V: Select APLIC and IMSIC drivers Anup Patel
2024-03-07 14:03 ` [PATCH v16 9/9] MAINTAINERS: Add entry for RISC-V AIA drivers Anup Patel
2024-03-07 14:11 ` [PATCH v16 0/9] Linux RISC-V AIA Support Anup Patel
2024-03-07 21:03 ` Thomas Gleixner
2024-03-08 11:11 ` Björn Töpel
2024-03-08 11:13 ` Björn Töpel
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=87qztmgj32.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=bjorn@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dai.hualiang@zte.com.cn \
--cc=deng.weixian@zte.com.cn \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=guo.chang2@zte.com.cn \
--cc=hu.yuye@zte.com.cn \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liu.qingtao2@zte.com.cn \
--cc=liu.wenhong35@zte.com.cn \
--cc=maz@kernel.org \
--cc=ni.liqiang@zte.com.cn \
--cc=ni_liqiang@126.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=sunilvl@ventanamicro.com \
--cc=wu.jiabao@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).