Searched refs:chaining (Results 1 – 22 of 22) sorted by relevance
| /Linux-v5.4/Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 12 and that the descriptor chaining is not only done in the irq/tasklet code
70 c) Transfers hot-chaining
95 restarted. Hot-chaining doesn't break the assumption that
104 - then hot-chaining cannot happen, as the channel must be stopped, the
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | pxa_camera.rst | 134 After the chaining is finished, the chain looks like :
146 c) DMA hot chaining timeslice issue
148 As DMA chaining is done while DMA _is_ running, the linking may be done
|
| /Linux-v5.4/arch/x86/include/asm/uv/ |
| D | uv_bau.h | 336 unsigned int chaining:1; /* next descriptor is part of member
394 unsigned int chaining:1; /* next descriptor is part of member
|
| /Linux-v5.4/Documentation/admin-guide/perf/ |
| D | qcom_l3_pmu.rst | 20 counter chaining. This feature is exposed via the "lc" (long counter) format
|
| /Linux-v5.4/Documentation/x86/i386/ |
| D | IO-APIC.rst | 78 depends on which slot they are in. If you look at the daisy chaining diagram,
97 board does not do default daisy-chaining. (or the IO-APIC has the PIRQ pins
|
| /Linux-v5.4/Documentation/crypto/ |
| D | architecture.rst | 27 chaining mode, the HMAC mechanism, etc.
352 implements the CTR block chaining mode. After performing the block
353 chaining operation, the CIPHER implementation of AES is invoked.
373 step (4) is used and the SKCIPHER block chaining mode is CBC.
|
| /Linux-v5.4/drivers/fsi/ |
| D | Kconfig | 43 allow chaining of FSI links to an arbitrary depth. This allows for
|
| /Linux-v5.4/arch/arm/crypto/ |
| D | Kconfig | 114 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
|
| /Linux-v5.4/Documentation/s390/ |
| D | cds.rst | 270 CCW_FLAG_DC data chaining
271 CCW_FLAG_CC command chaining
349 SCHN_STAT_CHAIN_CHECK chaining check
381 next it can reduce I/O processing overhead by chaining a NoOp I/O command
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | dma.txt | 69 This is a 4-channel DMA controller with extended addresses and chaining,
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | entry-header.S | 87 @ exception frame because of tail-chaining. So these have to be
|
| /Linux-v5.4/Documentation/networking/device_drivers/stmicro/ |
| D | stmmac.txt | 85 the list, hence creating the explicit chaining in the descriptor itself,
86 whereas such explicit chaining is not possible in RING mode.
|
| /Linux-v5.4/drivers/scsi/ |
| D | gdth.h | 598 u8 chaining; /* Chaining supported */ member
|
| /Linux-v5.4/Documentation/networking/ |
| D | 6pack.txt | 159 The 6pack protocol supports daisy-chaining of TNCs in a token ring, which is
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-net | 175 used to resolve interfaces chaining, linking and stacking.
|
| /Linux-v5.4/Documentation/bpf/ |
| D | btf.rst | 213 The ``struct btf_array`` allows chaining through element type to represent
215 information illustrates the chaining:
|
| /Linux-v5.4/Documentation/gpu/ |
| D | drm-kms.rst | 150 Note that currently the bridge chaining and interactions with connectors and
|
| /Linux-v5.4/net/netfilter/ipvs/ |
| D | Kconfig | 51 The IPVS connection hash table uses the chaining scheme to handle
|
| /Linux-v5.4/lib/ |
| D | Kconfig | 599 # sg chaining option
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 18 previous implementation of snapshots did this by chaining together
|
| /Linux-v5.4/Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 213 and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 405 the log vector chaining. If we track by the log vectors, then we only need to
|
