From: Bart Jonkers <jonkersbart@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Xenomai on PXA
Date: Wed, 02 Aug 2006 15:33:05 +0200 [thread overview]
Message-ID: <1154525585.9559.22.camel@domain.hid> (raw)
In-Reply-To: <17616.42011.663899.554796@domain.hid>
On Wed, 2006-08-02 at 15:09 +0200, Gilles Chanteperdrix wrote:
> Detlef Vollmann wrote:
> > > I also added an interrupt handler on a button which is connected to GPIO
> > > pin. The interrupt handler should print something when it is executed.
> > > When I push the button a couple of times nothing happens. So GPIO
> > > interrupts doesn't seems to work.
> > Probably GPIO0 and GPIO1 work.
> > I suspect it's the cascading interrupt that doesn't work.
> > When I played around with an earlier version of ipipe, I found that
> > the IRQ_GPIO_2_80 (IRQ 10 on PXA270) is masked, but never unmasked
> > again.
> >
> > The problem is that for the cascading interrupt you need a special
> > IPIPE handler, and I don't think there is currently one for PXA.
> >
> > How is that done on other machines/architectures?
>
> When looking at the ipipe_enable_pipeline function, we see that
> interrupts management routines are all intercepted by the I-pipe, so the
> cascaded interrupts management routines should be automatically
> intercepted.
>
> In order to have a better understanding of the issue, it would be
> interesting if you could trace the functions that are called on the path
> from the interrupt to the execution of the final handler.
I have tracked and solved the issue. I have looked to the i.MX21 port
and they added some code to the GPIO interrupt handler of the i.MX21.
When IPIPE is active they unmask the interrupt for the GPIO pins at the
end of the handler. I did the same for PXA and my GPIO interrupt problem
is solved. I think that the same is needed for SA-1100.
>
> Re-reading the patch I sent, I also realised that an important part of
> the work is missing: the function gettimeoffset should be changed by the
> patch too. I would be surprised if your problem was related to this,
> though.
What need to be changed in the function gettimeoffset?
Bart
>
next prev parent reply other threads:[~2006-08-02 13:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:02 [Xenomai-core] Xenomai on PXA Danilo Levantesi
2006-07-07 20:32 ` Gilles Chanteperdrix
2006-07-11 6:20 ` Detlef Vollmann
2006-07-11 15:01 ` Stelian Pop
2006-07-12 13:13 ` Bart Jonkers
2006-07-11 15:02 ` Stelian Pop
2006-07-17 16:17 ` Gilles Chanteperdrix
2006-07-17 16:29 ` Philippe Gerum
2006-07-17 16:56 ` Gilles Chanteperdrix
2006-07-31 8:34 ` Bart Jonkers
2006-07-31 9:20 ` Detlef Vollmann
2006-07-31 10:33 ` Bart Jonkers
2006-07-31 11:08 ` Detlef Vollmann
2006-08-02 13:09 ` Gilles Chanteperdrix
2006-08-02 13:33 ` Bart Jonkers [this message]
2006-08-02 13:56 ` Gilles Chanteperdrix
2006-08-02 18:06 ` Gilles Chanteperdrix
2006-08-03 9:12 ` Bart Jonkers
2006-08-03 13:18 ` Gilles Chanteperdrix
2006-08-03 14:56 ` Philippe Gerum
2006-08-03 17:14 ` Gilles Chanteperdrix
2006-08-04 6:10 ` Bart Jonkers
2006-08-04 6:10 ` Detlef Vollmann
2006-08-04 9:04 ` Philippe Gerum
2006-08-04 11:37 ` Gilles Chanteperdrix
2006-08-04 14:52 ` Bart Jonkers
2006-08-13 13:16 ` Gilles Chanteperdrix
2006-09-10 8:56 ` Detlef Vollmann
2006-09-10 12:19 ` Gilles Chanteperdrix
2006-09-10 16:31 ` Detlef Vollmann
2006-09-10 16:37 ` Gilles Chanteperdrix
2006-09-10 19:20 ` Detlef Vollmann
2006-09-10 19:42 ` Gilles Chanteperdrix
2006-08-03 11:23 ` Bart Jonkers
2006-07-17 22:33 ` Danilo Levantesi
-- strict thread matches above, loose matches on Subject: below --
2007-10-17 16:29 Patrick
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=1154525585.9559.22.camel@domain.hid \
--to=jonkersbart@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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.