linux-kernel - Re: [PATCH v2 01/14] dt-bindings: remoteproc: Add TI PRUSS bindings

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] [day] [month] [year] [list]

Message-ID: <CACRpkdYiLDbb=D2biBtr1aWJc6ottUONWm5qPE6g6_Pbpg94QQ@mail.gmail.com>
Date:   Wed, 20 Feb 2019 10:51:16 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Suman Anna <s-anna@...com>
Cc:     Roger Quadros <rogerq@...com>, Marc Zyngier <marc.zyngier@....com>,
        "Davis, Andrew" <afd@...com>, Lokesh Vutla <lokeshvutla@...com>,
        ext Tony Lindgren <tony@...mide.com>,
        Ohad Ben-Cohen <ohad@...ery.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        David Lechner <david@...hnology.com>,
        "Nori, Sekhar" <nsekhar@...com>, Tero Kristo <t-kristo@...com>,
        nsaulnier@...com, jreeder@...com,
        Murali Karicheri <m-karicheri2@...com>,
        woods.technical@...il.com, Linux-OMAP <linux-omap@...r.kernel.org>,
        linux-remoteproc@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        DTML <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 01/14] dt-bindings: remoteproc: Add TI PRUSS bindings

On Fri, Feb 15, 2019 at 2:00 AM Suman Anna <s-anna@...com> wrote:

> Mark, Linus,
>
> So, I hope it is clear from Roger's responses that above assertions do
> not hold true to this INTC, and so want to confirm that we are good with
> the current non-hierarchical design.

IIUC the 64 lines are latched onto 8 lines, but all 64 lines have
individual masking and ACKing bits and can all be used at the same
time, so yes that is cascading and then you should indeed use
the chained (or nested) IRQ handler.

Yours,
Linus Walleij