From: avictor.za@gmail.com (Andrew Victor)
To: linux-arm-kernel@lists.infradead.org
Subject: Interrupt registering for PIO problem in ATMEL chips
Date: Mon, 22 Feb 2010 22:26:59 +0200 [thread overview]
Message-ID: <cd73a99e1002221226i5d47e60cs4b99cb911000cd52@mail.gmail.com> (raw)
In-Reply-To: <17E4CABDDEE0BC4A9F40814378DEC0CB21EB65@BLR-EC-MBX03.wipro.com>
hi,
> Also, PIOs can not distinguish between inputs and interrupts, as they
> treat everything as inputs.
Not quite. Interrupts in GPIO input pins are optional.
> Now, my problem is I am writing this keypad driver, which is connected
> to PIOA.
There are existing GPIO-driven keypad drivers - have a look in
drivers/input/keyboard/.
> The PIOA is connected to pin 2 of AIC, but then I can not install the
> handler for pin2, It fails saying error -22 ( resource not available).
> I also don't know, what I can do even if I get to install the handler
> for PIO.
You request the interrupt only for the specific GPIO pin(s) you're
using. You don't request all PIOA interrupts.
ie, do the following:
request_irq(AT91_PIN_PA2, ...)
Regards,
Andrew Victor
next prev parent reply other threads:[~2010-02-22 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 8:36 Interrupt registering for PIO problem in ATMEL chips biswa.nayak at wipro.com
2010-02-22 20:26 ` Andrew Victor [this message]
2010-02-23 6:07 ` Hemanth V
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=cd73a99e1002221226i5d47e60cs4b99cb911000cd52@mail.gmail.com \
--to=avictor.za@gmail.com \
--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 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).