Home
last modified time | relevance | path

Searched refs:session (Results 1 – 2 of 2) sorted by relevance

/rockchip-linux_mpp/osal/driver/
H A Dmpp_server.c82 MppDevSession *session; member
269 MppDevSession *session = NULL; in process_task() local
292 session = task->session; in process_task()
309 batch->batch_id, task->batch_slot_id, session->client); in process_task()
310 mpp_mutex_cond_lock(&session->cond_lock); in process_task()
311 session->task_done++; in process_task()
312 mpp_mutex_cond_signal(&session->cond_lock); in process_task()
313 mpp_mutex_cond_unlock(&session->cond_lock); in process_task()
314 if (session->ctx && session->ctx->dev_cb) in process_task()
315 mpp_callback(session->ctx->dev_cb, NULL); in process_task()
[all …]
/rockchip-linux_mpp/doc/design/
H A D2.kernel_driver.txt22 | session A | | session B | | session C |
60 The driver uses session as communication channel. Each userspace client (client)
61 will have a kernel session. Client will commit tasks to session. Then hardware
66 link to both session waiting list and service waiting list. Then service will
69 session done list. Finally client will get the finished task from session.