From: rvaswani@codeaurora.org (rvaswani at codeaurora.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [DT] API to determine if interrupt is PPI or SPI ?
Date: Thu, 26 Jul 2012 12:18:41 -0700 (PDT) [thread overview]
Message-ID: <53a41d02c4c4c24bdab47667183891bf.squirrel@www.codeaurora.org> (raw)
Hello,
We can specify the interrupt information in the device tree using the arm
gic convention.
Is there an API to read directly the 1st cell and determine if an
interrupt is a PPI or a SPI ? This information is directly relevant to the
driver because it needs to call request_irq or request_percpu_irq based on
this data.
How should this be done ideally ?
Thanks,
Rohit
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
WARNING: multiple messages have this Message-ID (diff)
From: rvaswani@codeaurora.org
To: devicetree-discuss@lists.ozlabs.org, davidb@codeaurora.org,
grant.likely@secretlab.ca
Cc: linux-arm-kernel@lists.infradead.org
Subject: [DT] API to determine if interrupt is PPI or SPI ?
Date: Thu, 26 Jul 2012 12:18:41 -0700 (PDT) [thread overview]
Message-ID: <53a41d02c4c4c24bdab47667183891bf.squirrel@www.codeaurora.org> (raw)
Hello,
We can specify the interrupt information in the device tree using the arm
gic convention.
Is there an API to read directly the 1st cell and determine if an
interrupt is a PPI or a SPI ? This information is directly relevant to the
driver because it needs to call request_irq or request_percpu_irq based on
this data.
How should this be done ideally ?
Thanks,
Rohit
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
next reply other threads:[~2012-07-26 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 19:18 rvaswani at codeaurora.org [this message]
2012-07-26 19:18 ` [DT] API to determine if interrupt is PPI or SPI ? rvaswani
2012-07-27 12:33 ` Rob Herring
2012-07-27 12:33 ` Rob Herring
2012-07-27 13:09 ` Will Deacon
2012-07-27 13:09 ` Will Deacon
2012-07-27 20:00 ` rvaswani at codeaurora.org
2012-07-27 20:00 ` rvaswani
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=53a41d02c4c4c24bdab47667183891bf.squirrel@www.codeaurora.org \
--to=rvaswani@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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 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.