Home
last modified time | relevance | path

Searched full:doorbells (Results 1 – 25 of 110) sorted by relevance

12345

/linux/drivers/gpu/drm/amd/amdkfd/
H A Dkfd_doorbell.c31 * This extension supports a kernel level doorbells management for the
38 * The doorbells are intended to be written by applications as part
40 * We assign doorbells to applications in PAGE_SIZE-sized and aligned chunks.
46 * offsets (KFD_MMAP_DOORBELL_START-END) is used for doorbells.
74 /* Bitmap to dynamically allocate doorbells from kernel page */ in kfd_doorbell_init()
86 &kfd->doorbells, in kfd_doorbell_init()
90 pr_err("failed to allocate kernel doorbells\n"); in kfd_doorbell_init()
102 amdgpu_bo_free_kernel(&kfd->doorbells, NULL, in kfd_doorbell_fini()
165 kfd->doorbells, in kfd_get_kernel_doorbell()
218 /* Mask out doorbells reserved for SDMA, IH, and VCN on SOC15. */ in init_doorbell_bitmap()
[all …]
/linux/drivers/gpu/drm/xe/
H A Dxe_guc_db_mgr.c20 * DOC: GuC Doorbells
26 * In SR-IOV mode, the doorbells are treated as shared resource and PF must
62 xe_gt_err(dbm_to_gt(dbm), "GuC doorbells manager unclean (%u/%u)\n", in __fini_dbm()
75 * xe_guc_db_mgr_init() - Initialize GuC Doorbells Manager.
77 * @count: number of doorbells to manage
80 * doorbells supported by the hardware are available for use.
82 * Only VF's drivers will have to provide explicit number of doorbells IDs
252 * xe_guc_db_mgr_print() - Print status of GuC Doorbells Manager.
H A Dxe_gt_sriov_pf_config_types.h28 /** @num_dbs: number of GuC doorbells IDs. */
55 /** @num_dbs: number of GuC doorbells. */
H A Dxe_gt_sriov_vf_types.h26 /** @num_dbs: assigned number of GuC doorbells IDs. */
/linux/drivers/gpu/drm/amd/amdgpu/
H A Damdgpu_doorbell.h35 /* Number of doorbells reserved for amdgpu kernel driver */
38 /* Kernel doorbells */
41 /* For CPU access of doorbells */
45 /* Reserved doorbells for amdgpu (including multimedia).
244 …* All compute related doorbells: kiq, hiq, diq, traditional compute queue, user queue, should loca…
246 * Compute related doorbells are allocated from 0x00 to 0x8a
267 /* User queue doorbell range (128 doorbells) */
275 * Other graphics doorbells can be allocated here: from 0x8c to 0xdf
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dmsi.txt16 Devices may be configured by software to write to arbitrary doorbells which
17 they can address. An MSI controller may feature a number of doorbells.
35 address by some master. An MSI controller may feature a number of doorbells.
48 not encode doorbells or payloads as these can be configured dynamically.
H A Dmsi-controller.yaml15 number of doorbells.
23 and will not encode doorbells or payloads as these can be
/linux/drivers/ntb/
H A DKconfig21 hardware doorbells. MSI interrupts typically offer lower latency
22 than doorbells and more MSI interrupts can be made available to
/linux/drivers/misc/vmw_vmci/
H A Dvmci_context.h67 /* Doorbells created by context. */
70 /* Doorbells pending for context. */
102 * for doorbells and queue pairs.
H A Dvmci_doorbell.h17 * VMCINotifyResourceInfo: Used to create and destroy doorbells, and
/linux/drivers/virt/
H A Dfsl_hypervisor.c16 * 2. A file interface to reading incoming doorbells.
514 * Interrupt handler for all doorbells
516 * We use the same interrupt handler for all doorbells. Whenever a doorbell
548 * Interrupt handler for state-change doorbells
587 * Return the handles for any incoming doorbells
653 * Open the driver and prepare for reading doorbells.
656 * for that file handle. This queue is used for any incoming doorbells.
H A DKconfig36 2) A file interface to reading incoming doorbells.
/linux/drivers/net/ethernet/fungible/funcore/
H A Dfun_dev.h53 u32 __iomem *dbs; /* start of doorbells in BAR0 mapping */
62 /* address increment between consecutive doorbells, in 4B units */
/linux/Documentation/devicetree/bindings/mailbox/
H A Dnvidia,tegra186-hsp.yaml22 semaphores, arbitrated semaphores and doorbells.
38 For doorbells, the second cell specifies the index of the doorbell to
/linux/drivers/net/ethernet/qlogic/qed/
H A Dqed_vf.c461 /* Doorbells are tricky; Upper-layer has alreday set the hwfn doorbell in qed_vf_hw_prepare()
465 if (!p_hwfn->doorbells) { in qed_vf_hw_prepare()
466 p_hwfn->doorbells = (u8 __iomem *)p_hwfn->regview + in qed_vf_hw_prepare()
481 p_hwfn->doorbells = (u8 __iomem *) in qed_vf_hw_prepare()
544 p_hwfn->doorbells = (u8 __iomem *)p_hwfn->regview + in qed_vf_hw_prepare()
551 p_hwfn->regview, p_hwfn->doorbells, p_hwfn->cdev->doorbells); in qed_vf_hw_prepare()
880 *pp_doorbell = (u8 __iomem *)p_hwfn->doorbells + resp->offset; in qed_vf_pf_txq_start()
884 *pp_doorbell = (u8 __iomem *)p_hwfn->doorbells + in qed_vf_pf_txq_start()
/linux/drivers/ntb/test/
H A DKconfig6 doorbells of the ntb hardware. This driver may be used to test that
/linux/Documentation/networking/device_drivers/ethernet/google/
H A Dgve.rst33 - Bar2 - IRQ, RX and TX doorbells
150 doorbells to notify the device of new descriptors.
/linux/Documentation/PCI/endpoint/function/binding/
H A Dpci-ntb.rst31 db_count Number of doorbells; default = 4
/linux/arch/powerpc/kernel/
H A Didle_64e.S29 * since we may otherwise lose it (doorbells etc...).
/linux/drivers/net/ethernet/amazon/ena/
H A Dena_netdev.h191 u64 doorbells; member
444 ena_increase_stat(&tx_ring->tx_stats.doorbells, 1, &tx_ring->syncp); in ena_ring_tx_doorbell()
/linux/Documentation/admin-guide/
H A Drapidio.rst40 resources, and manage mailboxes/doorbells.
/linux/drivers/ntb/hw/intel/
H A Dntb_hw_gen4.h37 #define GEN4_IM_DOORBELL_OFFSET 0x0100 /* 0-31 doorbells */
/linux/arch/powerpc/include/asm/
H A Ddbell.h99 * Doorbells must only be used if CPU_FTR_DBELL is available.
/linux/drivers/net/ethernet/chelsio/cxgb4/
H A Dt4_values.h103 * The User Doorbells are each 128 bytes in length with a Simple Doorbell at
/linux/Documentation/driver-api/rapidio/
H A Dmport_cdev.rst41 - Query/Control type of events reported through this driver: doorbells,

12345