Home
last modified time | relevance | path

Searched refs:engines (Results 1 – 45 of 45) sorted by relevance

/linux-4.4.14/drivers/crypto/marvell/
Dcesa.c124 spin_lock_bh(&cesa_dev->engines[i].lock); in mv_cesa_queue_req()
125 if (!cesa_dev->engines[i].req) in mv_cesa_queue_req()
126 mv_cesa_dequeue_req_unlocked(&cesa_dev->engines[i]); in mv_cesa_queue_req()
127 spin_unlock_bh(&cesa_dev->engines[i].lock); in mv_cesa_queue_req()
320 struct mv_cesa_engine *engine = &cesa->engines[idx]; in mv_cesa_get_sram()
362 struct mv_cesa_engine *engine = &cesa->engines[idx]; in mv_cesa_put_sram()
378 struct mv_cesa_engine *engines; in mv_cesa_probe() local
413 cesa->engines = devm_kzalloc(dev, caps->nengines * sizeof(*engines), in mv_cesa_probe()
415 if (!cesa->engines) in mv_cesa_probe()
434 struct mv_cesa_engine *engine = &cesa->engines[i]; in mv_cesa_probe()
[all …]
Dcesa.h414 struct mv_cesa_engine *engines; member
/linux-4.4.14/Documentation/netlabel/
Dintroduction.txt12 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.4.14/Documentation/ABI/testing/
Dsysfs-bus-hsi8 engines (APE) with cellular modem engines (CMT) in cellular
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/fifo/
Dgpfifogk104.c215 u32 engines; in gk104_fifo_gpfifo_new() local
228 for (i = 0, engines = 0; i < ARRAY_SIZE(fifo->engine); i++) { in gk104_fifo_gpfifo_new()
232 engines |= (1 << i); in gk104_fifo_gpfifo_new()
237 args->v0.engine = engines; in gk104_fifo_gpfifo_new()
245 args->v0.engine &= engines; in gk104_fifo_gpfifo_new()
Dchan.c208 u64 mask = chan->engines; in nvkm_fifo_chan_child_get()
350 u64 vm, u64 push, u64 engines, int bar, u32 base, u32 user, in nvkm_fifo_chan_ctor() argument
364 chan->engines = engines; in nvkm_fifo_chan_ctor()
Dchan.h23 u64 engines, int bar, u32 base, u32 user,
/linux-4.4.14/drivers/gpu/drm/omapdrm/
Domap_dmm_tiler.c151 if (dmm->engines[i].async) in omap_dmm_irq_handler()
152 release_engine(&dmm->engines[i]); in omap_dmm_irq_handler()
154 complete(&dmm->engines[i].compl); in omap_dmm_irq_handler()
571 kfree(omap_dmm->engines); in omap_dmm_remove()
710 omap_dmm->engines = kcalloc(omap_dmm->num_engines, in omap_dmm_probe()
712 if (!omap_dmm->engines) { in omap_dmm_probe()
718 omap_dmm->engines[i].id = i; in omap_dmm_probe()
719 omap_dmm->engines[i].dmm = omap_dmm; in omap_dmm_probe()
720 omap_dmm->engines[i].refill_va = omap_dmm->refill_va + in omap_dmm_probe()
722 omap_dmm->engines[i].refill_pa = omap_dmm->refill_pa + in omap_dmm_probe()
[all …]
Domap_dmm_priv.h174 struct refill_engine *engines; member
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/
Dppc440spe-adma.txt5 for DMA engines and Memory Queue Module node. The latter is used
40 for both DMA engines>.
/linux-4.4.14/drivers/hsi/
DKconfig9 application engines and cellular modems.
/linux-4.4.14/drivers/gpu/drm/mgag200/
DKconfig2 tristate "Kernel modesetting driver for MGA G200 server engines"
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Dpicochip-spacc.txt3 Picochip picoXcell devices contain crypto offload engines that may be used for
Dmv_cesa.txt15 - clocks: reference to the crypto engines clocks. This property is only
Dmarvell-cesa.txt19 - clocks: reference to the crypto engines clocks. This property is not
Dfsl-sec4.txt31 equal to the number of Descriptor Controller (DECO) engines in a particular
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/engine/
Dfifo.h17 u64 engines; member
/linux-4.4.14/drivers/leds/
Dleds-lp5523.c405 enum lp55xx_engine_mode mode = chip->engines[nr - 1].mode; in show_engine_mode()
427 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in store_engine_mode()
496 lp5523_mux_to_array(chip->engines[nr - 1].led_mux, mux); in show_engine_leds()
506 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in lp5523_load_mux()
538 struct lp55xx_engine *engine = &chip->engines[nr - 1]; in store_engine_leds()
DKconfig244 LP5521 LED driver. It is 3 channel chip with programmable engines.
246 programming the engines.
255 It is 9 channel chip with programmable engines.
257 programming the engines.
265 It is 4 channels chip with programmable engines.
267 programming the engines.
275 It is 9 channel chip with programmable engines.
277 programming the engines.
Dleds-lp55xx-common.h157 struct lp55xx_engine engines[LP55XX_ENGINE_MAX]; member
Dleds-lp5521.c383 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()
Dleds-lp55xx-common.c209 chip->engines[idx - 1].mode = LP55XX_ENGINE_LOAD; in lp55xx_firmware_loaded()
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dmv-xor.txt1 * Marvell XOR engines
/linux-4.4.14/Documentation/
DIntel-IOMMU.txt21 ACPI enumerates and lists the different DMA engines in the platform, and
49 Different DMA engines may support different number of domains.
Dedac.txt41 along with DMA engines, fabric switches, main data path switches,
Dkernel-docs.txt712 * Name: "linux-kernel mailing list archives and search engines"
/linux-4.4.14/drivers/net/ethernet/cavium/
DKconfig22 The NIC provides the controller and DMA engines to
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dgpmc-nand.txt45 ELM hardware engines should specify this device node in .dtsi
101 (1) support of built in hardware engines.
/linux-4.4.14/Documentation/hwmon/
Dnct668319 It supports up to 16 fan rotation sensors and up to 8 fan control engines.
/linux-4.4.14/Documentation/leds/
Dleds-lp5521.txt24 Control interface for the engines:
Dleds-lp5523.txt34 Control interface for the engines:
Dleds-lp55xx.txt64 LP55xx chips have three program engines.
/linux-4.4.14/drivers/dma/
DKconfig9 DMA engines can do asynchronous data transfers without
76 Enable support for the AMCC PPC440SPe RAID engines.
260 Enable support for the Intel(R) IOP Series RAID engines.
544 This allows the async_tx api to take advantage of offload engines for
/linux-4.4.14/Documentation/crypto/
Dasync-tx-api.txt37 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.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dqe.txt20 - fsl,qe-num-riscs: define how many RISC engines the QE has.
/linux-4.4.14/tools/perf/util/
DBuild107 libperf-y += scripting-engines/
/linux-4.4.14/drivers/crypto/
DKconfig312 tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
323 This option enables support for the hardware offload engines in the
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt32 storage. These are called "backstores" or "storage engines". These
40 or "storage engines". The target comes with backstores that allow a
/linux-4.4.14/Documentation/dmaengine/
Dclient.txt138 engines tasklet, never from interrupt context.
/linux-4.4.14/Documentation/PCI/
Dpci.txt52 Enable DMA/processing engines
248 Enable DMA/processing engines.
465 IRQ handler might restart DMA engines.
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dvideo-interfaces.txt8 video DMA engines and video data processors.
/linux-4.4.14/Documentation/trace/
Dcoresight.txt15 that have many SoCs and other components like GPU and DMA engines. ARM has
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dfman.txt18 Due to the fact that the FMan is an aggregation of sub-engines (ports, MACs,
/linux-4.4.14/Documentation/power/
Ddevices.txt637 "on" (how many engines are active?), plus a state that gets back to "on"
/linux-4.4.14/Documentation/RCU/
DRTFP.txt7 and search engines will usually find what you are looking for.