| /linux-4.4.14/drivers/scsi/cxlflash/ |
| D | lunmgt.c | 226 struct dk_cxlflash_manage_lun *manage) in cxlflash_manage_lun() argument
230 u64 flags = manage->hdr.flags; in cxlflash_manage_lun()
234 lli = find_and_create_lun(sdev, manage->wwid); in cxlflash_manage_lun()
236 __func__, get_unaligned_be64(&manage->wwid[0]), in cxlflash_manage_lun()
237 get_unaligned_be64(&manage->wwid[8]), in cxlflash_manage_lun()
238 manage->hdr.flags, lli); in cxlflash_manage_lun()
|
| /linux-4.4.14/arch/powerpc/platforms/cell/ |
| D | Makefile | 19 spu-manage-$(CONFIG_PPC_CELL_COMMON) += spu_manage.o
25 $(spu-manage-y) \
|
| /linux-4.4.14/drivers/net/ethernet/intel/e1000e/ |
| D | Makefile | 35 mac.o manage.o nvm.o phy.o \
|
| /linux-4.4.14/arch/arc/boot/dts/ |
| D | abilis_tb10x.dtsi | 217 tb100-mdscr-manage-tsin;
226 tb100-mdscr-manage-tsin;
231 tb100-mdscr-manage-tsin;
|
| /linux-4.4.14/kernel/irq/ |
| D | Makefile | 2 obj-y := irqdesc.o handle.o manage.o spurious.o resend.o chip.o dummychip.o devres.o
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | max98357a.txt | 10 If this option is not specified then driver does not manage
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | .genericirq.xml.cmd | 2 …/generic-chip.c include/linux/irq.h include/linux/interrupt.h kernel/irq/manage.c kernel/irq/chip.…
|
| D | .kernel-api.xml.cmd | 2 …ude/linux/kfifo.h kernel/relay.c kernel/relay.c kernel/kmod.c kernel/irq/manage.c kernel/dma.c ker…
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | ti-keystone-pllctrl.txt | 5 the NETCP modules) requires a PLL Controller to manage the various clock
|
| /linux-4.4.14/Documentation/usb/ |
| D | dma.txt | 16 manage dma mappings for existing dma-ready buffers (see below).
24 don't manage dma mappings for URBs.
38 IOMMU to manage the DMA mappings. It can cost MUCH more to set up and
126 The calls manage urb->transfer_dma for you, and set URB_NO_TRANSFER_DMA_MAP
|
| D | callbacks.txt | 14 * @probe: Called to see if the driver is willing to manage a particular
|
| /linux-4.4.14/drivers/thermal/ |
| D | Kconfig | 82 Select this if you want to let the user space manage the
98 Enable this to manage platform thermals using fair-share governor.
103 Enable this to manage platform thermals using a simple linear
110 Enable this to manage platform thermals using bang bang governor.
119 Enable this to let the user space manage the platform thermals.
124 Enable this to manage platform thermals by dynamically
264 zones to manage temperatures. This option is also required for the
|
| /linux-4.4.14/Documentation/ |
| D | IRQ-domain.txt | 31 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
129 controller to manage IRQ allocations and it requires an irq_desc to be
172 CPU Vector irq_domain (root irq_domain to manage CPU vectors)
175 Interrupt Remapping irq_domain (manage irq_remapping entries)
178 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
217 3) Optionally implement an irq_chip to manage the interrupt controller
|
| D | SM501.txt | 15 drivers which manage the specific hardware blocks. These services
|
| D | eisa.txt | 9 abstractions to manage busses, devices and drivers.
|
| D | md-cluster.txt | 158 1. Node 1 issues mdadm --manage /dev/mdX --add /dev/sdYY which issues
|
| D | ManagementStyle | 40 manage had better know the details better than you, so if they come to
44 (Corollary:if the people you manage don't know the details better than
|
| D | robust-futex-ABI.txt | 28 as glibc linked with the application) has to manage and place the
|
| D | kernel-docs.txt | 294 how your Operating System allows you to manage a large number of
299 inactive FDs cost very little in memory and CPU time to manage".
|
| D | cachetlb.txt | 386 the kernel trying to do I/O to vmap areas must manually manage
|
| D | 00-INDEX | 51 - how to (attempt to) manage kernel hackers.
|
| D | vfio.txt | 125 pci bus, therefore the user will make use of vfio-pci to manage the
|
| D | md.txt | 1 Tools that manage md devices can be found at
|
| D | IPMI.txt | 310 though, since it is tricky to manage your own buffers.
|
| D | kernel-parameters.txt | 1977 so, the driver will manage that printer.
|
| /linux-4.4.14/drivers/media/dvb-core/ |
| D | Kconfig | 27 will be required to manage the device nodes.
|
| /linux-4.4.14/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.txt | 5 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
|
| D | l2tp.txt | 32 (userspace daemon) to manage them.
37 retained. L2TPv3, however, uses netlink to manage L2TPv3 tunnels and
141 include/linux/l2tp.h to manage tunnel and session contexts. The
|
| D | stmmac.txt | 291 o chain_mode.c/ring_mode.c:: functions to manage RING/CHAINED modes;
352 New GMAC devices provide own way to manage RGMII/SGMII.
354 HW capability register. This means that the stmmac can manage
|
| D | spider_net.txt | 19 together with three pointers into the ring that are used to manage its
|
| D | rxrpc.txt | 67 manage security on the client end. The server end must of necessity be
|
| D | bonding.txt | 1124 Also, at this writing, YaST/YaST2 will not manage bonding
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | phy-mvebu.txt | 28 controller. The USB cluster control register allows to manage common
|
| /linux-4.4.14/drivers/xen/ |
| D | Makefile | 3 obj-y += grant-table.o features.o balloon.o manage.o preempt.o
|
| /linux-4.4.14/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?
|
| D | btrfs.txt | 13 in their ability to address and manage large storage, and also in
262 * btrfs: a single tool to manage the filesystems, refer to the manpage for more details
|
| D | f2fs.txt | 410 The key data structure to manage the data locations is a "node". Similar to
|
| D | vfs.txt | 502 The address space object is used to group and manage pages in the page
1046 d_manage: called to allow the filesystem to manage the transition from a
|
| D | coda.txt | 227 must allow Venus to manage message traffic. In particular Venus must
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | tegra-soctherm.txt | 6 notifications. It is also used to manage emergency shutdown in an
|
| /linux-4.4.14/Documentation/vm/ |
| D | userfaultfd.txt | 22 2) various UFFDIO_* ioctls that can manage the virtual memory regions
24 resolve the userfaults it receives via 1) or to manage the virtual
70 Userland can use the uffdio_register.ioctls to manage the virtual
|
| D | frontswap.txt | 45 store frontswap pages to more completely manage its memory usage.
149 dynamically) manage memory limits to ensure this doesn't happen.
|
| D | numa | 62 nodes. Each emulated node will manage a fraction of the underlying cells'
|
| D | numa_memory_policy.txt | 286 policy is intended to manage. Let the kernel then remap to the
|
| D | unevictable-lru.txt | 38 infrastructure and the use of this to manage several types of "unevictable"
|
| /linux-4.4.14/drivers/soc/qcom/ |
| D | Kconfig | 18 QCOM Platform specific power driver to manage cores and L2 low power
|
| /linux-4.4.14/drivers/staging/android/ |
| D | TODO | 19 which want to manage caches themselves and which indicates whether cpu caches
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-pps | 15 contain files to manage and control its PPS source.
|
| D | sysfs-c2port | 15 manage and control its C2 port.
|
| /linux-4.4.14/fs/ocfs2/ |
| D | Kconfig | 34 It cannot manage any other cluster applications.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | README | 28 But of course, if you _do_ manage to screw up your system using
|
| /linux-4.4.14/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 28 appropriate software access to the reset signals in order to manage the HW,
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | zr364xx.txt | 13 If you manage to use your cam with this code, you can send me a mail (royale@zerezo.com) with the n…
|
| D | README.davinci-vpbe | 33 provides v4l2 device interface to manage VID0 and VID1 layers.
|
| D | soc-camera.txt | 151 conveniently manage these formats. A table of standard transformations is
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | spi-bus.txt | 21 assumption that board specific platform code will be used to manage
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | atmel-at91.txt | 152 Special Function Registers (SFR) manage specific aspects of the integrated
|
| D | cci.txt | 7 transactions and manage coherency, TLB invalidations and memory barriers.
|
| /linux-4.4.14/Documentation/trace/ |
| D | coresight.txt | 87 manage coresight devices on a platform. This first implementation centers on
133 manage coresight devices on a platform. Any coresight compliant device can
|
| /linux-4.4.14/tools/virtio/virtio-trace/ |
| D | README | 68 If you manage guests with libvirt, add the following tags to domain XML files.
|
| /linux-4.4.14/fs/jffs2/ |
| D | Kconfig | 147 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
|
| /linux-4.4.14/Documentation/dvb/ |
| D | ci.txt | 71 The disadvantage is that the driver/hardware has to manage the rest. For
|
| /linux-4.4.14/Documentation/gpio/ |
| D | sysfs.txt | 121 Kernel code can explicitly manage exports of GPIOs which have already been
|
| D | consumer.txt | 223 Device drivers like to manage the logical state of a GPIO, i.e. the value their
|
| D | gpio-legacy.txt | 267 needed to manage a signal that's in active use. That is, requesting a
741 Kernel code can explicitly manage exports of GPIOs which have already been
|
| /linux-4.4.14/Documentation/locking/ |
| D | lglock.txt | 16 To manage global data structures that are partitioned over all CPUs
|
| /linux-4.4.14/Documentation/spi/ |
| D | spidev | 53 Do not try to manage the /dev character device special file nodes by hand.
|
| D | spi-summary | 443 Note that there are two types of memory your driver must manage as part
|
| /linux-4.4.14/Documentation/scsi/ |
| D | osd.txt | 4 to provide efficient operation of input/output logical units that manage the
|
| D | scsi_mid_low_api.txt | 920 * manage the memory pointed to and maintain it, typically for the
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 2.Process | 214 of the kernel they manage; they are the ones who will (usually) accept a
217 Subsystem maintainers each manage their own version of the kernel source
366 Some major subsystem maintainers use quilt to manage patches intended to go
|
| /linux-4.4.14/Documentation/arm/ |
| D | README | 172 for, we have a method to manage this which ensures that we don't end up
|
| D | cluster-pm-race-avoidance.txt | 5 cluster setup and teardown operations and to manage hardware coherency
|
| /linux-4.4.14/Documentation/crypto/ |
| D | async-tx-api.txt | 94 manage the channel. Once a driver-specific threshold is met the driver
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | zram.txt | 17 There are several ways to configure and manage zram device(-s):
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei.txt | 25 Intel AMT provides the ability to manage a host remotely out-of-band (OOB)
|
| /linux-4.4.14/Documentation/power/ |
| D | charger-manager.txt | 66 and it will manage in-suspend monitoring for all instances of Charger Manager.
|
| D | pm_qos_interface.txt | 10 2. the per-device PM QoS framework provides the API to manage the per-device latency
|
| D | runtime_pm.txt | 266 power manage the device at run time via the /sys/devices/.../power/control
583 The user space can effectively disallow the driver of the device to power manage
592 manage the device at run time, the driver may confuse it by using
|
| D | devices.txt | 35 Some drivers can manage hardware wakeup events, which make the system
|
| /linux-4.4.14/drivers/spi/ |
| D | Kconfig | 156 this code to manage the per-word or per-transfer accesses to the
240 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
|
| /linux-4.4.14/drivers/input/serio/ |
| D | Kconfig | 137 Controller", an i8042 carrying microcode to manage a
|
| /linux-4.4.14/drivers/staging/fsl-mc/ |
| D | README.txt | 206 Used by drivers to send commands to the MC to manage
|
| /linux-4.4.14/kernel/power/ |
| D | Kconfig | 273 implementations a ready to use framework to manage OPPs.
|
| /linux-4.4.14/Documentation/thermal/ |
| D | intel_powerclamp.txt | 304 device, a PID based userspace thermal controller can manage to
|
| /linux-4.4.14/Documentation/timers/ |
| D | highres.txt | 82 solution to manage clock event devices and their usage for the various clock
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 9 trying to come up with a unified interface to manage the execution units and
|
| /linux-4.4.14/Documentation/target/ |
| D | tcmu-design.txt | 267 TCMU is designed so that multiple unrelated processes can manage TCMU
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 165 Module parameters are used to manage different applications for
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 159 to the caller to allocate and manage these identifiers. If the
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 240 (8) A pair of functions to manage contexts for the completion callback
681 manage the heuristics of coping with vmscan trying to eject pages, which may
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 47 hooks, beyond what is already present, required to manage dynamic
63 virtual file system, manage the attributes and permissions of these
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 59 bus errors are easy to manage in the device driver. Indeed, most
|
| /linux-4.4.14/Documentation/security/ |
| D | credentials.txt | 535 There are some functions to help manage credentials:
|
| /linux-4.4.14/arch/powerpc/ |
| D | Kconfig | 42 can manage. Virtual interrupt numbers are what you see in
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 33 with the ability to configure and manage cascaded switches on top of each other
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 358 figure out how we want to manage SCHED_DEADLINE bandwidth at the task group
|
| /linux-4.4.14/Documentation/block/ |
| D | biodoc.txt | 309 involved. In the latter case, the driver would modify and manage the
717 queueing (typically known as tagged command queueing), ie manage more than
|
| /linux-4.4.14/drivers/ide/ |
| D | Kconfig | 14 If you say Y here, your kernel will be able to manage ATA/(E)IDE and
|
| /linux-4.4.14/drivers/platform/x86/ |
| D | Kconfig | 712 that manage the hotkeys via WMI events.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 984 This option will let you create and manage CPUSETs which
1564 The shmem is an internal filesystem used to manage shared memory.
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 741 Use the IA-PC HPET (High Precision Event Timer) to manage
2252 power manage devices, enter the Standby State, enter the Suspend
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 463 acl Allow setfacl and getfacl to manage posix ACLs if server
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 1334 If KVM_DEV_ASSIGN_PCI_2_3 is set, the kernel will manage legacy INTx interrupts
1688 Note that the kernel uses the device INTx disable bit to internally manage the
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 199 manage devices. If you have a disk cage, the chances are that
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 1682 Uses K42's RCU-like functionality to manage clustered-object
|
| /linux-4.4.14/drivers/video/fbdev/ |
| D | Kconfig | 723 you manage to get it going. ;-)
|