From: Marc Zyngier <maz@kernel.org>
To: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Rob Herring <robh+dt@kernel.org>,
devicetree <devicetree@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>
Subject: Re: [PATCH v2 2/3] irqchip: dw-apb-ictl: support hierarchy irq domain
Date: Tue, 08 Sep 2020 10:45:17 +0100 [thread overview]
Message-ID: <0622508a42d5a5b25582a6ebd69ec1d2@kernel.org> (raw)
In-Reply-To: <0e860ff8-3e72-1099-c28c-c5a0bc28f2c4@huawei.com>
On 2020-09-08 10:40, Leizhen (ThunderTown) wrote:
> On 2020/9/8 15:41, Marc Zyngier wrote:
>> On 2020-09-08 08:11, Zhen Lei wrote:
>>> Add support to use dw-apb-ictl as primary interrupt controller.
>>>
>>> Suggested-by: Marc Zyngier <maz@kernel.org>
>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>> Tested-by: Haoyu Lv <lvhaoyu@huawei.com>
>>> ---
>>> drivers/irqchip/Kconfig | 2 +-
>>> drivers/irqchip/irq-dw-apb-ictl.c | 75
>>> +++++++++++++++++++++++++++++--
>>> 2 files changed, 73 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
>>> index bfc9719dbcdc..7c2d1c8fa551 100644
>>> --- a/drivers/irqchip/Kconfig
>>> +++ b/drivers/irqchip/Kconfig
>>> @@ -148,7 +148,7 @@ config DAVINCI_CP_INTC
>>> config DW_APB_ICTL
>>> bool
>>> select GENERIC_IRQ_CHIP
>>> - select IRQ_DOMAIN
>>> + select IRQ_DOMAIN_HIERARCHY
>>>
>>> config FARADAY_FTINTC010
>>> bool
>>> diff --git a/drivers/irqchip/irq-dw-apb-ictl.c
>>> b/drivers/irqchip/irq-dw-apb-ictl.c
>>> index aa6214da0b1f..405861322596 100644
>>> --- a/drivers/irqchip/irq-dw-apb-ictl.c
>>> +++ b/drivers/irqchip/irq-dw-apb-ictl.c
>>> @@ -17,6 +17,7 @@
>>> #include <linux/irqchip/chained_irq.h>
>>> #include <linux/of_address.h>
>>> #include <linux/of_irq.h>
>>> +#include <asm/exception.h>
>>>
>>> #define APB_INT_ENABLE_L 0x00
>>> #define APB_INT_ENABLE_H 0x04
>>> @@ -26,6 +27,30 @@
>>> #define APB_INT_FINALSTATUS_H 0x34
>>> #define APB_INT_BASE_OFFSET 0x04
>>>
>>> +/*
>>> + * irq domain of the primary interrupt controller. Currently, only
>>> one is
>>> + * supported.
>>
>> By definition, there is only one primary interrupt controller.
>
> OK, I will delete the comment "Currently, only one is supported".
> Should I replace it with your commend above?
No, just delete it.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-09-08 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 7:11 [PATCH v2 0/3] irqchip: dw-apb-ictl: support hierarchy irq domain Zhen Lei
2020-09-08 7:11 ` [PATCH v2 1/3] irqchip: dw-apb-ictl: prepare for " Zhen Lei
2020-09-08 7:11 ` [PATCH v2 2/3] irqchip: dw-apb-ictl: " Zhen Lei
2020-09-08 7:41 ` Marc Zyngier
2020-09-08 9:40 ` Leizhen (ThunderTown)
2020-09-08 9:45 ` Marc Zyngier [this message]
2020-09-08 9:16 ` kernel test robot
2020-09-08 7:11 ` [PATCH v2 3/3] 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=0622508a42d5a5b25582a6ebd69ec1d2@kernel.org \
--to=maz@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huawei.libin@huawei.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lvhaoyu@huawei.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--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).