From: Marc Zyngier <maz@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Frank Rowand <frowand.list@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
Android Kernel Team <kernel-team@android.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: property: Add device link support for interrupts
Date: Thu, 07 Jan 2021 17:17:40 +0000 [thread overview]
Message-ID: <29319d4bd3c6f8a19a6f800aff0f8f93@kernel.org> (raw)
In-Reply-To: <CAGETcx8D6Q7XojOnRCPNAZWcxhNt5ebFCp6gyh-cuKeaKfS2Bw@mail.gmail.com>
On 2021-01-07 17:08, Saravana Kannan wrote:
> On Thu, Jan 7, 2021 at 8:48 AM Rob Herring <robh@kernel.org> wrote:
>>
>> On Wed, Jan 6, 2021 at 6:26 PM Saravana Kannan <saravanak@google.com>
>> wrote:
>> >
>> > On Wed, Jan 6, 2021 at 10:52 AM Saravana Kannan <saravanak@google.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...
next prev parent reply other threads:[~2021-01-07 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 21:07 [PATCH] of: property: Add device link support for interrupts Saravana Kannan
2020-12-21 9:30 ` Marc Zyngier
2020-12-31 21:12 ` Rob Herring
2021-01-02 11:36 ` Marc Zyngier
2021-01-06 18:52 ` Saravana Kannan
2021-01-07 1:25 ` Saravana Kannan
2021-01-07 16:47 ` Rob Herring
2021-01-07 17:08 ` Saravana Kannan
2021-01-07 17:17 ` Marc Zyngier [this message]
2021-01-07 18:39 ` Rob Herring
2021-01-07 19:09 ` Saravana Kannan
2021-01-07 19:33 ` Rob Herring
2021-01-07 23:13 ` Saravana Kannan
2021-01-08 3:35 ` Rob Herring
2021-01-08 4:34 ` Saravana Kannan
2021-01-20 9:53 ` Geert Uytterhoeven
2021-01-20 10:04 ` Marc Zyngier
2021-01-20 14:28 ` Geert Uytterhoeven
2021-01-20 17:15 ` Saravana Kannan
-- strict thread matches above, loose matches on Subject: below --
2020-12-19 6:19 kernel test robot
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=29319d4bd3c6f8a19a6f800aff0f8f93@kernel.org \
--to=maz@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.