Searched refs:doorbell (Results 1 – 9 of 9) sorted by relevance
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,
70 uint32_t doorbell; member79 uint32_t doorbell; member
30 bool "Support interrupt based ivshmem (doorbell version)"32 This will enable support of ivshmem-doorbell, i.e. the interrupt
333 uint32_t doorbell = IVSHMEM_GEN_DOORBELL(peer_id, vector); in ivshmem_api_int_peer() local348 doorbell_reg = ®s->doorbell; in ivshmem_api_int_peer()355 doorbell_reg = ®s->doorbell; in ivshmem_api_int_peer()357 *doorbell_reg = doorbell; in ivshmem_api_int_peer()
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
62 PAX DMA hardware ring operation in doorbell mode
501 qpair->sq_tdbl_off = nvme_mmio_offsetof(doorbell) + in nvme_cmd_qpair_setup()503 qpair->cq_hdbl_off = nvme_mmio_offsetof(doorbell) + in nvme_cmd_qpair_setup()
46 } doorbell[1]; member
344 -device ivshmem-doorbell,vectors=${CONFIG_IVSHMEM_MSI_X_VECTORS},chardev=ivshmem
