Home
last modified time | relevance | path

Searched refs:directions (Results 1 – 25 of 104) sorted by relevance

12345

/kernel/linux/linux-5.10/drivers/staging/media/sunxi/cedrus/
Dcedrus_video.c40 .directions = CEDRUS_DECODE_SRC,
44 .directions = CEDRUS_DECODE_SRC,
48 .directions = CEDRUS_DECODE_SRC,
53 .directions = CEDRUS_DECODE_DST,
57 .directions = CEDRUS_DECODE_DST,
69 static struct cedrus_format *cedrus_find_format(u32 pixelformat, u32 directions, in cedrus_find_format() argument
80 !(fmt->directions & directions)) in cedrus_find_format()
187 if (!(cedrus_formats[i].directions & direction)) in cedrus_enum_fmt()
Dcedrus_video.h21 u32 directions; member
/kernel/linux/linux-5.10/tools/testing/vsock/
DREADME19 Invoke test binaries in both directions as follows:
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dadi,axi-i2s.txt4 (capture) or both directions enabled.
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-m420.rst22 directions. Each CbCr pair belongs to four pixels. For example,
/kernel/linux/linux-5.10/Documentation/fb/
Dvt8623fb.rst24 * panning in both directions
Darkfb.rst26 * panning in both directions
Ds3fb.rst34 * panning in both directions
/kernel/linux/linux-5.10/net/hsr/
DKconfig19 device will be sent in both directions on the ring (over both slave
/kernel/linux/linux-5.10/Documentation/sound/designs/
Dcontrol-names.rst15 <nothing> both directions
Doss-emulation.rst164 hardware itself does support both directions.
319 To use different values in the two directions, use both
/kernel/linux/linux-5.10/Documentation/input/
Dgamepad.rst55 Analog-sticks provide freely moveable sticks to control directions. Not
132 Every gamepad provides a D-Pad with four directions: Up, Down, Left, Right
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-counter73 Y. Two count directions are available: forward and backward.
79 This attribute exposes such count directions.
Dsysfs-bus-iio216 from the pad's size in both directions. Should be calibrated by
265 the underlying value in the specified directions.
782 If separate attributes exist for the two directions, but
784 threshold value applies to both directions.
865 If separate attributes exist for the two directions, but
867 hysteresis value applies to both directions.
916 If separate attributes exist for the two directions,
918 then a single threshold value applies to both directions.
1004 specified then this period applies to both directions.
1733 A list of possible counting directions which are:
/kernel/linux/linux-5.10/Documentation/misc-devices/
Dapds990x.rst28 Driver makes necessary conversions to both directions so that user handles
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/ufs/
Dufshcd-pltfrm.txt53 directions at once. If not specified, default is 2 lanes per direction.
/kernel/linux/linux-5.10/drivers/dma/
Ddmaengine.c590 if (!device->directions) in dma_get_slave_caps()
595 caps->directions = device->directions; in dma_get_slave_caps()
Dmcf-edma.c264 mcf_edma->dma_dev.directions = in mcf_edma_probe()
Duniphier-mdmac.c419 ddev->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in uniphier_mdmac_probe()
Dfsl-edma.c393 fsl_edma->dma_dev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in fsl_edma_probe()
/kernel/linux/linux-5.10/Documentation/networking/
Dnf_flowtable.rst15 in both directions), then you can decide to offload the flow to the flowtable
/kernel/linux/linux-5.10/Documentation/sound/soc/
Ddpcm.rst167 directions should also be set with the ``dpcm_playback`` and ``dpcm_capture``
200 directions using ``dpcm_playback`` and ``dpcm_capture`` above.
/kernel/linux/linux-5.10/include/linux/
Ddmaengine.h500 u32 directions; member
869 u32 directions; member
/kernel/linux/linux-5.10/drivers/dma/hsu/
Dhsu.c466 hsu->dma.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in hsu_dma_probe()
/kernel/linux/linux-5.10/Documentation/arm/
Dixp4xx.rst53 There are several websites that provide directions/pointers on using

12345