| /linux-3.4.99/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-3.4.99/drivers/leds/ |
| D | leds-lp5523.c | 129 struct lp5523_engine engines[LP5523_ENGINES]; member
144 engines[engine->id - 1]); in engine_to_lp5523()
224 ret |= lp5523_load_program(&chip->engines[0], pattern[0]); in lp5523_configure()
225 ret |= lp5523_load_program(&chip->engines[1], pattern[1]); in lp5523_configure()
226 ret |= lp5523_load_program(&chip->engines[2], pattern[2]); in lp5523_configure()
382 lp5523_mux_to_array(chip->engines[nr - 1].led_mux, mux); in show_engine_leds()
412 if (chip->engines[nr - 1].mode != LP5523_CMD_LOAD) in store_engine_leds()
415 if (lp5523_load_mux(&chip->engines[nr - 1], mux)) in store_engine_leds()
591 return lp5523_do_store_load(&chip->engines[nr - 1], buf, len); in store_engine_load()
611 switch (chip->engines[nr - 1].mode) { in show_engine_mode()
[all …]
|
| D | leds-lp5521.c | 119 struct lp5521_engine engines[LP5521_MAX_ENGINES]; member
133 engines[engine->id - 1]); in engine_to_lp5521()
232 for (i = 0; i < ARRAY_SIZE(chip->engines); i++) { in lp5521_init_engine()
233 chip->engines[i].id = i + 1; in lp5521_init_engine()
234 chip->engines[i].engine_mask = LP5521_ENG_MASK_BASE >> (i * 2); in lp5521_init_engine()
235 chip->engines[i].prog_page = i; in lp5521_init_engine()
401 return lp5521_do_store_load(&chip->engines[nr - 1], buf, len); in store_engine_load()
421 switch (chip->engines[nr - 1].mode) { in show_engine_mode()
450 struct lp5521_engine *engine = &chip->engines[nr - 1]; in store_engine_mode()
|
| D | Kconfig | 177 LP5521 LED driver. It is 3 channel chip with programmable engines.
179 programming the engines.
186 LP5523 LED driver. It is 9 channel chip with programmable engines.
188 programming the engines.
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-bus-hsi | 8 engines (APE) with cellular modem engines (CMT) in cellular
|
| /linux-3.4.99/drivers/staging/omapdrm/ |
| D | omap_dmm_tiler.c | 131 wake_up_interruptible(&dmm->engines[i].wait_for_refill); in omap_dmm_irq_handler()
495 kfree(omap_dmm->engines); in omap_dmm_remove()
622 omap_dmm->engines = kzalloc( in omap_dmm_probe()
625 if (!omap_dmm->engines) { in omap_dmm_probe()
634 omap_dmm->engines[i].id = i; in omap_dmm_probe()
635 omap_dmm->engines[i].dmm = omap_dmm; in omap_dmm_probe()
636 omap_dmm->engines[i].refill_va = omap_dmm->refill_va + in omap_dmm_probe()
638 omap_dmm->engines[i].refill_pa = omap_dmm->refill_pa + in omap_dmm_probe()
640 init_waitqueue_head(&omap_dmm->engines[i].wait_for_refill); in omap_dmm_probe()
642 list_add(&omap_dmm->engines[i].idle_node, &omap_dmm->idle_head); in omap_dmm_probe()
|
| D | omap_dmm_priv.h | 166 struct refill_engine *engines; member
|
| /linux-3.4.99/Documentation/leds/ |
| D | leds-lp5523.txt | 16 The chip provides 3 engines. Each engine can control channels without
20 Control interface for the engines:
|
| D | leds-lp5521.txt | 20 Control interface for the engines:
|
| /linux-3.4.99/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-3.4.99/drivers/hsi/ |
| D | Kconfig | 9 application engines and cellular modems.
|
| /linux-3.4.99/drivers/dma/ |
| D | Kconfig | 9 DMA engines can do asynchronous data transfers without
81 Enable support for the Intel(R) IOP Series RAID engines.
180 Enable support for the AMCC PPC440SPe RAID engines.
274 This enables the use of DMA engines in the network stack to
284 This allows the async_tx api to take advantage of offload engines for
|
| /linux-3.4.99/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 | 30 equal to the number of Descriptor Controller (DECO) engines in a particular
|
| /linux-3.4.99/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 | dmaengine.txt | 137 engines tasklet, never from interrupt context.
|
| 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-3.4.99/tools/perf/ |
| D | Makefile | 556 LIB_OBJS += $(OUTPUT)util/scripting-engines/trace-event-perl.o
818 $(OUTPUT)util/scripting-engines/trace-event-perl.o: util/scripting-engines/trace-event-perl.c $(OUT…
824 $(OUTPUT)util/scripting-engines/trace-event-python.o: util/scripting-engines/trace-event-python.c $…
|
| /linux-3.4.99/drivers/crypto/ |
| D | Kconfig | 261 tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
271 This option enables support for the hardware offload engines in the
|
| /linux-3.4.99/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 20 - fsl,qe-num-riscs: define how many RISC engines the QE has.
|
| /linux-3.4.99/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-3.4.99/Documentation/PCI/ |
| D | pci.txt | 52 Enable DMA/processing engines
266 Enable DMA/processing engines.
483 IRQ handler might restart DMA engines.
|
| /linux-3.4.99/Documentation/power/ |
| D | devices.txt | 602 "on" (how many engines are active?), plus a state that gets back to "on"
|
| /linux-3.4.99/Documentation/RCU/ |
| D | RTFP.txt | 7 and search engines will usually find what you are looking for.
|