[Xenomai-help] RTDM driver structure

[Bob Feretich <bob.feretich@domain.hid>]

  I want to verify that my understanding of the RTDM driver structure is 
correct.

My driver is created as a module that is loaded by Linux insmod. Given 
that...

My module_init routine (and module_exit)...
*  is executed in the Linux driver context.
*  should use Linux spin locks and events instead of rt_locks and events.
*  can call rtdm_irq_request (rtrm_irq_free) to register my interrupt 
handlers
       for rt interrupts.
*  can call rtdm_device_register (rt_dm_device_unregister) to register 
my rt device.
*  can call Linux omap dm_timer routines to reserve general purpose timers,
       so that Linux will not give my timers to others. (these routines 
call Linux locks)

My driver's open_nrt close_nrt entry points... (open_rt & close_rt are 
deprecated)
*  are executed in the caller's Linux user context, if the caller is a 
standard Linux
       user process.
*  are executed in the caller's Xenomai user context (secondary mode), 
if the caller
       is a rt user process.
*  can use Linux spin locks and events instead of rt_locks and events, 
if I know
       that protection is not needed from rt tasks and interrupt handlers.
*  should use rt locks and events, if protection is needed from rt tasks 
and
       interrupt handlers.

My driver's ioctl_rt, read_rt, and write_rt entry points...
*  are executed in the caller's Xenomai user context (primary mode), if 
the caller
       is a rt user process running in primary mode.
*  are executed in the caller's Xenomai user context (secondary mode), 
if the caller
       is a rt user process running in secondary mode.
*  must use rt locks and events.

My driver's ioctl_nrt, read_nrt, and write_nrt entry points...
*  are executed in the caller's Linux user context, if the caller is a 
standard
       Linux user process.
*  I should use rt locks and events, for protection from rt tasks and
       interrupt handlers.

My driver's rt interrupt handler entry points...
*  are executed in the Xenomai interrupt context.
*  must use rt locks and events.

Is the above correct?

The OMAP3 chip has a collection of hardware timers that must be shared 
between the Linux and Xenomai environments. I want to allocate/reserve 5 
timers for my use in the real time environment for the creation of pulse 
width modulation output signals, but the rest of the timers should be 
available for general Linux use. Being able to call omap dm_timer 
routines in the module_init and module_exit routines make this much easier.

Regards,
Bob Feretich