Lines Matching full:user
92 * over the last period specified by the user.
334 * and not already mapped. The user should check the
352 * and not already mapped. The user should check the
439 /* Two address ranges that the user can request to filter */
485 * Pointer to user input structure.
489 /* Pointer to user output structure */
491 /* Size of user input structure */
493 /* Size of user output structure */
513 * The user calls this IOCTL with an opcode that describes the required
514 * information. The user should supply a pointer to a user-allocated memory
517 * The user supplies the maximum amount of size to copy into the user's memory,
534 * When creating a new CB, the IOCTL returns a handle of it, and the user-space
544 * To submit work to the device, the user need to call this IOCTL with a set
546 * Each JOB will be enqueued on a specific queue, according to the user's input.
552 * (or if its the first CS for this context). The user can also order the
560 * For jobs on external queues, the user needs to create command buffers
562 * internal queues, the user needs to prepare a "command buffer" with packets
568 * relevant queues. Therefore, the user mustn't assume the CS has been completed
571 * Upon successful enqueue, the IOCTL returns a sequence number which the user
578 * Even though the sequence number increments per CS, the user can NOT
580 * with sequence number N-1 also finished. The user can make this assumption if
590 * The user can call this IOCTL with a handle it received from the CS IOCTL
591 * to wait until the handle's CS has finished executing. The user will wait
592 * inside the kernel until the CS has finished or until the user-requeusted
599 * that the user process received
602 * ENODEV - The device wants to do hard-reset (so user need to close FD)
624 * This IOCTL allows the user to map host memory to the device MMU
626 * For host memory, the IOCTL doesn't allocate memory. The user is supposed
627 * to allocate the memory in user-space (malloc/new). The driver pins the
631 * There is an option for the user to specify the requested virtual address.
641 * This IOCTL allows the user to get debug traces from the chip.
643 * Before the user can send configuration requests of the various
648 * Once a user set the device into debug mode, the driver won't allow other
650 * opened on the device, the driver won't allow any user to debug the device.
652 * For each configuration request, the user needs to provide the register index
655 * Once the user has finished using the debug/profile engines, he should
658 * The driver can decide to "kick out" the user if he abuses this interface.