Searched full:manage (Results 1 – 25 of 933) sorted by relevance
12345678910>>...38
/linux-6.14.4/drivers/crypto/ccp/ |
D | sp-dev.c | 84 /* Need a common routine to manage all interrupts */ in sp_request_ccp_irq() 97 /* Each sub-device can manage it's own interrupt */ in sp_request_ccp_irq() 112 /* Need a common routine to manage all interrupts */ in sp_request_psp_irq() 125 /* Each sub-device can manage it's own interrupt */ in sp_request_psp_irq() 137 /* Using common routine to manage all interrupts */ in sp_free_ccp_irq() 148 /* Each sub-device can manage it's own interrupt */ in sp_free_ccp_irq() 156 /* Using common routine to manage all interrupts */ in sp_free_psp_irq() 167 /* Each sub-device can manage it's own interrupt */ in sp_free_psp_irq()
|
/linux-6.14.4/drivers/scsi/cxlflash/ |
D | lunmgt.c | 219 * @arg: Manage ioctl data structure. 229 struct dk_cxlflash_manage_lun *manage = arg; in cxlflash_manage_lun() local 234 u64 flags = manage->hdr.flags; in cxlflash_manage_lun() 238 lli = find_and_create_lun(sdev, manage->wwid); in cxlflash_manage_lun() 240 __func__, get_unaligned_be64(&manage->wwid[0]), in cxlflash_manage_lun() 241 get_unaligned_be64(&manage->wwid[8]), manage->hdr.flags, lli); in cxlflash_manage_lun()
|
/linux-6.14.4/Documentation/driver-api/ |
D | extcon.rst | 14 options, such as smartphones, tablets, and laptops. It helps manage various 27 can manage the different states of this port, such as: 42 Extcon can manage the state of a wireless charging connection, allowing 47 In a smart TV, Extcon can manage multiple HDMI ports, detecting when 53 states, handle mutually exclusive connections, and manage connector
|
/linux-6.14.4/Documentation/core-api/irq/ |
D | irq-domain.rst | 33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is 184 controller to manage IRQ allocations and it requires an irq_desc to be 237 CPU Vector irq_domain (root irq_domain to manage CPU vectors) 240 Interrupt Remapping irq_domain (manage irq_remapping entries) 243 IOAPIC irq_domain (manage IOAPIC delivery entries/pins) 285 3) Optionally implement an irq_chip to manage the interrupt controller
|
/linux-6.14.4/arch/powerpc/platforms/cell/ |
D | Makefile | 19 spu-manage-$(CONFIG_PPC_CELL_COMMON) += spu_manage.o 24 $(spu-manage-y) \
|
/linux-6.14.4/Documentation/translations/zh_CN/core-api/irq/ |
D | irq-domain.rst | 200 CPU Vector irq_domain (root irq_domain to manage CPU vectors) 203 Interrupt Remapping irq_domain (manage irq_remapping entries) 206 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
|
/linux-6.14.4/drivers/firmware/broadcom/ |
D | Kconfig | 31 This module help to manage firmware on Broadcom BNXT device. The module 32 registers on tee bus and invoke calls to manage firmware on BNXT device.
|
/linux-6.14.4/drivers/platform/x86/amd/hsmp/ |
D | Kconfig | 19 The driver provides a way for user space tools to monitor and manage 36 The driver provides a way for user space tools to monitor and manage
|
/linux-6.14.4/Documentation/PCI/ |
D | tph.rst | 20 Complex, to better manage platform resources for these requests. 45 Manage TPH 68 Manage ST
|
/linux-6.14.4/Documentation/driver-api/usb/ |
D | dma.rst | 19 manage dma mappings for existing dma-ready buffers (see below). 27 don't manage dma mappings for URBs. 41 IOMMU to manage the DMA mappings. It can cost MUCH more to set up and
|
/linux-6.14.4/drivers/thermal/ |
D | Kconfig | 147 Enable this to manage platform thermals using fair-share governor. 152 Enable this to manage platform thermals using a simple linear 159 Enable this to manage platform thermals using bang bang governor. 168 Enable this to let the user space manage the platform thermals. 174 Enable this to manage platform thermals by dynamically
|
/linux-6.14.4/arch/alpha/include/asm/ |
D | pci.h | 13 * The following structure is used to manage multiple PCI busses. 19 /* A controller. Used to manage multiple PCI busses. */
|
/linux-6.14.4/arch/powerpc/platforms/powernv/ |
D | opal-flash.c | 31 /* Manage image status values */ 40 /* Manage operation tokens */ 223 * Manage flash routine 233 * Show manage flash status 248 * Manage operations:
|
/linux-6.14.4/sound/soc/ |
D | soc-devres.c | 21 * @dev: Device used to manage component 59 * @dev: Device used to manage card
|
/linux-6.14.4/drivers/soc/qcom/ |
D | Kconfig | 33 This driver is used to manage Generic Interface (GENI) firmware based 35 driver is also used to manage the common aspects of multiple Serial 236 to manage cores, L2 low power modes and to configure the internal
|
/linux-6.14.4/arch/arc/boot/dts/ |
D | abilis_tb10x.dtsi | 220 tb100-mdscr-manage-tsin; 229 tb100-mdscr-manage-tsin; 234 tb100-mdscr-manage-tsin;
|
/linux-6.14.4/drivers/misc/sgi-gru/ |
D | grutables.h | 70 * to manage user contexts and to perform functions such as TLB dropin and 87 * GMS - GRU Memory Struct - Used to manage TLB shootdowns. Tracks GRUs 91 * GS - GRU State - Used to manage the state of a GRU chiplet 92 * BS - Blade State - Used to manage state of all GRU chiplets 425 unsigned long gs_context_map; /* bitmap to manage 427 unsigned long gs_cbr_map; /* bitmap to manage CB 429 unsigned long gs_dsr_map; /* bitmap used to manage
|
/linux-6.14.4/drivers/gpu/drm/i915/ |
D | i915_ttm_buddy_manager.c | 258 * @type: Memory type we want to manage 260 * @size: The size in bytes to manage 261 * @visible_size: The CPU visible size in bytes to manage 325 * @type: Memory type we want to manage
|
/linux-6.14.4/Documentation/filesystems/ |
D | inotify.rst | 34 more fd's than are feasible to manage, and more fd's than are optimally 62 to manage and block on 1000 fd's via select?
|
/linux-6.14.4/drivers/md/ |
D | dm-bio-prison-v1.h | 48 * Treat this as opaque, only in header so callers can manage allocation 65 * Eventually all bio prison clients should manage their own cell memory.
|
D | dm-bio-prison-v2.h | 42 * Treat this as opaque, only in header so callers can manage allocation 62 * Eventually all bio prison clients should manage their own cell memory.
|
/linux-6.14.4/Documentation/networking/ |
D | multiqueue.rst | 21 The base driver will also need to manage the queues as it does the global 23 netif_{start|stop|wake}_subqueue() functions to manage each queue while the
|
/linux-6.14.4/Documentation/admin-guide/device-mapper/ |
D | vdo.rst | 11 it. It is strongly recommended that lvm be used to manage vdo volumes. See 135 The number of threads used to manage data comparisons for 140 The number of threads used to manage caching and locking 145 The number of threads used to manage administration of the
|
/linux-6.14.4/net/ncsi/ |
D | Makefile | 5 obj-$(CONFIG_NET_NCSI) += ncsi-cmd.o ncsi-rsp.o ncsi-aen.o ncsi-manage.o ncsi-netlink.o
|
/linux-6.14.4/drivers/net/ethernet/intel/e1000e/ |
D | Makefile | 14 mac.o manage.o nvm.o phy.o \
|
12345678910>>...38