Files | |
file | intr.c |
This file is part of the Xenomai project. | |
Functions | |
int | rt_intr_create (RT_INTR *intr, const char *name, unsigned irq, rt_isr_t isr, rt_iack_t iack, int mode) |
Create an interrupt object from kernel space. | |
int | rt_intr_delete (RT_INTR *intr) |
Delete an interrupt object. | |
int | rt_intr_enable (RT_INTR *intr) |
Enable an interrupt object. | |
int | rt_intr_disable (RT_INTR *intr) |
Disable an interrupt object. | |
int | rt_intr_inquire (RT_INTR *intr, RT_INTR_INFO *info) |
Inquire about an interrupt object. | |
int | rt_intr_create (RT_INTR *intr, const char *name, unsigned irq, int mode) |
Create an interrupt object from user-space. | |
int | rt_intr_wait (RT_INTR *intr, RTIME timeout) |
Wait for the next interrupt. | |
int | rt_intr_bind (RT_INTR *intr, const char *name, RTIME timeout) |
Bind to an interrupt object. | |
static int | rt_intr_unbind (RT_INTR *intr) |
Unbind from an interrupt object. |
|
Bind to an interrupt object. This user-space only service retrieves the uniform descriptor of a given Xenomai interrupt object identified by its IRQ number. If the object does not exist on entry, this service blocks the caller until an interrupt object of the given number is created. An interrupt is registered whenever a kernel-space task invokes the rt_intr_create() service successfully for the given IRQ line.
Environments: This service can be called from:
Rescheduling: always unless the request is immediately satisfied or timeout specifies a non-blocking operation.
|
|
Create an interrupt object from user-space. Initializes and associates an interrupt object with an IRQ line from a user-space application. In this mode, the basic principle is to define some interrupt server task which routinely waits for the next incoming IRQ event through the rt_intr_wait() syscall. When an interrupt occurs on the given irq line, any task pending on the interrupt object through rt_intr_wait() is imediately awaken in order to deal with the hardware event. The interrupt service code may then call any Xenomai service available from user-space.
Environments: This service can be called from:
Rescheduling: possible.
|
|
Create an interrupt object from kernel space. Initializes and associates an interrupt object with an IRQ line. In kernel space, interrupts are immediately notified to a user-defined handler or ISR (interrupt service routine). When an interrupt occurs on the given irq line, the ISR is fired in order to deal with the hardware event. The interrupt service code may call any non-suspensive Xenomai service. Upon receipt of an IRQ, the ISR is immediately called on behalf of the interrupted stack context, the rescheduling procedure is locked, and the interrupt source is masked at hardware level. The status value returned by the ISR is then checked for the following values:
In addition, one of the following bits may be set by the ISR : NOTE: use these bits with care and only when you do understand their effect on the system. The ISR is not encouraged to use these bits in case it shares the IRQ line with other ISRs in the real-time domain.
A count of interrupt receipts is tracked into the interrupt descriptor, and reset to zero each time the interrupt object is attached. Since this count could wrap around, it should be used as an indication of interrupt activity only.
Environments: This service can be called from:
Rescheduling: possible.
|
|
Delete an interrupt object. Destroys an interrupt object. An interrupt exists in the system since rt_intr_create() has been called to create it, so this service must be called in order to destroy it afterwards. Any user-space task which might be currently pending on the interrupt object through the rt_intr_wait() service will be awaken as a result of the deletion, and return with the -EIDRM status.
Environments: This service can be called from:
Rescheduling: possible. |
|
Disable an interrupt object. Disables the hardware interrupt line associated with an interrupt object. This operation invalidates further interrupt requests from the given source until the IRQ line is re-enabled anew through rt_intr_enable().
Environments: This service can be called from:
Rescheduling: never. |
|
Enable an interrupt object. Enables the hardware interrupt line associated with an interrupt object. Over Adeos-based systems which mask and acknowledge IRQs upon receipt, this operation is necessary to revalidate the interrupt channel so that more interrupts from the same source can be notified.
Environments: This service can be called from:
Rescheduling: never. |
|
Inquire about an interrupt object. Return various information about the status of a given interrupt object.
Environments: This service can be called from:
Rescheduling: never. |
|
Unbind from an interrupt object. This user-space only service unbinds the calling task from the interrupt object previously retrieved by a call to rt_intr_bind().
Rescheduling: never. |
|
Wait for the next interrupt. This user-space only call allows the current task to suspend execution until the associated interrupt event triggers. The priority of the current task is raised above all other Xenomai tasks - except those also undergoing an interrupt or alarm wait (see rt_alarm_wait()) - so that it would preempt any of them under normal circumstances (i.e. no scheduler lock). Interrupt receipts are logged if they cannot be delivered immediately to some interrupt server task, so that a call to rt_intr_wait() might return immediately if an IRQ is already pending on entry of the service.
Environments: This service can be called from:
Rescheduling: always, unless an interrupt is already pending on entry.
|