Lines Matching full:user
306 * over the last period specified by the user.
353 * used by the user.
355 * free to be used by the user.
356 * @dram_size: The DRAM size that is available to the user.
357 * @sram_size: The SRAM size that is available to the user.
359 * is needed so the user can what is the size of the h/w events
365 * @first_available_interrupt_id: The first available interrupt ID for the user
366 * to be used when it works with user interrupts.
643 * User allocated CB is a command buffer allocated by the user, via malloc
644 * (or similar). After allocating the CB, the user invokes “memory ioctl”
645 * to map the user memory into a device virtual address. The user provides
709 * This set the signals range that the user want to wait for
711 * e.g if the signals range is 20, and user don't want
873 * In case of wait for multi CS hold a user pointer to
884 /* User address for completion comparison.
982 * and not already mapped. The user should check the
1000 * and not already mapped. The user should check the
1014 * returned to the user and will be used to mmap the
1114 /* Two address ranges that the user can request to filter */
1160 * Pointer to user input structure.
1164 /* Pointer to user output structure */
1166 /* Size of user input structure */
1168 /* Size of user output structure */
1188 * The user calls this IOCTL with an opcode that describes the required
1189 * information. The user should supply a pointer to a user-allocated memory
1192 * The user supplies the maximum amount of size to copy into the user's memory,
1209 * When creating a new CB, the IOCTL returns a handle of it, and the user-space
1213 * device's MMU, and thus its memory should be mapped. In these cases, user can
1216 * and won't be returned to user.
1225 * To submit work to the device, the user need to call this IOCTL with a set
1227 * Each JOB will be enqueued on a specific queue, according to the user's input.
1233 * (or if its the first CS for this context). The user can also order the
1241 * For jobs on external queues, the user needs to create command buffers
1243 * internal queues, the user needs to prepare a "command buffer" with packets
1249 * relevant queues. Therefore, the user mustn't assume the CS has been completed
1252 * Upon successful enqueue, the IOCTL returns a sequence number which the user
1259 * Even though the sequence number increments per CS, the user can NOT
1261 * with sequence number N-1 also finished. The user can make this assumption if
1271 * The user can call this IOCTL with a handle it received from the CS IOCTL
1272 * to wait until the handle's CS has finished executing. The user will wait
1273 * inside the kernel until the CS has finished or until the user-requested
1283 * that the user process received
1286 * ENODEV - The device wants to do hard-reset (so user need to close FD)
1307 * This IOCTL allows the user to map host memory to the device MMU
1309 * For host memory, the IOCTL doesn't allocate memory. The user is supposed
1310 * to allocate the memory in user-space (malloc/new). The driver pins the
1314 * There is an option for the user to specify the requested virtual address.
1324 * This IOCTL allows the user to get debug traces from the chip.
1326 * Before the user can send configuration requests of the various
1331 * Once a user set the device into debug mode, the driver won't allow other
1333 * opened on the device, the driver won't allow any user to debug the device.
1335 * For each configuration request, the user needs to provide the register index
1338 * Once the user has finished using the debug/profile engines, he should
1341 * The driver can decide to "kick out" the user if he abuses this interface.