Home
last modified time | relevance | path

Searched full:manage (Results 1 – 25 of 692) sorted by relevance

12345678910>>...28

/linux/drivers/crypto/ccp/
H A Dsp-dev.c84 /* 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/Documentation/translations/zh_CN/core-api/irq/
H A Dirq-domain.rst194 CPU Vector irq_domain (root irq_domain to manage CPU vectors)
197 Interrupt Remapping irq_domain (manage irq_remapping entries)
200 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
/linux/Documentation/core-api/irq/
H A Dirq-domain.rst33 top of the irq_alloc_desc*() API. An irq_domain to manage the mapping
187 controller to manage IRQ allocations and it requires an irq_desc to be
234 CPU Vector irq_domain (root irq_domain to manage CPU vectors)
237 Interrupt Remapping irq_domain (manage irq_remapping entries)
240 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
275 3) Optionally, implement an irq_chip to manage the interrupt controller
/linux/drivers/firmware/broadcom/
H A DKconfig31 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/drivers/platform/x86/amd/hsmp/
H A DKconfig20 The driver provides a way for user space tools to monitor and manage
38 The driver provides a way for user space tools to monitor and manage
/linux/drivers/firmware/arm_scmi/vendors/imx/
H A DKconfig21 This enables i.MX System CPU Protocol to manage cpu
34 manage Logical Machines boot, shutdown and etc.
/linux/Documentation/driver-api/usb/
H A Ddma.rst19 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/drivers/thermal/
H A DKconfig147 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/Documentation/devicetree/bindings/firmware/
H A Dnxp,imx95-scmi.yaml17 machines (LM). It is usually used to allow one LM to manage another used
37 used to manage auxiliary CPUs in a LM.
/linux/arch/alpha/include/asm/
H A Dpci.h13 * The following structure is used to manage multiple PCI busses.
19 /* A controller. Used to manage multiple PCI busses. */
/linux/sound/soc/
H A Dsoc-devres.c21 * @dev: Device used to manage component
59 * @dev: Device used to manage card
/linux/arch/arc/boot/dts/
H A Dabilis_tb10x.dtsi220 tb100-mdscr-manage-tsin;
229 tb100-mdscr-manage-tsin;
234 tb100-mdscr-manage-tsin;
/linux/drivers/misc/sgi-gru/
H A Dgrutables.h70 * 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/drivers/gpu/drm/i915/
H A Di915_ttm_buddy_manager.c258 * @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/Documentation/admin-guide/device-mapper/
H A Dvdo.rst11 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/Documentation/filesystems/
H A Dinotify.rst34 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/Documentation/networking/
H A Dmultiqueue.rst21 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/drivers/md/
H A Ddm-bio-prison-v2.h42 * 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/net/ncsi/
H A DMakefile5 obj-$(CONFIG_NET_NCSI) += ncsi-cmd.o ncsi-rsp.o ncsi-aen.o ncsi-manage.o ncsi-netlink.o
/linux/Documentation/security/
H A Dlsm.rst62 manage the security fields and to perform access control.
113 categories: hooks that are used to manage the security fields and hooks
/linux/drivers/gpu/drm/amd/display/dc/link/protocols/
H A Dlink_hpd.c28 * This file implements functions that manage basic HPD components such as gpio.
30 * file only manages basic HPD functionality. It doesn't manage detection or
/linux/tools/testing/selftests/drivers/net/netdevsim/
H A Ddevlink_trap.sh186 check_err $? "Did not manage to read trap (hard dropped) statistics when should"
343 check_err $? "Did not manage to read policer drop counter when should"
395 check_err $? "Did not manage to bind a policer when should"
/linux/drivers/virt/acrn/
H A DKconfig10 a privileged management VM, called Service VM, to manage User
/linux/drivers/opp/
H A DKconfig12 implementations a ready to use framework to manage OPPs.
/linux/drivers/net/ethernet/intel/e1000e/
H A DMakefile14 mac.o manage.o nvm.o phy.o \

12345678910>>...28