From: Guillaume Knispel <gknispel@proformatique.com>
To: Baojun Wang <wangbj.ml@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Configure CPM2 PORTC pin (PC9) for external interrupt?
Date: Sat, 15 Aug 2009 00:39:04 +0200 [thread overview]
Message-ID: <20090815003904.5378cb35@xilun.lan.proformatique.com> (raw)
In-Reply-To: <17dc9c530908140727l6423bebawaed8808f195d4d20@mail.gmail.com>
On Fri, 14 Aug 2009 22:27:39 +0800
Baojun Wang <wangbj.ml@gmail.com> wrote:
> I need to configure CPM2 PORTC pin (PC9) for external interrupt, when I
> read the MPC8555ERM.pdf and cpm2-pic.c, I find that PC9 interrupt number is
> 56, and I request the IRQ in this way:
>
> hw_irq = 56;
> virq = irq_create_mapping(cpm2_host, hw_irq);
>
> reqeust_irq(virq, ...);
>
> I can request the irq successfully, but the interrupt is never generated
> (ISR is not called) to the PC9 pins, even though the hardware said an
> interrupt was raised. (the hardware have a register with a special bit)
>
> Should I configure the cpm2 io port first to allow PORTC interrupt? I have
> read the cpm2 io port documentation, and I initialize the PC9 as:
>
> PPARC[pc9_bit] = 0; /* for general purpose IO, not dedicated */
> PSORC[pc9_bit] = 0; /* no special option */
> PDIRC[pc9_bit] = 0; /* for both input/output */
>
> Am I missing some thing? Any suggestion will be greatly appreciated.
Hi,
Have a look on commit 7f3ea17f316577e31db868f720ac575c74d20163, which
fixes a linux bug about Port C interrupts
Also note that the 8555 have the same issue that the 8272 about
PC2 / PC3 missing which shifts other vectors, but I don't know if 56
for PC9 take that into account.
PS: in the future make sure to include your Linux version number, so we
know if an issue apply or not.
--
Guillaume KNISPEL
next prev parent reply other threads:[~2009-08-14 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 14:27 Configure CPM2 PORTC pin (PC9) for external interrupt? Baojun Wang
2009-08-14 22:39 ` Guillaume Knispel [this message]
2009-08-15 4:32 ` Baojun Wang
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=20090815003904.5378cb35@xilun.lan.proformatique.com \
--to=gknispel@proformatique.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=wangbj.ml@gmail.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).