Home
last modified time | relevance | path

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

1234

/Linux-v4.19/tools/testing/vsock/
DREADME18 Invoke test binaries in both directions as follows:
/Linux-v4.19/net/hsr/
DKconfig15 directions on the ring (over both slave ports), giving a redundant,
/Linux-v4.19/Documentation/media/uapi/v4l/
Dpixfmt-m420.rst22 directions. Each CbCr pair belongs to four pixels. For example,
Dselection-api-configuration.rst14 vertical directions. Also it may not support scaling at all. At the same
/Linux-v4.19/Documentation/fb/
Dvt8623fb.txt24 * panning in both directions
Darkfb.txt26 * panning in both directions
Ds3fb.txt34 * panning in both directions
/Linux-v4.19/Documentation/isdn/
DREADME.hfc-pci4 to read the echo-channel of the isdn bus. So all frames in both directions
/Linux-v4.19/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
/Linux-v4.19/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
/Linux-v4.19/Documentation/devicetree/bindings/ufs/
Dufshcd-pltfrm.txt43 directions at once. If not specified, default is 2 lanes per direction.
/Linux-v4.19/Documentation/misc-devices/
Dapds990x.txt25 Driver makes necessary conversions to both directions so that user handles
/Linux-v4.19/drivers/dma/
Ddmaengine.c492 if (!device->directions) in dma_get_slave_caps()
497 caps->directions = device->directions; in dma_get_slave_caps()
Ddma-jz4740.c544 dd->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in jz4740_dma_probe()
Dstm32-dma.c1279 dd->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in stm32_dma_probe()
1288 dd->directions |= BIT(DMA_MEM_TO_MEM); in stm32_dma_probe()
/Linux-v4.19/Documentation/networking/
Dnf_flowtable.txt12 in both directions), then you can decide to offload the flow to the flowtable
/Linux-v4.19/include/linux/
Ddmaengine.h429 u32 directions; member
755 u32 directions; member
/Linux-v4.19/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.
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-bus-iio209 from the pad's size in both directions. Should be calibrated by
258 the underlying value in the specified directions.
759 If separate attributes exist for the two directions, but
761 threshold value applies to both directions.
841 If separate attributes exist for the two directions, but
843 hysteresis value applies to both directions.
890 If separate attributes exist for the two directions,
892 then a single threshold value applies to both directions.
977 specified then this period applies to both directions.
1672 A list of possible counting directions which are:
/Linux-v4.19/drivers/dma/hsu/
Dhsu.c473 hsu->dma.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in hsu_dma_probe()
/Linux-v4.19/Documentation/arm/
DIXP4xx53 There are several websites that provide directions/pointers on using
/Linux-v4.19/Documentation/networking/caif/
Dspi_porting.txt36 of the transfer in both directions.The dev parameter can be used
/Linux-v4.19/drivers/staging/most/Documentation/ABI/
Dsysfs-bus-most.txt176 Indicates the directions the current channel is capable of.
/Linux-v4.19/drivers/dma/ti/
Dedma.c1850 s_ddev->directions = BIT(DMA_MEM_TO_MEM); in edma_dma_init()
1867 s_ddev->directions |= (BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV)); in edma_dma_init()
1899 m_ddev->directions = BIT(DMA_MEM_TO_MEM); in edma_dma_init()

1234