Lines Matching full:driver
37 * infrustracture for switching from external contexts to the driver's context.
38 * This includes also the driver task itself (workqueue in Linux), which invokes the
39 * driver specific handlers in the driver's context.
72 TI_BOOL bContextSwitchRequired; /* Indicate if the driver should switch to its */
174 * Set default setting which indicates if the driver should switch to
200 * This includes their callback function that should be invoked from the driver context
260 * \brief Handle client's switch to driver's context.
263 * It sets the client's Pending flag and requests the driver's task scheduling.
264 * Thus, the client's callback will be called afterwards from the driver context.
288 * If configured to switch context, request driver task scheduling.
289 * Else (context switch not required) call the driver task directly.
306 * \brief The driver task
308 * This function is the driver's main task that always runs in the driver's
309 * single context, scheduled through the OS (the driver's workqueue in Linux).
356 * Called by the driver main when needed to enble/disable a specific event handling.
357 * The Enable function also schedules the driver-task if the specified client is pending.
381 /* If client is pending, schedule driver task */
388 * If configured to switch context, request driver task scheduling.
389 * Else (context switch not required) call the driver task directly.
427 * when handling context transition to driver context.
