Lines Matching full:scheduler

236 /* 3945 Tx scheduler registers */
247  * Tx Scheduler
249  * The Tx Scheduler selects the next frame to be transmitted, choosing TFDs
275  * 1)  Scheduler-Ack, in which the scheduler automatically supports a
281  *     In scheduler-ack mode, the scheduler keeps track of the Tx status of
292  * 2)  FIFO (a.k.a. non-Scheduler-ACK), in which each TFD is processed in order.
300  * Driver controls scheduler operation via 3 means:
301  * 1)  Scheduler registers
302  * 2)  Shared scheduler data base in internal 4956 SRAM
313  * the scheduler (especially for queue #4/#9, the command queue, otherwise
318  * Max Tx win size is the max number of contiguous TFDs that the scheduler
331  * 4965 tells driver SRAM address for internal scheduler structs via this reg.
339  * scheduler is not tracking what's happening).
349  * Each Tx queue has a BC CB in host DRAM to support Scheduler-ACK mode.
361  * Scheduler generates requests for only the active channels.
379  * For Scheduler-ACK mode, idx indicates first frame in Tx win.
380  * Initialized by driver, updated by scheduler.
391  *        Scheduler-ACK mode as well, via SCD_QUEUE_STATUS_BITS(x).
396  * Select which queues interrupt driver when scheduler increments
412  *     8: Scheduler-ACK mode (1), non-Scheduler-ACK (i.e. FIFO) mode (0).
415  *     5: Window Size Left; indicates whether scheduler can request
422  * NOTE:  If enabling Scheduler-ACK mode, chain mode should also be enabled
439  * 4965 internal SRAM structures for scheduler, shared with driver ...
450  * Driver reads base address of this scheduler area from SCD_SRAM_BASE_ADDR.
462  *  0-06:  Max Tx win size for Scheduler-ACK.  Driver should init to 64.
493  * When queue is in Scheduler-ACK mode, frames placed in a that queue must be
497  * mappings, one for each of the 16 queues.  If queue is not in Scheduler-ACK
520 /*********************** END TX SCHEDULER *************************************/