[PATCH] irqchip/riscv-aplic: Register the driver prior to device creation

Yicong Yang yang.yicong at picoheart.com
Thu Jan 15 22:16:21 PST 2026


On 1/15/26 9:28 PM, Thomas Gleixner wrote:
> On Thu, Jan 15 2026 at 16:31, Yicong Yang wrote:
>> so based on above, if we use async_wq (with async_schedule* APIs) in
>> acpi_scan_clear_dep_queue() for creating these devices, the issue
>> could be solved since we're sure to have these devices before entering
>> userspace, since the barrier of async_synchronize_full(). This should be
>> a solution with a conceptual support and I did a quick test on our
>> platform it solves the issue.
> 
> Sounds about right to me. The drivers core and ACPI folks might have
> opinions though :)
> 

sure I'll wait a bit to see if there's further comment before sending out
next version.

>> As for the order of console_on_rootfs()/async_synchronize_full(),
>> though our issue is not directly caused by it, it will cause the
>> same issue (by the console open time the async probing maybe not
>> finised) theoretically and needs to be fixed, is it?
> 
> Yes, that should move past the synchronization point.
> 

will include this fix as a separate patch since they're two separate issue.

thanks a lot for the useful discussion to help find a better solution :)

Thanks.



More information about the linux-riscv mailing list