Home
last modified time | relevance | path

Searched refs:send_cpu_message_lock (Results 1 – 3 of 3) sorted by relevance

/linux/drivers/accel/habanalabs/common/
H A Ddevice.c978 mutex_init(&hdev->send_cpu_message_lock); in device_early_init()
1029 mutex_destroy(&hdev->send_cpu_message_lock); in device_early_fini()
1264 mutex_lock(&hdev->send_cpu_message_lock); in take_release_locks()
1265 mutex_unlock(&hdev->send_cpu_message_lock); in take_release_locks()
H A Dfirmware_if.c423 mutex_lock(&hdev->send_cpu_message_lock); in hl_fw_send_cpu_message()
441 * entries). We lock on it using 'send_cpu_message_lock' which in hl_fw_send_cpu_message()
535 mutex_unlock(&hdev->send_cpu_message_lock); in hl_fw_send_cpu_message()
H A Dhabanalabs.h3268 * @send_cpu_message_lock: enforces only one message in Host <-> CPU-CP queue.
3453 struct mutex send_cpu_message_lock; member