Home
last modified time | relevance | path

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

1234567

/linux-6.12.1/drivers/gpu/drm/amd/amdkfd/
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 …]
Dkfd_priv.h121 * same SDMA engine on SOC15, which has 8-byte doorbells for SDMA.
123 * (2*i+1) doorbells (in terms of the lower 12 bit address) lie exactly in
324 u32 __iomem *doorbell_kernel_ptr; /* This is a pointer for a doorbells
369 /* Kernel doorbells for KFD device */
370 struct amdgpu_bo *doorbells; member
701 /* doorbells for kfd process */
1094 /* Doorbells */
/linux-6.12.1/drivers/gpu/drm/xe/
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.
Dxe_guc_types.h22 * struct xe_guc_db_mgr - GuC Doorbells Manager.
24 * Note: GuC Doorbells Manager is relying on &xe_guc::submission_state.lock
28 /** @count: number of doorbells to manage */
30 /** @bitmap: bitmap to track allocated doorbells */
Dxe_gt_sriov_pf_config_types.h28 /** @num_dbs: number of GuC doorbells IDs. */
53 /** @num_dbs: number of GuC doorbells. */
/linux-6.12.1/drivers/gpu/drm/amd/amdgpu/
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
Damdgpu_doorbell_mgr.c138 * amdgpu_doorbell_create_kernel_doorbells - Create kernel doorbells for graphics
142 * Creates doorbells for graphics driver usages.
150 /* SI HW does not have doorbells, skip allocation */ in amdgpu_doorbell_create_kernel_doorbells()
169 DRM_ERROR("Failed to allocate kernel doorbells, err=%d\n", r); in amdgpu_doorbell_create_kernel_doorbells()
218 * doorbells are in the first page. So with paging queue enabled, in amdgpu_doorbell_init()
/linux-6.12.1/Documentation/devicetree/bindings/interrupt-controller/
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.
Dmsi-controller.yaml15 number of doorbells.
23 and will not encode doorbells or payloads as these can be
/linux-6.12.1/drivers/ntb/
DKconfig21 hardware doorbells. MSI interrupts typically offer lower latency
22 than doorbells and more MSI interrupts can be made available to
/linux-6.12.1/arch/powerpc/platforms/pseries/
Dsmp.c165 /* Use msgsndp doorbells target is a sibling, else use interrupt controller */
206 /* Doorbells can only be used for IPIs between SMT siblings */ in pSeries_smp_probe()
214 * KVM emulates doorbells by disabling FSCR[MSGP] so msgsndp in pSeries_smp_probe()
233 * gang scheduled on the same physical core, so doorbells are always in pSeries_smp_probe()
/linux-6.12.1/drivers/misc/vmw_vmci/
Dvmci_context.h67 /* Doorbells created by context. */
70 /* Doorbells pending for context. */
102 * for doorbells and queue pairs.
Dvmci_doorbell.h17 * VMCINotifyResourceInfo: Used to create and destroy doorbells, and
/linux-6.12.1/Documentation/devicetree/bindings/mailbox/
Dnvidia,tegra186-hsp.yaml22 semaphores, arbitrated semaphores and doorbells.
38 For doorbells, the second cell specifies the index of the doorbell to
Darm,mhuv2.yaml37 bits in a channel window. A channel window can support up to 32 doorbells
119 windows are used in doorbell protocol (64 doorbells), followed by 1, 5 and
/linux-6.12.1/drivers/virt/
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.
DKconfig36 2) A file interface to reading incoming doorbells.
/linux-6.12.1/drivers/mailbox/
Dtegra-hsp.c120 struct list_head doorbells; member
163 list_for_each_entry(entry, &hsp->doorbells, list) in __tegra_hsp_doorbell_get()
204 * have some doorbells enabled, which means that requesting an in tegra_hsp_doorbell_irq()
292 list_add_tail(&db->list, &hsp->doorbells); in tegra_hsp_doorbell_create()
740 INIT_LIST_HEAD(&hsp->doorbells); in tegra_hsp_probe()
804 dev_err(&pdev->dev, "failed to add doorbells: %d\n", in tegra_hsp_probe()
884 list_for_each_entry(db, &hsp->doorbells, list) { in tegra_hsp_resume()
/linux-6.12.1/drivers/gpu/drm/xe/abi/
Dguc_klvs_abi.h199 * Refers to the number of doorbells allocated to this VF.
201 * :0: no doorbells (default)
202 * :1-255: number of doorbells (Gen12)
287 * :1-255: number of doorbells (Gen12)
/linux-6.12.1/drivers/net/ethernet/fungible/funcore/
Dfun_dev.h53 u32 __iomem *dbs; /* start of doorbells in BAR0 mapping */
62 /* address increment between consecutive doorbells, in 4B units */
/linux-6.12.1/drivers/net/ethernet/qlogic/qed/
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()
Dqed.h487 BAR_ID_1 /* Used for doorbells */
545 void __iomem *doorbells; member
758 void __iomem *doorbells; member
965 ((cdev)->doorbells) + (db_addr)))
/linux-6.12.1/drivers/ntb/test/
DKconfig6 doorbells of the ntb hardware. This driver may be used to test that
/linux-6.12.1/drivers/infiniband/hw/efa/
Defa_admin_cmds_defs.h651 /* Bar used for SQ and RQ doorbells */
733 * consecutive doorbells (in units of 64B). Driver must ensure that only
736 * be written to SQ between two consecutive doorbells. max_tx_batch=11
738 * two consecutive doorbells. Zero means unlimited.
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/google/
Dgve.rst33 - Bar2 - IRQ, RX and TX doorbells
150 doorbells to notify the device of new descriptors.

1234567