From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Masahiro Yamada
<yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: interrupts or interrupts-extended ?
Date: Thu, 30 Apr 2015 09:37:19 +0200 [thread overview]
Message-ID: <3035159.qyhQB5YNxD@wuerfel> (raw)
In-Reply-To: <CAK7LNATcFzCV_3uaOnRDHLb=A+TPPDUeAoH_1QTUZDxYAB7VDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thursday 30 April 2015 14:57:19 Masahiro Yamada wrote:
> Hello, device tree folks,
>
>
> Can I ask a little piece of advice?
>
> Which is a preferred way for specifying an interrupt property,
> interrupt-parent & interrupts, or interrupts-extended ?
>
>
> There is only one interrupt controller on my SoC,
> so I think either should work enough for me.
>
interrupts is well-understood by more people, I would pick that one normally,
unless there is a need.
The main purpose of interrupts-extended is to allow one device to have
multiple interrupts that are handled by different controllers, without
introducing a (more complex) interrupt-map property in the parent.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-30 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 5:57 interrupts or interrupts-extended ? Masahiro Yamada
[not found] ` <CAK7LNATcFzCV_3uaOnRDHLb=A+TPPDUeAoH_1QTUZDxYAB7VDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-30 7:37 ` Arnd Bergmann [this message]
2015-05-07 4:19 ` Masahiro Yamada
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=3035159.qyhQB5YNxD@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org \
/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