From: Vladimir Kondratiev <Vladimir.Kondratiev@mobileye.com>
To: Anup Patel <anup@brainfault.org>
Cc: Thomas Gleixner <tglx@kernel.org>, Radu Rendec <radu@rendec.net>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Jessica Liu <liu.xuemei1@zte.com.cn>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v5 2/2] irqchip/riscv-aplic: force synchronous probing
Date: Thu, 12 Nov 2026 14:11:11 +0200 [thread overview]
Message-ID: <a35f6eb0-ed5c-4ba4-85d0-c3a6d6bbe8ac@mobileye.com> (raw)
In-Reply-To: <CAAhSdy2kxydOk9wPdBtVHCTN2uDrpFbQ0WGUXHz0AUvUWAncpg@mail.gmail.com>
On 11/10/26 10:07, Anup Patel wrote:
> Making the whole driver synchronously probe is a conservative work-around.
>
> Your original direction was good. How about the following:
> 1) Convert aplic_syscore_registered as atomic variable
> 2) Add another atomic variable aplic_direct_parent_irq_count and use
> "if (!atomic_inc_return(&aplic_direct_parent_irq_count) && domain) {"
> in aplic_direct_setup().
I will get to it some day. For now, forcing synchronous probing is the
easiest way to get things functionally correct, even not most flexible.
Thanks, Vladimir
prev parent reply other threads:[~2026-11-12 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:38 [PATCH v5 0/2] irqchip/riscv-aplic: fix probing of multiple APLIC instances Vladimir Kondratiev
2026-10-20 15:38 ` [PATCH v5 1/2] irqchip/riscv-aplic: do not mark the syscore registered flag ro_after_init Vladimir Kondratiev
2026-11-09 9:22 ` [tip: irq/drivers] irqchip/riscv-aplic: Do " tip-bot2 for Vladimir Kondratiev
2026-10-20 15:38 ` [PATCH v5 2/2] irqchip/riscv-aplic: force synchronous probing Vladimir Kondratiev
2026-11-09 9:22 ` [tip: irq/drivers] irqchip/riscv-aplic: Force " tip-bot2 for Vladimir Kondratiev
2026-11-10 8:07 ` [PATCH v5 2/2] irqchip/riscv-aplic: force " Anup Patel
2026-11-12 12:11 ` Vladimir Kondratiev [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=a35f6eb0-ed5c-4ba4-85d0-c3a6d6bbe8ac@mobileye.com \
--to=vladimir.kondratiev@mobileye.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=liu.xuemei1@zte.com.cn \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=radu@rendec.net \
--cc=rostedt@goodmis.org \
--cc=tglx@kernel.org \
/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
all inboxes | Powered by JetHome®