- From: Frank Mori Hess <fmhess_at_users.sourceforge.net>
- Date: Tue, 8 Feb 2005 08:07:56 -0500
On Tuesday 08 February 2005 06:23 am, Ian Abbott wrote: > > Could you clarify the restrictions on tasklets in an RT environment? In > my driver, the interrupt source handler callbacks are called from the > hardware interrupt handler, not the tasklet. If it's an RT interrupt, > the channel data would be read or written within a guaranteed period > after the 'scan' trigger. The tasklet is just there for cleaning up > freed handlers. I could clean things up without the tasklet, but it Oh, my mistake. > > I'll investigate having a separate subdevice to handle interrupt > triggers. I'm thinking of a using a 6-channel subdevice with a > "virtual" external trigger that fires when any of the channels on the > channel list fire. The read value would indicate which trigger(s) have > fired. This sort of thing would be much less intuitive to use than the I would like to improve the scheme for supporting externally triggered interrupts in general, but it's not clear to me how yet. -- Frank
Attachments
- application/pgp-signature attachment: stored
Received on 2005-02-08Z13:07:56