All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Minazzi <Paolo.Minazzi@mitrol.it>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] rt_intr_wait bug during debugging
Date: Tue, 24 Sep 2013 09:26:13 +0200	[thread overview]
Message-ID: <52413E95.3010003@mitrol.it> (raw)
In-Reply-To: <52408790.3070907@xenomai.org>

Il 23/09/2013 20.25, Gilles Chanteperdrix ha scritto:
> On 09/23/2013 10:48 AM, Paolo Minazzi wrote:
>> Hi to all,
>> the problem arise when I debug an application that uses an external
>> interrupt.
>> Below there is a sample (pseudo) code that show how I can see the problem.
>> The irq stuff is related on my specific machine, so I think it is not
>> important
>> give details about GPIO programming and interrupt clear (CLEAR_IRQ).
> Could you try reproducing this issue with a recent I-pipe patch? Say the
> I-pipe patch for Linux 3.5 or 3.8?
>
>
I see the problem with xenomai 2.5.6, linux kernel 2.6.31.8.
I cannot try with a new i-pipe.

I realize that the issue is very closed to our arm board and our porting 
of xenomai.
I think that timers and tasks related to time are more general, while 
tasks connected to
irq line are more specific to hardware and porting. So it is difficult 
reproduce it.

What I'd like to know if it is normal do it in user space (directly 
programming the registers) both
- enable at every cycle the interrupt on the line
- ack the interrupt

The xenomai example you give in the documentation does not show these 
steps,
maybe because this should be done in kernel space.

Thanks for support,

Regards

Paolo Minazzi


  reply	other threads:[~2013-09-24  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23  8:48 [Xenomai] rt_intr_wait bug during debugging Paolo Minazzi
2013-09-23 18:25 ` Gilles Chanteperdrix
2013-09-24  7:26   ` Paolo Minazzi [this message]
2013-09-24  7:38 ` Philippe Gerum

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=52413E95.3010003@mitrol.it \
    --to=paolo.minazzi@mitrol.it \
    --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.