linux-kernel - Re: [PATCH] of: property: Add device link support for interrupts

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: <29319d4bd3c6f8a19a6f800aff0f8f93@kernel.org>
Date:   Thu, 07 Jan 2021 17:17:40 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     Saravana Kannan <saravanak@...gle.com>
Cc:     Rob Herring <robh@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Frank Rowand <frowand.list@...il.com>,
        Kevin Hilman <khilman@...libre.com>,
        Android Kernel Team <kernel-team@...roid.com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] of: property: Add device link support for interrupts

On 2021-01-07 17:08, Saravana Kannan wrote:
> On Thu, Jan 7, 2021 at 8:48 AM Rob Herring <robh@...nel.org> wrote:
>> 
>> On Wed, Jan 6, 2021 at 6:26 PM Saravana Kannan <saravanak@...gle.com> 
>> wrote:
>> >
>> > On Wed, Jan 6, 2021 at 10:52 AM Saravana Kannan <saravanak@...gle.com> wrote:

[...]

>> > > I wasn't aware of interrupt-map until a few weeks ago and didn't know
>> > > it carried phandles. I can add support for that too. There's no reason
>> > > for all of them to go in one patch though.
>> >
>> > Hmm... I looked at
>> > Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>> > and it has no documentation for interrupt-map. There's a bunch of
>> > references to it in device specific DT binding documentation but I
>> > don't want to rely on those for correctness.
>> 
>> See the DT spec and there's also details on elinux.org. It's only
>> existed since the 1990s.
> 
> Thanks :) Will try to find it there.

My document of reference is [1]. Although interrupt-map appears
there in the context of PCI, it is in no way specific to a specific
bus.

HTH,

         M.

[1] https://www.openbios.org/data/docs/rec.intmap.d09.pdf
-- 
Jazz is not dead. It just smells funny...