| /linux-4.1.27/include/linux/amba/ |
| D | pl061.h | 14 u8 directions; /* startup directions, 1: out, 0: in */ member
|
| /linux-4.1.27/net/hsr/ |
| D | Kconfig | 15 directions on the ring (over both slave ports), giving a redundant,
|
| /linux-4.1.27/Documentation/fb/ |
| D | vt8623fb.txt | 24 * panning in both directions
|
| D | arkfb.txt | 26 * panning in both directions
|
| D | s3fb.txt | 34 * panning in both directions
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.hfc-pci | 4 to read the echo-channel of the isdn bus. So all frames in both directions
|
| D | INTERFACE.CAPI | 18 directions between the application and the hardware driver.
|
| D | README | 417 directions above. Of course, there may be some limitations. But we have
|
| /linux-4.1.27/arch/cris/boot/rescue/ |
| D | kimagerescue.S | 53 ;; setup port PA and PB default initial directions and data
|
| D | head_v10.S | 231 ;; setup port PA and PB default initial directions and data
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | ControlNames.txt | 6 <nothing> (both directions)
|
| D | OSS-Emulation.txt | 148 hardware itself does support both directions.
290 To use different values in the two directions, use both
|
| D | hda_codec.txt | 169 capture (SNDRV_PCM_STREAM_CAPTURE = 1) directions. The card driver
|
| /linux-4.1.27/drivers/dma/ |
| D | dmaengine.c | 482 if (!device->directions) in dma_get_slave_caps()
487 caps->directions = device->directions; in dma_get_slave_caps()
|
| D | dma-jz4740.c | 546 dd->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in jz4740_dma_probe()
|
| D | bcm2835-dma.c | 597 od->ddev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in bcm2835_dma_probe()
|
| D | dma-jz4780.c | 790 dd->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in jz4780_dma_probe()
|
| D | mxs-dma.c | 853 mxs_dma->dma_device.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in mxs_dma_probe()
|
| D | sirf-dma.c | 719 dma->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in sirfsoc_dma_probe()
|
| D | amba-pl08x.c | 2071 pl08x->memcpy.directions = BIT(DMA_MEM_TO_MEM); in pl08x_probe()
2090 pl08x->slave.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in pl08x_probe()
|
| D | img-mdc-dma.c | 914 mdma->dma_dev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in mdc_dma_probe()
|
| D | qcom_bam_dma.c | 1176 bdev->common.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in bam_dma_probe()
|
| D | edma.c | 999 dma->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in edma_dma_init()
|
| D | mmp_pdma.c | 1077 pdev->device.directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in mmp_pdma_probe()
|
| D | fsldma.c | 1376 fdev->common.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in fsldma_of_probe()
|
| D | sun6i-dma.c | 971 sdc->slave.directions = BIT(DMA_DEV_TO_MEM) | in sun6i_dma_probe()
|
| D | cppi41.c | 934 cdd->ddev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in cppi41_dma_probe()
|
| D | fsl-edma.c | 923 fsl_edma->dma_dev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in fsl_edma_probe()
|
| D | omap-dma.c | 1109 od->ddev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in omap_dma_probe()
|
| D | nbpfaxi.c | 1419 dma_dev->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in nbpf_probe()
|
| D | sa11x0-dma.c | 945 d->slave.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in sa11x0_dma_probe()
|
| D | imx-sdma.c | 1591 sdma->dma_device.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in sdma_probe()
|
| D | tegra20-apb-dma.c | 1436 tdma->dma_dev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in tegra_dma_probe()
|
| D | at_hdmac.c | 1730 atdma->dma_common.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in at_dma_probe()
|
| D | at_xdmac.c | 1509 atxdmac->dma.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in at_xdmac_probe()
|
| D | pl330.c | 2891 pd->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in pl330_probe()
|
| /linux-4.1.27/Documentation/input/ |
| D | gamepad.txt | 50 Analog-sticks provide freely moveable sticks to control directions. Not
116 Every gamepad provides a D-Pad with four directions: Up, Down, Left, Right
|
| D | joystick-api.txt | 77 directions, some only in 4, The driver, however, always reports a hat as two
|
| /linux-4.1.27/include/linux/ |
| D | dmaengine.h | 381 u32 directions; member
630 u32 directions; member
|
| /linux-4.1.27/Documentation/misc-devices/ |
| D | apds990x.txt | 25 Driver makes necessary conversions to both directions so that user handles
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | DPCM.txt | 161 directions should also be set with the "dpcm_playback" and "dpcm_capture"
193 directions using "dpcm_playback" and "dpcm_capture" above.
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-iio | 205 the underlying value in the specified directions.
663 If separate attributes exist for the two directions, but
665 threshold value applies to both directions.
745 If separate attributes exist for the two directions, but
747 hysteresis value applies to both directions.
794 If separate attributes exist for the two directions,
796 then a single threshold value applies to both directions.
881 specified then this period applies to both directions.
|
| /linux-4.1.27/drivers/gpio/ |
| D | gpio-pl061.c | 312 if (pdata->directions & (BIT(i))) in pl061_probe()
|
| /linux-4.1.27/drivers/dma/hsu/ |
| D | hsu.c | 465 hsu->dma.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in hsu_dma_probe()
|
| /linux-4.1.27/Documentation/arm/ |
| D | IXP4xx | 53 There are several websites that provide directions/pointers on using
|
| /linux-4.1.27/Documentation/networking/caif/ |
| D | spi_porting.txt | 36 of the transfer in both directions.The dev parameter can be used
|
| /linux-4.1.27/drivers/dma/sh/ |
| D | rcar-hpbdma.c | 602 dma_dev->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in hpb_dmae_probe()
|
| D | usb-dmac.c | 840 engine->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in usb_dmac_probe()
|
| D | shdmac.c | 753 dma_dev->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in sh_dmae_probe()
|
| D | rcar-dmac.c | 1705 engine->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in rcar_dmac_probe()
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | provider.txt | 123 * directions:
124 - should contain a bitmask of the supported slave directions
|
| /linux-4.1.27/Documentation/networking/ |
| D | dccp.txt | 90 type of CCID for both directions; and mixed use of CCIDs is not currently well
|
| /linux-4.1.27/Documentation/scsi/ |
| D | advansys.txt | 195 Nathan Hartwell <mage@cdc3.cdc.net> provided the directions and
|
| /linux-4.1.27/arch/cris/arch-v10/ |
| D | Kconfig | 360 kernel I2C driver sets the appropriate directions itself so you
|
| /linux-4.1.27/arch/cris/arch-v32/drivers/ |
| D | Kconfig | 182 Remember that you need to setup the port directions appropriately in
|
| /linux-4.1.27/Documentation/target/ |
| D | tcmu-design.txt | 102 mechanisms in both directions.
|
| /linux-4.1.27/Documentation/ |
| D | vme_api.txt | 261 for a DMA channel purely checks the directions in which the
|
| D | ManagementStyle | 199 specific directions, but let's face it, they might be good at what they
|
| /linux-4.1.27/Documentation/fmc/ |
| D | carrier.txt | 109 * sdb: FPGA contents, scanned according to driver's directions.
|
| /linux-4.1.27/arch/cris/arch-v10/kernel/ |
| D | head.S | 499 ;; setup port PA and PB default initial directions and data
|
| /linux-4.1.27/arch/cris/arch-v10/drivers/ |
| D | Kconfig | 517 Remember that you need to setup the port directions appropriately in
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.txt | 334 Future directions:
|
| /linux-4.1.27/drivers/dma/dw/ |
| D | core.c | 1678 dw->dma.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV) | in dw_dma_probe()
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 2.Process | 329 directions. The whole thing would not work anywhere near as well as it
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 305 which has directions on getting the sources. You can also browse the
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | fpsp.S | 16337 # Typically, only one of the two possible branch directions could #
|