All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [Combo-PATCH] Shared interrupts (final)
Date: Thu, 09 Feb 2006 12:14:26 +0100	[thread overview]
Message-ID: <43EB2412.8040704@domain.hid> (raw)
In-Reply-To: <43EB1741.9080809@domain.hid>

Jan Kiszka wrote:
> Philippe Gerum wrote:
> 
>>Anders Blomdell wrote:
>>
>>
>>>My distinct feeling is that the return value should be a scalar and
>>>not a set!
>>>
>>
>>To sum up, the valid return values are HANDLED, HANDLED | ENABLE (*),
>>HANDLED | CHAINED and CHAINED. It's currently a set because I once
>>thought that the "handled" indication (or lack of) could be a valuable
>>information to gather at nucleus level to detect unhandled RT
>>interrupts. Fact is that we currently don't use this information,
> 
> 
> But it is required for the edge-triggered case to detect when the IRQ
> line was at least shortly released. I guess Dmitry introduced that NOINT
> just because HANDLED equals 0 so far. As I would say HANDLED == !NOINT,
> we could avoid this new flag by just making HANDLED non-zero.
> 

Yes, we could. HANDLED is currently zero only because the nucleus does not care of 
the !handled case, yet.

> 
>>though. IOW, we could indeed define some enum and have a scalar there
>>instead of a set; or we could just leave this as a set, but whine when
>>detecting the invalid ENABLE | CHAINED combination.
> 
> 
> In combination with the change above and some doc improvement ("valid
> combinations are: ..."), I could also live with keeping the flags. The
> advantage were that we wouldn't break existing applications.
> 
> 
>>(*) because the handler does not necessary know how to ->end() the
>>current IRQ at IC level, but Xenomai always does.
>>
> 
> 
> Jan
> 


-- 

Philippe.


  parent reply	other threads:[~2006-02-09 11:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  9:04 [Xenomai-core] [Combo-PATCH] Shared interrupts (final) Dmitry Adamushko
2006-02-07  9:58 ` Wolfgang Grandegger
2006-02-07 17:58   ` Jan Kiszka
2006-02-08  7:26     ` Wolfgang Grandegger
2006-02-08  8:24       ` Jan Kiszka
2006-02-08 10:12         ` Dmitry Adamushko
2006-02-08 10:57     ` Philippe Gerum
2006-02-09  8:30       ` Anders Blomdell
2006-02-09  9:11         ` Jan Kiszka
2006-02-09 10:07           ` Philippe Gerum
2006-02-09  9:59         ` Philippe Gerum
2006-02-09 10:19           ` Jan Kiszka
2006-02-09 11:11             ` Dmitry Adamushko
2006-02-09 15:46               ` [Xenomai-core] More on Shared interrupts Anders Blomdell
2006-02-09 16:39                 ` Jan Kiszka
2006-02-10  8:04                   ` Anders Blomdell
2006-02-10 13:59                 ` [Xenomai-core] " Philippe Gerum
2006-02-11 11:35                   ` Dmitry Adamushko
2006-02-13  7:49                     ` Anders Blomdell
2006-02-13 11:00                       ` Dmitry Adamushko
2006-02-14 17:46                     ` Philippe Gerum
2006-02-16 16:05                 ` [Xenomai-core] " Anders Blomdell
2006-02-09 11:14             ` Philippe Gerum [this message]
2006-02-09 10:43           ` [Xenomai-core] [Combo-PATCH] Shared interrupts (final) Anders Blomdell
2006-02-07 19:24   ` Dmitry Adamushko

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=43EB2412.8040704@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@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.