linux-kernel - Re: [PATCH 0/2] add support for Hisilicon SD5203 vector interrupt controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ac9458877cd414a8265d267569b0e8ea@kernel.org>
Date:   Thu, 03 Sep 2020 17:46:44 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Zhen Lei <thunder.leizhen@...wei.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Jason Cooper <jason@...edaemon.net>,
        Rob Herring <robh+dt@...nel.org>,
        devicetree <devicetree@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Kefeng Wang <wangkefeng.wang@...wei.com>
Subject: Re: [PATCH 0/2] add support for Hisilicon SD5203 vector interrupt
 controller

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...