All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Blaess <mailist@logilin.fr>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] GPIO Interrupts problem with RTDM
Date: Thu, 24 Jan 2013 17:52:35 +0100	[thread overview]
Message-ID: <510166D3.8050905@logilin.fr> (raw)
In-Reply-To: <201301220306.28220.paul_c@tuxcnc.org>

On 22/01/2013 04:06, Paul wrote:
> On Sunday 20 January 2013, Gilles Chanteperdrix wrote:
>> Yes, this patch is based on 3.5.7 and is used with and without
>> GENERIC_CLOCKEVENTS.
> Short version: Updated my kernel to 3.5.7 and backported the Raspberry
> Pi changes from 3.6.11 and added in the ipipe support. Interrupts are
> not being recognised unless irq_set_irq_type() is called. Digging
> through the rtdm, nucleus, and ipipe code, at no point is
> irq_chip->irq_set_type() called - Also have a problem that none of the
> ipipe_pic_muter fields are set, so __ipipe_enable_irqdesc() & friends
> do nothing.

I'm trying to follow the same steps as you but I still have some 
compilation errors while porting
R-Pi modifications to 3.5.7. (especially arm timer code).

Do you have any available patch against 3.5.7 vanilla kernel ?

I have a working GPIO interrupt rtdm driver with 3.2.21 kernel (Xenomai 
2.6.2) but the interrupt latencies seems terrible (about 20us and 
jiterring up to 150us without any load). To compare with the 7us latency 
I see on a vanilla Linux GPIO interrupt handler.


Regards,

-- 
Christophe


  parent reply	other threads:[~2013-01-24 16:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 15:15 [Xenomai] GPIO Interrupts problem with RTDM Pierre LE COZ
2013-01-18 19:59 ` Gilles Chanteperdrix
2013-01-18 22:11 ` Paul
2013-01-18 23:47   ` Pierre LE COZ
2013-01-19  0:52     ` Paul
2013-01-19 10:41       ` Pierre LE COZ
2013-01-19 12:35         ` Paul
2013-01-19 15:46           ` Pierre LE COZ
2013-01-19 15:49             ` Gilles Chanteperdrix
2013-01-20  0:13             ` Paul
2013-01-20 13:50               ` Gilles Chanteperdrix
2013-01-22  3:06                 ` Paul
2013-01-22  7:51                   ` Gilles Chanteperdrix
2013-01-22  8:40                     ` Gilles Chanteperdrix
2013-01-23 12:14                   ` Gilles Chanteperdrix
2013-01-24 16:52                   ` Christophe Blaess [this message]
2013-01-24 17:12                     ` Paul
2013-01-24 17:38                       ` Christophe Blaess
2013-01-25  9:08                         ` Gilles Chanteperdrix
2013-01-31  2:11                           ` Paul
2013-01-31 19:45                             ` Gilles Chanteperdrix
2013-02-13 12:40                               ` Paul
2013-01-25  9:03                       ` Gilles Chanteperdrix
2013-01-28 12:29                         ` Paul
2013-01-28 17:22                           ` Gilles Chanteperdrix
2013-01-19 12:32   ` Gilles Chanteperdrix

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=510166D3.8050905@logilin.fr \
    --to=mailist@logilin.fr \
    --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.