Home
last modified time | relevance | path

Searched refs:manage (Results 1 – 25 of 175) sorted by relevance

1234567

/kernel/linux/linux-5.10/drivers/scsi/cxlflash/
Dlunmgt.c228 struct dk_cxlflash_manage_lun *manage) in cxlflash_manage_lun() argument
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()
Dsuperpipe.h149 struct dk_cxlflash_manage_lun *manage);
/kernel/linux/linux-5.10/arch/powerpc/platforms/cell/
DMakefile19 spu-manage-$(CONFIG_PPC_CELL_COMMON) += spu_manage.o
25 $(spu-manage-y) \
/kernel/linux/linux-5.10/drivers/firmware/broadcom/
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.
/kernel/linux/linux-5.10/net/ncsi/
DMakefile5 obj-$(CONFIG_NET_NCSI) += ncsi-cmd.o ncsi-rsp.o ncsi-aen.o ncsi-manage.o ncsi-netlink.o
/kernel/linux/linux-5.10/arch/arc/boot/dts/
Dabilis_tb10x.dtsi220 tb100-mdscr-manage-tsin;
229 tb100-mdscr-manage-tsin;
234 tb100-mdscr-manage-tsin;
/kernel/linux/linux-5.10/drivers/net/ethernet/intel/e1000e/
DMakefile11 mac.o manage.o nvm.o phy.o \
/kernel/linux/linux-5.10/Documentation/driver-api/usb/
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
129 The calls manage ``urb->transfer_dma`` for you, and set
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/
Dti-keystone-pllctrl.txt5 the NETCP modules) requires a PLL Controller to manage the various clock
/kernel/linux/linux-5.10/kernel/irq/
DMakefile3 obj-y := irqdesc.o handle.o manage.o spurious.o resend.o chip.o dummychip.o devres.o
/kernel/linux/linux-5.10/Documentation/core-api/irq/
Dirq-domain.rst33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
163 controller to manage IRQ allocations and it requires an irq_desc to be
210 CPU Vector irq_domain (root irq_domain to manage CPU vectors)
213 Interrupt Remapping irq_domain (manage irq_remapping entries)
216 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
258 3) Optionally implement an irq_chip to manage the interrupt controller
/kernel/linux/linux-5.10/drivers/opp/
DKconfig13 implementations a ready to use framework to manage OPPs.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dmax98357a.txt11 If this option is not specified then driver does not manage
/kernel/linux/linux-5.10/drivers/thermal/tegra/
DKconfig11 zones to manage temperatures. This option is also required for the
/kernel/linux/linux-5.10/Documentation/networking/
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
Dalias.rst7 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/
Dphy-mvebu.txt27 controller. The USB cluster control register allows to manage common
/kernel/linux/linux-5.10/Documentation/networking/devlink/
Dmlx5.rst38 steering entities are created and manage through the driver without
/kernel/linux/linux-5.10/drivers/thermal/
DKconfig116 Select this if you want to let the user space manage the
132 Enable this to manage platform thermals using fair-share governor.
137 Enable this to manage platform thermals using a simple linear
144 Enable this to manage platform thermals using bang bang governor.
153 Enable this to let the user space manage the platform thermals.
159 Enable this to manage platform thermals by dynamically
/kernel/linux/linux-5.10/drivers/xen/
DMakefile3 obj-y += grant-table.o features.o balloon.o manage.o time.o
/kernel/linux/linux-5.10/Documentation/driver-api/xilinx/
Deemi.rst27 specific. This API also manage shared device configuration.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/ata/
Dnvidia,tegra124-ahci.txt41 doesn't manage them. If it does, they should not be.
/kernel/linux/linux-5.10/Documentation/filesystems/
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?
/kernel/linux/linux-5.10/drivers/soc/fsl/
DKconfig18 This driver is to manage and access global utilities block.
/kernel/linux/linux-5.10/Documentation/admin-guide/
Drapidio.rst40 resources, and manage mailboxes/doorbells.

1234567