Searched refs:manage (Results 1 – 25 of 161) sorted by relevance
1234567
| /Linux-v5.4/drivers/scsi/cxlflash/ |
| D | lunmgt.c | 228 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()
|
| D | superpipe.h | 149 struct dk_cxlflash_manage_lun *manage);
|
| /Linux-v5.4/arch/powerpc/platforms/cell/ |
| D | Makefile | 19 spu-manage-$(CONFIG_PPC_CELL_COMMON) += spu_manage.o
25 $(spu-manage-y) \
|
| /Linux-v5.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-v5.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-v5.4/drivers/net/ethernet/intel/e1000e/ |
| D | Makefile | 11 mac.o manage.o nvm.o phy.o \
|
| /Linux-v5.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
129 The calls manage ``urb->transfer_dma`` for you, and set
|
| /Linux-v5.4/kernel/irq/ |
| D | Makefile | 3 obj-y := irqdesc.o handle.o manage.o spurious.o resend.o chip.o dummychip.o devres.o
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | ti-keystone-pllctrl.txt | 5 the NETCP modules) requires a PLL Controller to manage the various clock
|
| /Linux-v5.4/Documentation/ |
| D | IRQ-domain.txt | 33 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
|
| /Linux-v5.4/drivers/opp/ |
| D | Kconfig | 13 implementations a ready to use framework to manage OPPs.
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | max98357a.txt | 10 If this option is not specified then driver does not manage
|
| /Linux-v5.4/drivers/thermal/tegra/ |
| D | Kconfig | 11 zones to manage temperatures. This option is also required for the
|
| /Linux-v5.4/drivers/thermal/ |
| D | Kconfig | 106 Select this if you want to let the user space manage the
122 Enable this to manage platform thermals using fair-share governor.
127 Enable this to manage platform thermals using a simple linear
134 Enable this to manage platform thermals using bang bang governor.
143 Enable this to let the user space manage the platform thermals.
148 Enable this to manage platform thermals by dynamically
|
| /Linux-v5.4/Documentation/networking/ |
| D | multiqueue.txt | 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
|
| D | alias.rst | 7 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
|
| /Linux-v5.4/Documentation/devicetree/bindings/pci/ |
| D | cdns,cdns-pcie-ep.txt | 13 than one in the list. If only one PHY listed it must manage all lanes.
|
| /Linux-v5.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
83 QCOM Platform specific power driver to manage cores and L2 low power
|
| /Linux-v5.4/Documentation/devicetree/bindings/phy/ |
| D | phy-mvebu.txt | 27 controller. The USB cluster control register allows to manage common
|
| /Linux-v5.4/drivers/soc/fsl/ |
| D | Kconfig | 18 This driver is to manage and access global utilities block.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | inotify.txt | 25 more fd's than are feasible to manage, and more fd's than are optimally
53 to manage and block on 1000 fd's via select?
|
| /Linux-v5.4/drivers/xen/ |
| D | Makefile | 3 obj-y += grant-table.o features.o balloon.o manage.o preempt.o time.o
|
| /Linux-v5.4/Documentation/core-api/ |
| D | kernel-api.rst | 231 .. kernel-doc:: kernel/irq/manage.c
336 instances may be used to manage for example a 96 MHz signal that is used
350 Power-aware drivers only enable their clocks when the device they manage
|
| /Linux-v5.4/Documentation/devicetree/bindings/ata/ |
| D | nvidia,tegra124-ahci.txt | 41 doesn't manage them. If it does, they should not be.
|
| /Linux-v5.4/drivers/media/dvb-core/ |
| D | Kconfig | 27 will be required to manage the device nodes.
|
1234567
