Home
last modified time | relevance | path

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

12345

/linux/drivers/staging/media/sunxi/cedrus/
A Dcedrus_video.c40 .directions = CEDRUS_DECODE_SRC,
45 .directions = CEDRUS_DECODE_SRC,
50 .directions = CEDRUS_DECODE_SRC,
55 .directions = CEDRUS_DECODE_SRC,
60 .directions = CEDRUS_DECODE_DST,
64 .directions = CEDRUS_DECODE_DST,
76 static struct cedrus_format *cedrus_find_format(u32 pixelformat, u32 directions, in cedrus_find_format() argument
87 !(fmt->directions & directions)) in cedrus_find_format()
195 if (!(cedrus_formats[i].directions & direction)) in cedrus_enum_fmt()
A Dcedrus_video.h21 u32 directions; member
/linux/tools/testing/selftests/dma/
A Ddma_map_benchmark.c26 static char *directions[] = { variable
145 threads, seconds, node, dir[directions], granule); in main()
/linux/Documentation/ABI/testing/
A Dsysfs-driver-xdata8 in all directions.
33 in all directions.
A Dsysfs-bus-counter74 Y. Two count directions are available: forward and backward.
80 This attribute exposes such count directions.
/linux/tools/testing/vsock/
A DREADME19 Invoke test binaries in both directions as follows:
/linux/Documentation/devicetree/bindings/sound/
A Dadi,axi-i2s.txt4 (capture) or both directions enabled.
A Dnvidia,tegra210-admaif.yaml47 both directions.
A Drockchip,i2s-tdm.yaml75 description: resets for the tx and rx directions
/linux/Documentation/userspace-api/media/v4l/
A Dpixfmt-m420.rst22 directions. Each CbCr pair belongs to four pixels. For example,
/linux/Documentation/fb/
A Dvt8623fb.rst24 * panning in both directions
A Darkfb.rst26 * panning in both directions
A Ds3fb.rst34 * panning in both directions
/linux/net/hsr/
A DKconfig19 device will be sent in both directions on the ring (over both slave
/linux/Documentation/devicetree/bindings/pinctrl/
A Dintel,pinctrl-keembay.yaml14 of pin directions, input/output values and configuration
/linux/Documentation/input/
A 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
/linux/Documentation/sound/designs/
A Dcontrol-names.rst15 <nothing> both directions
A Doss-emulation.rst164 hardware itself does support both directions.
319 To use different values in the two directions, use both
/linux/Documentation/misc-devices/
A Dapds990x.rst28 Driver makes necessary conversions to both directions so that user handles
/linux/drivers/dma/
A Ddmaengine.c589 if (!device->directions) in dma_get_slave_caps()
594 caps->directions = device->directions; in dma_get_slave_caps()
A Dmcf-edma.c263 mcf_edma->dma_dev.directions = in mcf_edma_probe()
/linux/Documentation/devicetree/bindings/ufs/
A Dufshcd-pltfrm.txt55 directions at once. If not specified, default is 2 lanes per direction.
/linux/drivers/dma/ptdma/
A Dptdma-dmaengine.c334 dma_dev->directions = DMA_MEM_TO_MEM; in pt_dmaengine_register()
/linux/include/linux/
A Ddmaengine.h508 u32 directions; member
880 u32 directions; member
/linux/Documentation/sound/soc/
A Ddpcm.rst167 directions should also be set with the ``dpcm_playback`` and ``dpcm_capture``
200 directions using ``dpcm_playback`` and ``dpcm_capture`` above.

Completed in 42 milliseconds

12345