From: Marc Zyngier <maz@kernel.org>
To: Zhen Lei <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>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH 0/2] add support for Hisilicon SD5203 vector interrupt controller
Date: Thu, 03 Sep 2020 17:46:44 +0100 [thread overview]
Message-ID: <ac9458877cd414a8265d267569b0e8ea@kernel.org> (raw)
In-Reply-To: <20200903120504.2308-1-thunder.leizhen@huawei.com>
On 2020-09-03 13:05, Zhen Lei wrote:
> The interrupt controller of SD5203 SoC is VIC(vector interrupt
> controller), it's
> based on Synopsys DesignWare APB interrupt controller (dw_apb_ictl) IP,
> but it
> can not directly use dw_apb_ictl driver. The main reason is that VIC is
> used as
> primary interrupt controller and dw_apb_ictl driver worked for
> secondary
> interrupt controller.
What prevents you from improving the existing driver so that it can act
as a primary interrupt controller? It shouldn't be rocket science,
really.
There are some examples in the tree of drivers that can be used in
both situations (GIC, VIC
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-09-03 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 12:05 [PATCH 0/2] add support for Hisilicon SD5203 vector interrupt controller Zhen Lei
2020-09-03 12:05 ` [PATCH 1/2] dt-bindings: interrupt-controller: add " Zhen Lei
2020-09-14 20:31 ` Rob Herring
2020-09-15 6:12 ` Leizhen (ThunderTown)
2020-09-17 3:30 ` Leizhen (ThunderTown)
2020-09-18 18:55 ` Rob Herring
2020-09-19 2:02 ` Leizhen (ThunderTown)
2020-09-03 12:05 ` [PATCH 2/2] irqchip: " Zhen Lei
2020-09-03 16:46 ` Marc Zyngier [this message]
2020-09-04 4:57 ` [PATCH 0/2] add support for " Leizhen (ThunderTown)
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=ac9458877cd414a8265d267569b0e8ea@kernel.org \
--to=maz@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).