From: Philippe Gerum <rpm@xenomai.org>
To: Detlef Vollmann <dv@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Xenomai on PXA
Date: Fri, 04 Aug 2006 11:04:01 +0200 [thread overview]
Message-ID: <1154682242.4983.5.camel@domain.hid> (raw)
In-Reply-To: <44D2E4DC.63409EBA@vollmann.ch>
On Fri, 2006-08-04 at 08:10 +0200, Detlef Vollmann wrote:
> Gilles Chanteperdrix wrote:
> > Philippe Gerum wrote:
> > > Fixing the I-pipe is the way to go, definitely. If I understand this
> > > correctly, the best way to handle the demux case is to implement an
> > > I-pipe variant of the demultiplexing code currently available in
> > > pxa_gpio_demux_handler(), which would be called from __ipipe_grab_irq()
> > > when processing the multiplexed interrupt channel.
> > >
> > > The I-pipe-specific demux code would then log the decoded IRQ by a call
> > > to __ipipe_handle_irq() instead of running the root handler directly
> > > (i.e. desc_handle_irq), which would in turn preserve the ability to
> > > "wire" GPIO interrupts and also handle IRQ stickiness issues.
> This was also my first idea. But after a bit of musing on that
> idea, I'm not really sure that this is the best way to go.
> We're talking here about more than 100 bits that have to be tested
> one after the other (on PXA270, it's 116, though the actual code
> checks 126 bits), and even on a fast CPU this takes some time.
>
> So I've thought about a way to register a GPIO-IRQ into I-pipe
> that gets checked directly under I-pipe, while all other GPIOs
> are only checked and handled in the domain that handles the
> original multiplexing IRQ.
> But I have to admit that I have no idea how to implement that...
>
Provided that every IRQ notification goes through __ipipe_grab_irq,
including the GPIO_2_x one, then you just need to check for irq ==
GPIO_2_x in the latter routine and proceed to the demultiplexing only in
this case. No?
> [snip]
> > +++ linux-2.6.16.5-tcl1-ipipe/arch/arm/mach-pxa/irq.c 2006-08-03 19:04:52.000000000 +0200
>
> > +#ifdef CONFIG_IPIPE
> > +void __ipipe_mach_demux_irq(unsigned irq, struct pt_regs *regs)
>
> > + __ipipe_handle_irq(irq, regs);
> Just to check: this only marks the interrupt, but not actually
> handles it, doesn't it?
>
> Detlef
>
--
Philippe.
next prev parent reply other threads:[~2006-08-04 9:04 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
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 [this message]
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=1154682242.4983.5.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=dv@domain.hid \
--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.