This section details the Driver Kernel
Interface. Note that most of these functions are identical to Kernel C
API calls, and will in most configurations be wrappers for them. In
non-kernel configurations they will be supported directly by the HAL,
or by code to emulate the required behavior.
This API is defined in the header file
<cyg/hal/drv_api.h>.
Re-enables delivery of interrupts, allowing ISRs to
run. This function decrements the counter maintained by
cyg_drv_isr_lock(), and only re-allows
interrupts when it goes to zero.
Destroy a spinlock that is no longer of use. There should be no
CPUs attempting to claim the lock at the time this function is
called, otherwise the behavior is undefined.
Claim a spinlock, waiting in a busy loop until it is
available. Wherever this is called from, this operation
effectively pauses the CPU until it succeeds. This operations
should therefore be used sparingly, and in situations where
deadlocks/livelocks cannot occur. Also see
cyg_drv_spinlock_spin_intsave().
Clear a spinlock. This clears the spinlock and allows another
CPU to claim it. If there is more than one CPU waiting in
cyg_drv_spinlock_spin() then just one of
them will be allowed to proceed.
TRUE if the spinlock was claimed,
FALSE otherwise.
Level:
ISR
Description:
Try to claim the spinlock without waiting. If the spinlock could
be claimed immediately then TRUE is
returned. If the spinlock is already claimed then the result is
FALSE.
This function behaves exactly like
cyg_drv_spinlock_spin() except that it also
disables interrupts before attempting to claim the lock. The
current interrupt enable state is saved in
*istate. Interrupts remain disabled once
the spinlock had been claimed and must be restored by calling
cyg_drv_spinlock_clear_intsave().
In general, device drivers should use this function to claim and
release spinlocks rather than the
non-_intsave() variants, to ensure proper
exclusion with code running on both other CPUs and this CPU.
This function behaves exactly like
cyg_drv_spinlock_clear() except that it
also restores an interrupt state saved by
cyg_drv_spinlock_spin_intsave(). The
istate argument must have been
initialized by a previous call to
cyg_drv_spinlock_spin_intsave().
Re-enables scheduling of DSRs. This function decrements
the counter incremented by
cyg_drv_dsr_lock(). DSRs are only allowed
to be delivered when the counter goes to zero.
Destroy the mutex pointed to by the
mutex argument. The mutex should be unlocked
and there should be no threads waiting to lock it when this call
in made.
TRUE it the thread has claimed the
lock, FALSE otherwise.
Level:
Thread
Description:
Attempt to lock the mutex pointed to by the
mutex argument. If the mutex is already
locked by another thread then this thread will wait until that
thread is finished. If the result from this function is
FALSE then the thread was broken out of its
wait by some other thread. In this case the mutex will not have
been locked.
TRUE if the mutex has been locked,
FALSE otherwise.
Level:
Thread
Description:
Attempt to lock the mutex pointed to by the
mutex argument without waiting. If the
mutex is already locked by some other thread then this function
returns FALSE. If the function can lock the
mutex without waiting, then TRUE is
returned.
Release all threads waiting on the mutex pointed to by the
mutex argument. These threads will return
from cyg_drv_mutex_lock() with a
FALSE result and will not have claimed the
mutex. This function has no effect on any thread that may have
the mutex claimed.
mutex - mutex to associate with this condition variable
Result:
None
Level:
Thread
Description:
Initialize the condition variable pointed to by the
cond argument. The
mutex argument must point to a mutex with
which this condition variable is associated. A thread may only
wait on this condition variable when it has already locked the
associated mutex. Waiting will cause the mutex to be unlocked,
and when the thread is reawakened, it will automatically claim
the mutex before continuing.
Wait for a signal on the condition variable pointed to by
the cond argument. The thread must have
locked the associated mutex, supplied in
cyg_drv_cond_init(), before waiting on this
condition variable. While the thread waits, the mutex will be
unlocked, and will be re-locked before this function returns. It
is possible for threads waiting on a condition variable to
occasionally wake up spuriously. For this reason it is necessary
to use this function in a loop that re-tests the condition each
time it returns. Note that this function performs an implicit
scheduler unlock/relock sequence, so that it may be used within
an explicit
cyg_drv_dsr_lock()...cyg_drv_dsr_unlock()
structure.
Signal the condition variable pointed to by the cond
argument. If there are any threads waiting on this variable at
least one of them will be awakened. Note that in some
configurations there may not be any difference between this
function and cyg_drv_cond_broadcast().
Create an interrupt object and returns a handle to it. The
object contains information about which interrupt vector to use
and the ISR and DSR that will be called after the interrupt
object is attached to the vector. The interrupt object will be
allocated in the memory passed in the
intr parameter. The interrupt object is
not immediately attached; it must be attached with the
cyg_interrupt_attach() call.
Program the interrupt controller to stop delivery of
interrupts on the given vector. On architectures which implement
interrupt priority levels this may also disable all lower
priority interrupts.
Program the interrupt controller to stop delivery of
interrupts on the given vector. On architectures which implement
interrupt priority levels this may also disable all lower
priority interrupts. This version differs from
cyg_drv_interrupt_mask() in not being
interrupt safe. So in situations where, for example, interrupts
are already known to be disabled, this may be called to avoid
the extra overhead.
Program the interrupt controller to re-allow delivery of
interrupts on the given vector. This
version differs from
cyg_drv_interrupt_unmask() in not being
interrupt safe.
Perform any processing required at the interrupt
controller and in the CPU to cancel the current interrupt
request on the vector. An ISR may also
need to program the hardware of the device to prevent an
immediate re-triggering of the interrupt.
void cyg_drv_interrupt_configure( cyg_vector_t vector,
cyg_bool_t level,
cyg_bool_t up
)
Arguments:
vector - vector to configure
level - level or edge triggered
up - rising/falling edge, high/low level
Result:
None
Level:
ISR
Description:
Program the interrupt controller with the characteristics
of the interrupt source. The level
argument chooses between level- or edge-triggered
interrupts. The up argument chooses
between high and low level for level triggered interrupts or
rising and falling edges for edge triggered interrupts. This
function only works with interrupt controllers that can control
these parameters.
Program the interrupt controller to deliver the given
interrupt at the supplied priority level. This function only
works with interrupt controllers that can control this
parameter.
void cyg_drv_interrupt_set_cpu( cyg_vector_t vector,
cyg_cpu_t cpu
)
Arguments:
vector - interrupt vector to route
cpu - destination CPU
Result:
None
Level:
ISR
Description:
This function causes all interrupts on the given vector to be
routed to the specified CPU. Subsequently, all such interrupts
will be handled by that CPU. This only works if the underlying
hardware is capable of performing this kind of routing. This
function does nothing on a single CPU system.
In multi-processor systems this function returns the id of the
CPU to which interrupts on the given vector are current being
delivered. In single CPU systems this function returns zero.
typedef cyg_uint32 cyg_ISR_t( cyg_vector_t vector,
cyg_addrword_t data
)
Fields:
vector - vector being delivered
data - data value supplied by client
Result:
Bit mask indicating whether interrupt was handled and
whether the DSR should be called.
Description:
Interrupt Service Routine definition. A pointer to a
function with this prototype is passed to
cyg_interrupt_create() when an interrupt
object is created. When an interrupt is delivered the function
will be called with the vector number and the data value that
was passed to cyg_interrupt_create().
The return value is a bit mask containing one or both of the
following bits:
CYG_ISR_HANDLED
indicates that the interrupt was handled by this
ISR. It is a configuration option whether this will
prevent further ISR being run.
CYG_ISR_CALL_DSR
causes the DSR that was passed to
cyg_interrupt_create() to be
scheduled to be called.
typedef void cyg_DSR_t( cyg_vector_t vector,
cyg_ucount32 count,
cyg_addrword_t data
)
Fields:
vector - vector being delivered
count - number of times DSR has been scheduled
data - data value supplied by client
Result:
None
Description:
Deferred Service Routine prototype. A pointer to a
function with this prototype is passed to
cyg_interrupt_create() when an interrupt
object is created. When the ISR requests the scheduling of its
DSR, this function will be called at some later point. In
addition to the vector and
data arguments, which will be the same as
those passed to the ISR, this routine is also passed a
count of the number of times the ISR has
requested that this DSR be scheduled. This counter is zeroed
each time the DSR actually runs, so it indicates how many
interrupts have occurred since it last ran.