From: valmiki <valmikibow@gmail.com>
To: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: helgaas@kernel.org, marc.zyngier@arm.com, arnd@arndb.de,
mark.rutland@arm.com
Subject: Need clarity on PCIe MSI interrupt in device tree
Date: Wed, 4 Jan 2017 08:47:43 +0530 [thread overview]
Message-ID: <2fea5a0c-7410-97fd-91d1-ae6a06ab1a52@gmail.com> (raw)
Hi,
I have confusion on MSI interrupt flags in PCIe documetation.
MSI interrupts are edge triggered, but i see some controllers use
Ex:tegra <0 99 0x4>, here interrupt flags show 0x4 which means level
sensitive as per include/dt-bindings/interrupt-controller/irq.h.
May i know why is it like this, why MSI depicted as level sensitive in
device tree.
Regards,
valmiki
next reply other threads:[~2017-01-04 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 3:17 valmiki [this message]
2017-01-04 8:29 ` Need clarity on PCIe MSI interrupt in device tree Marc Zyngier
2017-01-04 17:28 ` valmiki
2017-01-04 10:05 ` Mark Rutland
2017-01-04 17:29 ` valmiki
2017-01-04 17:39 ` Need clarity on MSI handling in RC driver valmiki
2017-01-04 17:46 ` Marc Zyngier
2017-01-06 2:30 ` valmiki
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=2fea5a0c-7410-97fd-91d1-ae6a06ab1a52@gmail.com \
--to=valmikibow@gmail.com \
--cc=arnd@arndb.de \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.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).