From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Rob Herring <robh+dt@kernel.org>, Guo Ren <guoren@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-csky <linux-csky@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Haoyu Lv <lvhaoyu@huawei.com>, Libin <huawei.libin@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
"Jianguo Chen" <chenjianguo3@huawei.com>
Subject: Re: [PATCH v4 1/4] genirq: define an empty function set_handle_irq() if !GENERIC_IRQ_MULTI_HANDLER
Date: Thu, 17 Sep 2020 17:47:34 +0800 [thread overview]
Message-ID: <c9868aee-f03a-53cf-1004-f1e6ddcf3f44@huawei.com> (raw)
In-Reply-To: <22defc7e8bf8d4dd91565473e1a67f22@kernel.org>
On 2020/9/17 17:32, Marc Zyngier wrote:
> On 2020-09-17 04:46, Leizhen (ThunderTown) wrote:
>> On 2020/9/15 16:43, Zhen Lei wrote:
>>> To avoid compilation error if an irqchip driver references the function
>>> set_handle_irq() but may not select GENERIC_IRQ_MULTI_HANDLER on some
>>> systems.
>>
>> Hi, Marc:
>> Do you agree with this method?
>>
>> Otherwise, I should use "#ifdef CONFIG_GENERIC_IRQ_MULTI_HANDLER ... #endif"
>> to perform the compilation isolation. This may make the code less beautiful.
>>
>>>
>>> For example, the Synopsys DesignWare APB interrupt controller
>>> (dw_apb_ictl) is used as the secondary interrupt controller on arc, csky,
>>> arm64, and most arm32 SoCs, and it's also used as the primary interrupt
>>> controller on Hisilicon SD5203 (an arm32 SoC). The latter need to use
>>> set_handle_irq() to register the top-level IRQ handler, but this multi
>>> irq handler registration mechanism is not implemented on arc system.
>>>
>>> The input parameter "handle_irq" maybe defined as static and only
>>> set_handle_irq() references it. This will trigger "defined but not used"
>>> warning. So add "(void)handle_irq" to suppress it.
>>>
>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>> ---
>>> include/linux/irq.h | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/include/linux/irq.h b/include/linux/irq.h
>>> index 1b7f4dfee35b397..0848a2aaa9b40b1 100644
>>> --- a/include/linux/irq.h
>>> +++ b/include/linux/irq.h
>>> @@ -1252,6 +1252,8 @@ void irq_matrix_free(struct irq_matrix *m, unsigned int cpu,
>>> * top-level IRQ handler.
>>> */
>>> extern void (*handle_arch_irq)(struct pt_regs *) __ro_after_init;
>>> +#else
>>> +#define set_handle_irq(handle_irq) do { (void)handle_irq; } while (0)
>>> #endif
>>>
>>> #endif /* _LINUX_IRQ_H */
>>>
>
> You shouldn't just make it a NOP. Consider adding a WARN_ON(1), so that
> people can realize this cannot work without the required architecture support.
Oh, right. I will add it.
>
> M.
next prev parent reply other threads:[~2020-09-17 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:43 [PATCH v4 0/4] irqchip: dw-apb-ictl: support hierarchy irq domain Zhen Lei
2020-09-15 8:43 ` [PATCH v4 1/4] genirq: define an empty function set_handle_irq() if !GENERIC_IRQ_MULTI_HANDLER Zhen Lei
2020-09-17 3:46 ` Leizhen (ThunderTown)
2020-09-17 9:32 ` Marc Zyngier
2020-09-17 9:47 ` Leizhen (ThunderTown) [this message]
2020-09-15 8:43 ` [PATCH v4 2/4] irqchip: dw-apb-ictl: prepare for support hierarchy irq domain Zhen Lei
2020-09-15 8:43 ` [PATCH v4 3/4] irqchip: dw-apb-ictl: " Zhen Lei
2020-09-15 8:43 ` [PATCH v4 4/4] dt-bindings: " Zhen Lei
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=c9868aee-f03a-53cf-1004-f1e6ddcf3f44@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=chenjianguo3@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=huawei.libin@huawei.com \
--cc=jason@lakedaemon.net \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvhaoyu@huawei.com \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
/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).