| /linux-4.1.27/Documentation/netlabel/ |
| D | introduction.txt | 12 is composed of three main components, the protocol engines, the communication
17 The protocol engines are responsible for both applying and retrieving the
21 refrain from calling the protocol engines directly, instead they should use
39 independent interface to the underlying NetLabel protocol engines. In addition
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-hsi | 8 engines (APE) with cellular modem engines (CMT) in cellular
|
| /linux-4.1.27/drivers/gpu/drm/omapdrm/ |
| D | omap_dmm_tiler.c | 150 if (dmm->engines[i].async) in omap_dmm_irq_handler()
151 release_engine(&dmm->engines[i]); in omap_dmm_irq_handler()
153 complete(&dmm->engines[i].compl); in omap_dmm_irq_handler()
570 kfree(omap_dmm->engines); in omap_dmm_remove()
709 omap_dmm->engines = kcalloc(omap_dmm->num_engines, in omap_dmm_probe()
711 if (!omap_dmm->engines) { in omap_dmm_probe()
717 omap_dmm->engines[i].id = i; in omap_dmm_probe()
718 omap_dmm->engines[i].dmm = omap_dmm; in omap_dmm_probe()
719 omap_dmm->engines[i].refill_va = omap_dmm->refill_va + in omap_dmm_probe()
721 omap_dmm->engines[i].refill_pa = omap_dmm->refill_pa + in omap_dmm_probe()
[all …]
|
| D | omap_dmm_priv.h | 174 struct refill_engine *engines; member
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | ppc440spe-adma.txt | 5 for DMA engines and Memory Queue Module node. The latter is used
40 for both DMA engines>.
|
| /linux-4.1.27/drivers/hsi/ |
| D | Kconfig | 9 application engines and cellular modems.
|
| /linux-4.1.27/drivers/gpu/drm/mgag200/ |
| D | Kconfig | 2 tristate "Kernel modesetting driver for MGA G200 server engines"
|
| /linux-4.1.27/drivers/leds/ |
| D | leds-lp5523.c | 400 enum lp55xx_engine_mode mode = chip->engines[nr - 1].mode; in show_engine_mode()
422 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in store_engine_mode()
491 lp5523_mux_to_array(chip->engines[nr - 1].led_mux, mux); in show_engine_leds()
501 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in lp5523_load_mux()
533 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in store_engine_leds()
|
| D | Kconfig | 219 LP5521 LED driver. It is 3 channel chip with programmable engines.
221 programming the engines.
230 It is 9 channel chip with programmable engines.
232 programming the engines.
240 It is 4 channels chip with programmable engines.
242 programming the engines.
250 It is 9 channel chip with programmable engines.
252 programming the engines.
|
| D | leds-lp55xx-common.h | 157 struct lp55xx_engine engines[LP55XX_ENGINE_MAX]; member
|
| D | leds-lp5521.c | 383 enum lp55xx_engine_mode mode = chip->engines[nr - 1].mode; in show_engine_mode()
405 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in store_engine_mode()
|
| D | leds-lp55xx-common.c | 209 chip->engines[idx - 1].mode = LP55XX_ENGINE_LOAD; in lp55xx_firmware_loaded()
|
| /linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
| D | picochip-spacc.txt | 3 Picochip picoXcell devices contain crypto offload engines that may be used for
|
| D | fsl-sec4.txt | 31 equal to the number of Descriptor Controller (DECO) engines in a particular
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | mv-xor.txt | 1 * Marvell XOR engines
|
| /linux-4.1.27/Documentation/ |
| D | Intel-IOMMU.txt | 21 ACPI enumerates and lists the different DMA engines in the platform, and
49 Different DMA engines may support different number of domains.
|
| D | edac.txt | 60 engines, fabric switches, main data path switches, interconnections,
|
| D | kernel-docs.txt | 712 * Name: "linux-kernel mailing list archives and search engines"
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | gpmc-nand.txt | 45 ELM hardware engines should specify this device node in .dtsi
101 (1) support of built in hardware engines.
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | nct6683 | 19 It supports up to 16 fan rotation sensors and up to 8 fan control engines.
|
| /linux-4.1.27/drivers/dma/ |
| D | Kconfig | 9 DMA engines can do asynchronous data transfers without
86 Enable support for the Intel(R) IOP Series RAID engines.
221 Enable support for the AMCC PPC440SPe RAID engines.
469 This allows the async_tx api to take advantage of offload engines for
|
| /linux-4.1.27/Documentation/leds/ |
| D | leds-lp5523.txt | 34 Control interface for the engines:
|
| D | leds-lp5521.txt | 24 Control interface for the engines:
|
| D | leds-lp55xx.txt | 64 LP55xx chips have three program engines.
|
| /linux-4.1.27/Documentation/crypto/ |
| D | async-tx-api.txt | 37 xor-parity-calculations of the md-raid5 driver using the offload engines
40 network stack using Intel(R) I/OAT engines. The following design
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 20 - fsl,qe-num-riscs: define how many RISC engines the QE has.
|
| /linux-4.1.27/tools/perf/util/ |
| D | Build | 93 libperf-y += scripting-engines/
|
| /linux-4.1.27/drivers/crypto/ |
| D | Kconfig | 277 tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
287 This option enables support for the hardware offload engines in the
|
| /linux-4.1.27/Documentation/target/ |
| D | tcmu-design.txt | 32 storage. These are called "backstores" or "storage engines". These
40 or "storage engines". The target comes with backstores that allow a
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | client.txt | 138 engines tasklet, never from interrupt context.
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 52 Enable DMA/processing engines
248 Enable DMA/processing engines.
465 IRQ handler might restart DMA engines.
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 8 video DMA engines and video data processors.
|
| /linux-4.1.27/Documentation/trace/ |
| D | coresight.txt | 15 that have many SoCs and other components like GPU and DMA engines. ARM has
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | fman.txt | 18 Due to the fact that the FMan is an aggregation of sub-engines (ports, MACs,
|
| /linux-4.1.27/Documentation/power/ |
| D | devices.txt | 630 "on" (how many engines are active?), plus a state that gets back to "on"
|
| /linux-4.1.27/Documentation/RCU/ |
| D | RTFP.txt | 7 and search engines will usually find what you are looking for.
|