From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: [MPC5200] using GPT's for interrupts
Date: Fri, 15 Jun 2012 14:58:10 +0200 (CEST) [thread overview]
Message-ID: <1751605717.59698.1339765090606.JavaMail.ngmail@webmail13.arcor-online.net> (raw)
Hi all,
I currently try to use a MPC5200B GPT as interrupt source, which according to the comment at the start of arch/powerpc/platforms/52xx/mpc52xx_gpt.c is possible if the "interrupt-controller" and "#interrupt-cells = < 1 >" properties are added to the device tree node.
Apparently, /some/ work is done during startup, as I can see in the boot log:
[ 0.438623] gpiochip_find_base: found new base at 251
[ 0.444202] mpc52xx-gpt f0000650.timer: mpc52xx_gpt_irq_setup() complete. virq=78
In my driver, I identify the GPT node, call irq_of_parse_and_map() to get the irq number (which succeeds, with the same number as above), but unfortunately request_irq() or devm_request_irq() for this irq fail with error -22. I tracked the failed call down to request_threaded_irq() which ejects because irq_settings_can_request(desc) returns false.
Before digging deeper into the code, maybe someone can tell me what I missed... I'm using kernel 3.2.16.
Thanks in advance,
Albrecht.
reply other threads:[~2012-06-15 12:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1751605717.59698.1339765090606.JavaMail.ngmail@webmail13.arcor-online.net \
--to=albrecht.dress@arcor.de \
--cc=linuxppc-dev@lists.ozlabs.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