From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Marc Zyngier <maz@kernel.org>,
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>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: property: Add device link support for interrupts
Date: Wed, 20 Jan 2021 10:53:23 +0100 [thread overview]
Message-ID: <CAMuHMdUpZELgL4qUCs1VH0UUeckpTwqYLrMy2ETPzrpuUwkLnQ@mail.gmail.com> (raw)
In-Reply-To: <20201218210750.3455872-1-saravanak@google.com>
Hi Saravana,
On Fri, Dec 18, 2020 at 10:11 PM Saravana Kannan <saravanak@google.com> wrote:
> Add support for creating device links out of interrupts property.
>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Kevin Hilman <khilman@baylibre.com>
> Signed-off-by: Saravana Kannan <saravanak@google.com>
Thanks for your patch!
This does not seem to add all links. I see links being created to the
secondary interrupt controller (e61c0000 "renesas,irqc"), but not to
the primary interrupt controller (GIC)
Which is good, as the GIC driver is not a platform_driver, and thus
creating links would break everything ;-)
BTW, I'd _love_ the GIC driver to be a platform_driver, as the GIC is
part of a power/and or clock domain on Renesas SoCs...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-01-20 11:01 UTC|newest]
Thread overview: 19+ 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
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 [this message]
2021-01-20 10:04 ` Marc Zyngier
2021-01-20 14:28 ` Geert Uytterhoeven
2021-01-20 17:15 ` Saravana Kannan
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=CAMuHMdUpZELgL4qUCs1VH0UUeckpTwqYLrMy2ETPzrpuUwkLnQ@mail.gmail.com \
--to=geert@linux-m68k.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=maz@kernel.org \
--cc=robh+dt@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 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).