Searched refs:doorbell (Results 1 – 11 of 11) sorted by relevance
71 uint32_t doorbell; member80 uint32_t doorbell; member
30 bool "Support interrupt based ivshmem (doorbell version)"32 This will enable support of ivshmem-doorbell, i.e. the interrupt
364 uint32_t doorbell = IVSHMEM_GEN_DOORBELL(peer_id, vector); in ivshmem_api_int_peer() local379 doorbell_reg = ®s->doorbell; in ivshmem_api_int_peer()386 doorbell_reg = ®s->doorbell; in ivshmem_api_int_peer()388 *doorbell_reg = doorbell; in ivshmem_api_int_peer()
21 thus to be interrupted as well itself (ivshmem-doorbell).29 Zephyr supports both versions: plain and doorbell. Ivshmem driver can be built32 doorbell version.34 Because the doorbell version uses MSI-X vectors to support notification vectors,
9 Driver for ESP32 mailbox based on its doorbell mechanism.
1 .. zephyr:code-sample:: ivshmem-doorbell2 :name: IVSHMEM doorbell31 Building ivshmem-doorbell is as follows:37 :zephyr-app: samples/drivers/virtualization/ivshmem/doorbell47 :zephyr-app: samples/drivers/virtualization/ivshmem/doorbell57 :zephyr-app: samples/drivers/virtualization/ivshmem/doorbell
107 Shared memory and doorbell-based transport117 transport API, which is implemented by the shared memory and doorbell-based124 …hyr rings request doorbell. If in ``PRE_KERNEL_1`` or ``PRE_KERNEL_2`` phase start polling for rep…125 …red memory area, processes it, writes the reply back to the same area and rings the reply doorbell.199 /* compatible for shared memory and doorbell-based transport */
62 PAX DMA hardware ring operation in doorbell mode
504 qpair->sq_tdbl_off = nvme_mmio_offsetof(doorbell) + in nvme_cmd_qpair_setup()506 qpair->cq_hdbl_off = nvme_mmio_offsetof(doorbell) + in nvme_cmd_qpair_setup()
48 } doorbell[1]; member
353 -device ivshmem-doorbell,vectors=${CONFIG_IVSHMEM_MSI_X_VECTORS},chardev=ivshmem
