All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Bob Feretich <bob.feretich@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RTDM driver structure - an update
Date: Tue, 10 Aug 2010 23:41:19 +0200	[thread overview]
Message-ID: <4C61C77F.1000901@domain.hid> (raw)
In-Reply-To: <4C61A1F8.7080901@domain.hid>

Bob Feretich wrote:
>   Comments inline..
> 
> On 8/10/2010 6:18 AM, Gilles Chanteperdrix wrote:
>> ...snipped...
>> The RTDM_IRQTYPE_EDGE is documented in RTDM API documentation: "Mark IRQ
>> as edge-triggered, relevant for correct handling of shared
>> edge-triggered IRQs. " Here:
>> http://www.xenomai.org/documentation/xenomai-2.5/html/api/group__rtdmirq.html
> The above quotation is the full extent of the documentation. The driver 
> authors (we) ask the question, "Should I include this flag when I call 
> rtdm_irq_request()?" The documentation leaves the answer ambiguous in 
> the case where the RTDM_IRQTYPE_SHARED flag is not coded.
> 
> It also creates confusion. We assume that RTDM_IRQTYPE_EDGE will cause 
> hardware to be configured similar to request_irq().We knows that the 
> specification of RTDM_IRQTYPE_EDGE is insufficient.  Normally we need to 
> specify which edge is to cause the interrupt. We question whether 
> specifying RTDM_IRQTYPE_EDGE will cause our ISR to be entered on both 
> rising and falling edges.

Yes, the doc is not perfect, but in this case, I find the sentence
unambiguous, this flag is only relevant for shared irqs. And Xenomai is
free software, it means that:
- in case of doubt you may have a look at the code;
- we accept documentation patches.

> 
> The essence of this e-mail discussion eventually needs to be added to 
> the rtdm_irq_request() documentation.

I agree that we should try and improve the documentation. But in the
rtdm_irq_request case, it is even the interface which we should improve
by adding bits for setting the hardware, and when we are done, the
documentation work will be much simpler.

-- 
					    Gilles.


      reply	other threads:[~2010-08-10 21:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05  2:49 [Xenomai-help] RTDM driver structure Bob Feretich
2010-08-05  7:07 ` Gilles Chanteperdrix
2010-08-05 18:57   ` Bob Feretich
2010-08-05 19:27     ` Gilles Chanteperdrix
2010-08-07  2:22   ` [Xenomai-help] RTDM driver structure - an update Bob Feretich
2010-08-08  9:36     ` Everett Wang
2010-08-08 12:08       ` Gilles Chanteperdrix
2010-08-08 14:32         ` Everett Wang
2010-08-10  0:56       ` Bob Feretich
2010-08-10  7:43         ` Guenter Ebermann
2010-08-10  9:08           ` Bob Feretich
2010-08-10 13:33             ` Gilles Chanteperdrix
2010-08-10 13:41               ` Philippe Gerum
2010-08-10 13:18         ` Gilles Chanteperdrix
2010-08-10 19:01           ` Bob Feretich
2010-08-10 21:41             ` Gilles Chanteperdrix [this message]

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=4C61C77F.1000901@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=bob.feretich@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.