/linux-4.4.14/Documentation/bus-devices/ |
D | ti-gpmc.txt | 20 functioning of the peripheral, while peripheral has another set of 21 timings. To have peripheral work with gpmc, peripheral timings has to 23 translated depends on the connected peripheral. Also there is a 28 from gpmc peripheral timings. struct gpmc_device_timings fields has to 29 be updated with timings from the datasheet of the peripheral that is 30 connected to gpmc. A few of the peripheral timings can be fed either 33 happen that timing as specified by peripheral datasheet is not present 34 in timing structure, in this scenario, try to correlate peripheral 36 field as required by peripheral, educate generic timing routine to 38 Then there may be cases where peripheral datasheet doesn't mention [all …]
|
/linux-4.4.14/Documentation/devicetree/bindings/display/ |
D | mipi-dsi-bus.txt | 15 The following assumes that only a single peripheral is connected to a DSI 32 DSI peripheral 40 - reg: The virtual channel number of a DSI peripheral. Must be in the range 46 that the peripheral responds to. 47 - If the virtual channels that a peripheral responds to are consecutive, the 61 /* peripheral responds to virtual channel 0 */ 62 peripheral@0 { 76 /* peripheral responds to virtual channels 0 and 2 */ 77 peripheral@0 { 91 /* peripheral responds to virtual channels 1, 2 and 3 */ [all …]
|
/linux-4.4.14/Documentation/devicetree/bindings/clock/ |
D | pistachio-clock.txt | 4 Pistachio has four clock controllers (core clock, peripheral clock, peripheral 47 The peripheral clock controller generates clocks for the DDR, ROM, and other 48 peripherals. The peripheral system clock ("periph_sys") generated by the core 49 clock controller is the input clock to the peripheral clock controller. 53 - reg: Must contain the base address and length of the peripheral clock 58 - clock-names: Must include "periph_sys", the peripheral system clock generated 74 The peripheral general control block generates system interface clocks and 75 resets for various peripherals. It also contains miscellaneous peripheral 76 control registers. The system clock ("sys") generated by the peripheral clock 81 - reg: Must contain the base address and length of the peripheral general [all …]
|
D | ste-u300-syscon-clock.txt | 21 0 0 Slow peripheral bridge clock 28 1 0 Fast peripheral bridge clock 31 1 5 MMC interface peripheral (silicon) clock
|
D | lpc1850-cgu.txt | 4 peripheral blocks of the LPC18xx. Each independent clock is called 51 and APB peripheral blocks #0 and #2 56 9 BASE_APB1_CLK Base clock for APB peripheral block # 1 57 10 BASE_APB3_CLK Base clock for APB peripheral block # 3
|
D | at91-clock.txt | 45 "atmel,at91sam9x5-clk-peripheral" or 46 "atmel,at91rm9200-clk-peripheral": 47 at91 peripheral clocks 249 Required properties for peripheral clocks: 254 - name: device tree node describing a specific peripheral clock. 256 * reg: peripheral id. See Atmel's datasheets to get a full 257 list of peripheral ids. 259 (two u32 fields). Only valid on at91sam9x5-clk-peripheral 264 compatible = "atmel,at91sam9x5-clk-peripheral"; 475 * reg: peripheral id. See Atmel's datasheets to get a full [all …]
|
D | ux500.txt | 17 PRCC (programmable reset- and clock controller) peripheral clocks. 38 * Registers for the CLKRST block on peripheral
|
D | ti-keystone-pllctrl.txt | 4 and a majority of the peripheral clocks (all but the ARM CorePacs, DDR3 and
|
D | calxeda.txt | 10 "calxeda,hb-a9periph-clock" - The A9 peripheral clock divided from the
|
D | altr_socfpga.txt | 10 "altr,socfpga-perip-clock" - The peripheral clock divided from the
|
D | alphascale,acc.txt | 20 _SYS_ - adjustable clock source. Not all peripheral have _SYS_ clock provider.
|
D | mvebu-gated-clock.txt | 4 peripheral clocks to be gated to save some power. The clock consumer
|
D | qoriq-clock.txt | 7 cores and peripheral IP blocks.
|
D | exynos5433-clock.txt | 30 which generates global data buses clock and global peripheral buses clock.
|
D | sunxi.txt | 13 "allwinner,sun9i-a80-pll4-clk" - for the peripheral PLLs on A80
|
/linux-4.4.14/Documentation/devicetree/bindings/phy/ |
D | hix5hd2-phy.txt | 11 - hisilicon,peripheral-syscon: phandle of syscon used to control peripheral. 12 - hisilicon,power-reg: offset and bit number within peripheral-syscon, 20 hisilicon,peripheral-syscon = <&peripheral_ctrl>;
|
D | nvidia,tegra20-usb-phy.txt | 64 "host", "peripheral", or "otg". Defaults to "host" if not defined. 66 peripheral means it is device controller
|
/linux-4.4.14/Documentation/devicetree/bindings/display/panel/ |
D | sharp,lq101r1sx01.txt | 7 Each of the DSI channels controls a separate DSI peripheral. The peripheral 9 peripheral and controls the device. The 'link2' property contains a phandle 10 to the peripheral driven by the second link (DSI-LINK2, right or odd). 20 - reg: DSI virtual channel of the peripheral 23 - link2: phandle to the DSI peripheral on the secondary link. Note that the
|
D | samsung,s6e8aa0.txt | 5 - reg: the virtual channel number of a DSI peripheral
|
/linux-4.4.14/Documentation/devicetree/bindings/usb/ |
D | atmel-usb.txt | 10 - clocks: Should reference the peripheral, host and system clocks 12 "ohci_clk" for the peripheral clock 37 - clocks: Should reference the peripheral and the UTMI clocks 39 "ehci_clk" for the peripheral clock 60 - clocks: Should reference the peripheral and the AHB clocks 62 "pclk" for the peripheral clock 87 - clocks: Should reference the peripheral and host clocks 89 "pclk" for the peripheral clock
|
D | ux500-usb.txt | 7 - dr_mode : Dual-role; either host mode "host", peripheral mode "peripheral"
|
D | msm-hsusb.txt | 53 - dr_mode: One of "host", "peripheral" or "otg". Defaults to "otg" 93 dr_mode = "peripheral";
|
D | dwc2.txt | 21 - dr_mode: shall be one of "host", "peripheral" and "otg"
|
D | generic.txt | 11 "peripheral" and "otg". In case this attribute isn't
|
D | fsl-usb.txt | 27 controllers. Can be "host", "peripheral", or "otg". Default to
|
D | ci-hdrc-usb2.txt | 17 - dr_mode: One of "host", "peripheral" or "otg". Defaults to "otg"
|
D | am33xx-usb.txt | 38 - dr_mode: Should be one of "host", "peripheral" or "otg".
|
/linux-4.4.14/Documentation/devicetree/bindings/dma/ |
D | atmel-xdma.txt | 15 - bit 14: DIF, destination interface identifier, used to get the peripheral 17 - bit 30-24: PERID, peripheral identifier. 37 - bit 14: DIF, destination interface identifier, used to get the peripheral 39 - bit 30-24: PERID, peripheral identifier.
|
D | fsl-imx-sdma.txt | 22 The second cell of dma phandle specifies the peripheral type of DMA transfer. 23 The full ID of peripheral types can be found below. 39 12 External peripheral
|
D | atmel-dma.txt | 25 2. The memory interface (16 most significant bits), the peripheral interface 29 - bit 7-0: peripheral identifier for the hardware handshaking interface. The
|
D | img-mdc-dma.txt | 11 - img,cr-periph: Must contain a phandle to the peripheral control syscon 17 - The first cell is the peripheral's DMA request line.
|
D | tegra20-apbdma.txt | 16 select value for the peripheral. For more details, consult the Tegra TRM's
|
D | mpc512x-dma.txt | 16 Each channel of this DMA controller has a peripheral request line,
|
D | lpc1850-dmamux.txt | 8 * 2nd cell contain the mux value (0-3) for the peripheral
|
D | qcom_adm.txt | 45 The CRCI is used for flow control. It identifies the peripheral device that
|
D | adi,axi-dmac.txt | 13 configuration options of the peripheral as it was instantiated.
|
/linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
D | qcom,spmi-pmic.txt | 37 Required properties for peripheral child nodes: 38 - compatible: Should contain "qcom,xxx", where "xxx" is a peripheral name. 40 Optional properties for peripheral child nodes: 47 example below the rtc device node represents a peripheral of pm8941 48 SID = 0. The regulator device node represents a peripheral of pm8941 SID = 1.
|
D | atmel-flexcom.txt | 11 - clocks: Should be the Flexcom peripheral clock from PMC.
|
/linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
D | samsung,sysmmu.txt | 4 physical memory chunks visible as a contiguous region to DMA-capable peripheral 13 System MMUs are in many to one relation with peripheral devices, i.e. single 14 peripheral device might have multiple System MMUs (usually one for each bus 15 master), but one System MMU can handle transactions from only one peripheral 16 device. The relation between a System MMU and the peripheral device needs to be 17 defined in device node of the peripheral device.
|
/linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
D | i2c-sunxi-p2wi.txt | 9 - interrupts : The interrupt line connected to the P2WI peripheral. 10 - clocks : The gate clk connected to the P2WI peripheral. 11 - resets : The reset line connected to the P2WI peripheral.
|
/linux-4.4.14/Documentation/devicetree/bindings/input/ |
D | ti,nspire-keypad.txt | 6 - reg: Physical base address of the peripheral and length of memory mapped 9 - interrupts: The interrupt number for the peripheral. 16 - clocks: The clock this peripheral is attached to.
|
/linux-4.4.14/drivers/clk/qcom/ |
D | Kconfig | 18 Say Y if you want to use peripheral devices such as UART, SPI, 36 Say Y if you want to use peripheral devices such as UART, SPI, 53 Say Y if you want to use peripheral devices such as UART, SPI, 70 Say Y if you want to use peripheral devices such as UART, SPI, 97 Say Y if you want to use peripheral devices such as UART, SPI,
|
/linux-4.4.14/sound/soc/adi/ |
D | Kconfig | 13 ASoC driver for the Analog Devices AXI-I2S softcore peripheral. 21 ASoC driver for the Analog Devices AXI-SPDIF softcore peripheral.
|
/linux-4.4.14/drivers/usb/ |
D | README | 6 "gadget.pdf" for peripheral side.) Also, Documentation/usb has 15 host controllers (on PCs, servers, and more); peripheral 19 * Specifications for other protocols implemented by USB peripheral 33 gadget/ - This is for USB peripheral controller drivers and
|
D | Kconfig | 66 If your system has a device-side USB port, used in the peripheral
|
/linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
D | k3-dw-mshc.txt | 19 - hisilicon,peripheral-syscon: phandle of syscon used to control peripheral. 61 hisilicon,peripheral-syscon = <&ao_ctrl>;
|
D | sdhci-msm.txt | 17 "iface" - Main peripheral bus clock (PCLK/HCLK - AHB Bus clock) (required)
|
/linux-4.4.14/Documentation/devicetree/bindings/spmi/ |
D | qcom,spmi-pmic-arb.txt | 33 single interrupt entry for the peripheral interrupt 40 cell 2: peripheral ID for requested interrupt (0-255) 41 cell 3: the requested peripheral interrupt (0-7)
|
/linux-4.4.14/Documentation/i2c/busses/ |
D | i2c-ismt | 35 00:13.0 System peripheral: Intel Corporation Centerton SMBus 2.0 Controller 0 36 00:13.1 System peripheral: Intel Corporation Centerton SMBus 2.0 Controller 1
|
/linux-4.4.14/Documentation/blackfin/ |
D | bfin-spi-notes.txt | 3 With the Blackfin on-chip SPI peripheral, there is some logic tied to the CPHA 15 You can even use the same pin whose peripheral role is a SSEL,
|
D | bfin-gpio-notes.txt | 23 multi-functions. They can be configured as peripheral, or just as GPIO, 33 - Use the pin as peripheral,
|
/linux-4.4.14/drivers/usb/gadget/udc/ |
D | Kconfig | 3 # (a) a peripheral controller, and 157 R8A66597 is a discrete USB host and peripheral controller chip that 169 Renesas USBHS is a discrete USB host and peripheral controller chip 221 full speed USB peripheral. 228 controller, which support super speed USB peripheral. 237 M66592 is a discrete USB peripheral controller chip that 259 if it's not being used to implement peripheral or OTG roles. 281 PLX NET2272 is a USB peripheral controller which supports 304 NetChip 2280 / 2282 is a PCI based USB peripheral controller which 311 PLX 3380 / 3382 is a PCIe based USB peripheral controller which [all …]
|
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
D | img,pdc-intc.txt | 27 shared SysWake interrupt, and remaining specifies shall be PDC peripheral 39 flags as follows (only 4 valid for peripheral interrupts): 82 * An SoC peripheral that is wired through the PDC.
|
D | brcm,bcm2836-l1-intc.txt | 5 peripheral (GPU) events, which chain to the BCM2835-style interrupt
|
D | snps,archs-idu-intc.txt | 14 First cell specifies the "common" IRQ from peripheral to IDU
|
D | brcm,bcm7038-l1-intc.txt | 14 peripheral IRQs to be routed to any CPU
|
/linux-4.4.14/drivers/usb/isp1760/ |
D | Kconfig | 44 Select this if you want to use the ISP1760 in peripheral mode only. 55 peripheral modes.
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/ |
D | primecell.txt | 4 identify the peripheral type, vendor, and revision. This value can be used for 9 - compatible : should be a specific name for the peripheral and
|
D | spear-misc.txt | 4 few properties of different peripheral controllers.
|
D | sp810.txt | 6 - compatible: standard compatible string for a Primecell peripheral,
|
/linux-4.4.14/Documentation/ |
D | SM501.txt | 24 peripheral set as platform devices for the specific drivers. 34 Each peripheral has a view of the device which is implicitly narrowed to 35 the specific set of resources that peripheral requires in order to
|
D | smsc_ece1099.txt | 36 a computer host and its peripheral devices. The SMBus data
|
D | parport-lowlevel.txt | 157 for reverse (peripheral to host) 662 0 handshake OK; IEEE 1284 peripheral and mode available 663 -1 handshake failed; peripheral not compliant (or none present) 664 1 handshake OK; IEEE 1284 peripheral present but mode not 922 delays at the peripheral. After the peripheral has not responded for 1162 Enables the data line drivers, for 8-bit host-to-peripheral
|
D | ramoops.txt | 88 You can specify either RAM memory or peripheral devices' memory. However, when
|
D | phy.txt | 53 The PHY driver should create the PHY in order for other peripheral controllers
|
D | parport.txt | 175 for the peripheral to respond. You might find that
|
D | remoteproc.txt | 262 * @RSC_DEVMEM: request to iommu_map a memory-based peripheral.
|
/linux-4.4.14/Documentation/devicetree/bindings/reset/ |
D | nxp,lpc1850-rgu.txt | 14 See table below for valid peripheral reset numbers. Numbers not 62 the reset signals and the connected block/peripheral.
|
D | brcm,bcm63138-pmb.txt | 12 by the phandle, and the second is the number of zones for this peripheral
|
D | st,sti-softreset.txt | 5 disable on-chip peripheral controllers such as USB and SATA, using
|
D | st,sti-powerdown.txt | 5 disable on-chip peripheral controllers such as USB and SATA, using
|
/linux-4.4.14/Documentation/devicetree/ |
D | overlay-notes.txt | 48 /* bar peripheral */ 61 /* FOO platform + bar peripheral */ 74 /* bar peripheral */
|
/linux-4.4.14/drivers/usb/gadget/ |
D | Kconfig | 3 # (a) a peripheral controller, and 21 host (such as a PC) controlling up to 127 peripheral devices. 23 you can't connect a "to-the-host" connector to a peripheral. 25 Linux can run in the host, or in the peripheral. In both cases 34 a USB peripheral device. Configure one hardware driver for your 35 peripheral/device side bus controller, and a "gadget driver" for 36 your peripheral protocol. (If you use modular gadget drivers, 81 (for a peripheral controller). The information in these 211 the peripheral hardware. 358 USB peripheral controller driver. Then you can use host-side
|
/linux-4.4.14/arch/powerpc/platforms/52xx/ |
D | mpc52xx_pic.c | 496 goto peripheral; in mpc52xx_get_irq() 501 goto peripheral; in mpc52xx_get_irq() 504 peripheral: in mpc52xx_get_irq()
|
/linux-4.4.14/Documentation/devicetree/bindings/serial/ |
D | atmel-usart.txt | 18 It will use specified PIO instead of the peripheral function pin for the USART feature. 22 memory peripheral interface and USART DMA channel ID, FIFO configuration.
|
D | digicolor-usart.txt | 3 Note: this binding is only applicable for using the USART peripheral as
|
D | fsl-mxs-auart.txt | 18 line respectively. It will use specified PIO instead of the peripheral
|
D | snps-dw-apb-uart.txt | 13 The supplying peripheral clock can also be handled, needing a second property
|
/linux-4.4.14/Documentation/devicetree/bindings/ |
D | common-properties.txt | 11 know the peripheral always needs to be accessed in BE mode. 14 peripheral always needs to be accessed in LE mode.
|
/linux-4.4.14/Documentation/devicetree/bindings/media/ |
D | exynos4-fimc-is.txt | 5 processor, ISP, DRC and FD IP blocks and peripheral devices such as UART, I2C 29 The following are the FIMC-IS peripheral device nodes and can be specified
|
/linux-4.4.14/drivers/usb/mon/ |
D | Kconfig | 9 between peripheral-specific drivers and HC drivers will be built.
|
/linux-4.4.14/drivers/clk/at91/ |
D | Makefile | 7 obj-y += clk-system.o clk-peripheral.o clk-programmable.o
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-platform-chipidea-usb-otg | 9 the bus(or wants to work as peripheral). a_bus_req can also 41 work as host and decides to switch back to be peripheral.
|
D | sysfs-platform-tahvo-usb | 6 "peripheral".
|
/linux-4.4.14/Documentation/devicetree/bindings/nvmem/ |
D | vf610-ocotp.txt | 9 clocks : ipg clock we associate with the OCOTP peripheral
|
D | imx-ocotp.txt | 12 - clocks: Should contain a phandle pointing to the gated peripheral clock.
|
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
D | atmel,at91-pinctrl.txt | 28 Each column will represent the possible peripheral of the pinctrl 41 For each peripheral/bank we will descibe in a u32 if a pin can be 44 Let's take the pioA on peripheral B
|
D | img,tz1090-pinctrl.txt | 70 function which enables them with their intended peripheral. 76 by GPIO, and you don't want the usual peripheral to have any control of the
|
D | fsl,mxs-pinctrl.txt | 33 means a group of pins put together for particular peripheral to work in
|
/linux-4.4.14/drivers/usb/renesas_usbhs/ |
D | Kconfig | 12 Renesas USBHS is a discrete USB host and peripheral controller chip
|
/linux-4.4.14/Documentation/devicetree/bindings/timer/ |
D | brcm,bcm2835-system-timer.txt | 3 The System Timer peripheral provides four 32-bit timer channels and a
|
D | img,pistachio-gptimer.txt | 12 - img,cr-periph: Must contain a phandle to the peripheral control
|
/linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
D | img-pwm.txt | 13 - img,cr-periph: Must contain a phandle to the peripheral control
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/ |
D | brcm,nsp.txt | 7 several peripheral interfaces including multiple Gigabit Ethernet PHYs,
|
/linux-4.4.14/Documentation/dmaengine/ |
D | client.txt | 54 for the peripheral. 75 slave_sg - DMA a list of scatter gather buffers from/to a peripheral 76 dma_cyclic - Perform a cyclic DMA operation from/to a peripheral till the 100 The peripheral driver is expected to have mapped the scatterlist for
|
/linux-4.4.14/Documentation/devicetree/bindings/iio/adc/ |
D | rockchip-saradc.txt | 11 the peripheral clock.
|
/linux-4.4.14/sound/spi/ |
D | Kconfig | 21 peripheral found on most AT91 and AVR32 microprocessors.
|
/linux-4.4.14/drivers/usb/chipidea/ |
D | Kconfig | 8 peripheral mode is supported.
|
/linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
D | gpmc-onenand.txt | 12 - reg: The CS line the peripheral is connected to
|
D | atmel-nand.txt | 41 - clocks: phandle to the peripheral clock
|
D | gpmc-nand.txt | 16 - reg: The CS line the peripheral is connected to
|
/linux-4.4.14/drivers/video/fbdev/omap2/dss/ |
D | Kconfig | 56 DBI is a bus between the host processor and a peripheral, 102 processor and a peripheral, such as a display or a framebuffer chip.
|
/linux-4.4.14/drivers/extcon/ |
D | Kconfig | 35 Say Y here to enable support for USB peripheral detection 87 Say Y here to enable support for USB peripheral and USB host
|
/linux-4.4.14/drivers/usb/phy/ |
D | Kconfig | 92 tristate "GPIO based peripheral-only VBUS sensing 'transceiver'" 106 controller is needed to switch between host and peripheral modes. 149 This driver is required even for peripheral only or host only
|
/linux-4.4.14/drivers/staging/most/Documentation/ |
D | driver_usage.txt | 35 one of the peripheral interfaces of a network interface controller (e.g. 50 peripheral interface the hardware supports the driver has a suitable module 53 The HDMs encapsulate the peripheral interface specific knowledge of the driver
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/freescale/ |
D | fsl,vf610-mscm-ir.txt | 5 allows to configure the recipient of each peripheral interrupt. Furthermore
|
/linux-4.4.14/arch/arm64/boot/dts/xilinx/ |
D | zynqmp-ep108.dts | 124 dr_mode = "peripheral";
|
/linux-4.4.14/Documentation/devicetree/bindings/spi/ |
D | spi-rockchip.txt | 18 the peripheral clock.
|
D | spi-davinci.txt | 37 Please check SPI peripheral documentation for a device before using these.
|
D | qcom,spi-qup.txt | 4 and an input FIFO) for serial peripheral interface (SPI) mini-core.
|
/linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
D | gpio-stp-xway.txt | 4 peripheral controller used to drive external shift register cascades. At most
|
D | spear_spics.txt | 19 * st-spics,peripcfg-reg: peripheral configuration register offset
|
D | 8xxx_gpio.txt | 67 Example of a peripheral using the GPIO module as an IRQ controller:
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | imx28-cfa10036.dts | 118 dr_mode = "peripheral";
|
D | dra74x.dtsi | 76 interrupt-names = "peripheral",
|
D | am335x-wega.dtsi | 147 dr_mode = "peripheral";
|
D | imx6qdl-wandboard.dtsi | 248 dr_mode = "peripheral";
|
D | bcm-cygnus-clock.dtsi | 52 /* peripheral clock for system timer */
|
D | s5pv210-smdkv210.dts | 184 dr_mode = "peripheral";
|
D | imx53-m53evk.dts | 354 dr_mode = "peripheral";
|
D | imx6ul-14x14-evk.dts | 117 dr_mode = "peripheral";
|
D | imx53-qsb-common.dtsi | 366 dr_mode = "peripheral";
|
D | imx6sl-warp.dts | 92 dr_mode = "peripheral";
|
D | am57xx-beagle-x15.dts | 713 * Stand alone usage is peripheral only. 720 dr_mode = "peripheral";
|
D | s5pv210-aquila.dts | 358 dr_mode = "peripheral";
|
D | am335x-bone-common.dtsi | 205 dr_mode = "peripheral";
|
D | s5pv210-goni.dts | 336 dr_mode = "peripheral";
|
D | vexpress-v2m-rs1.dtsi | 393 /* IO FPGA peripheral clock */
|
D | exynos4210-trats.dts | 265 dr_mode = "peripheral";
|
D | vexpress-v2m.dtsi | 392 /* IO FPGA peripheral clock */
|
D | sama5d2.dtsi | 469 compatible = "atmel,at91sam9x5-clk-peripheral"; 660 compatible = "atmel,at91sam9x5-clk-peripheral";
|
D | exynos4412-odroid-common.dtsi | 196 dr_mode = "peripheral";
|
D | imx53-tx53.dtsi | 545 dr_mode = "peripheral";
|
D | am335x-sl50.dts | 319 dr_mode = "peripheral";
|
D | exynos4210-universal_c210.dts | 286 dr_mode = "peripheral";
|
D | am4372.dtsi | 922 interrupt-names = "peripheral", 951 interrupt-names = "peripheral",
|
D | dra7.dtsi | 1352 interrupt-names = "peripheral", 1380 interrupt-names = "peripheral", 1410 interrupt-names = "peripheral",
|
D | hisi-x5hd2.dtsi | 477 hisilicon,peripheral-syscon = <&peripheral_ctrl>;
|
D | imx6qdl-tx6.dtsi | 674 dr_mode = "peripheral";
|
D | omap5.dtsi | 880 interrupt-names = "peripheral", 885 dr_mode = "peripheral";
|
D | qcom-apq8064.dtsi | 502 dr_mode = "peripheral";
|
D | imx28-tx28.dts | 700 dr_mode = "peripheral";
|
D | vfxxx.dtsi | 385 dr_mode = "peripheral";
|
D | exynos3250-monk.dts | 171 dr_mode = "peripheral";
|
D | am437x-sk-evm.dts | 574 dr_mode = "peripheral";
|
D | at91sam9261.dtsi | 718 compatible = "atmel,at91rm9200-clk-peripheral";
|
D | exynos3250-rinato.dts | 162 dr_mode = "peripheral";
|
D | am43x-epos-evm.dts | 676 dr_mode = "peripheral";
|
D | ste-nomadik-stn8815.dtsi | 276 * peripheral clocking, clock gates.
|
D | dra72-evm.dts | 588 dr_mode = "peripheral";
|
D | at91rm9200.dtsi | 236 compatible = "atmel,at91rm9200-clk-peripheral";
|
D | dra7-evm.dts | 724 dr_mode = "peripheral";
|
D | at91sam9rl.dtsi | 901 compatible = "atmel,at91rm9200-clk-peripheral";
|
/linux-4.4.14/Documentation/devicetree/bindings/mips/img/ |
D | xilfpga.txt | 72 The BootRAM initializes the cache and the axi_uart peripheral.
|
/linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
D | rockchip-thermal.txt | 13 the peripheral clock.
|
/linux-4.4.14/drivers/irqchip/ |
D | Kconfig | 159 a free irq and configures the IP. Thus the peripheral interrupts are
|
/linux-4.4.14/drivers/nvmem/ |
D | Kconfig | 75 This is a driver for the 'OCOTP' peripheral available on Vybrid
|
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
D | CPUfreq.txt | 8 the ability to change the core, memory and peripheral operating
|
D | Suspend.txt | 9 in Self-Refresh mode, and all but the essential peripheral blocks are
|
D | GPIO.txt | 47 1) If your board is exclusively using an GPIO, say to control peripheral
|
/linux-4.4.14/drivers/dma/ |
D | Kconfig | 98 Enable support for the Analog Devices AXI-DMAC peripheral. This DMA 408 16 to 32 channels for peripheral to memory or memory to memory 443 The DMA controller can transfer data from memory to peripheral, 463 This DMA controller transfers data from memory to peripheral fifo
|
/linux-4.4.14/Documentation/devicetree/bindings/net/ |
D | apm-xgene-enet.txt | 81 /* Board-specific peripheral configurations */
|
D | stmmac.txt | 39 the second clock should be peripheral's register interface clock. Further
|
/linux-4.4.14/arch/arm/mach-davinci/ |
D | Kconfig | 142 prompt "Select DA830/OMAP-L137/AM17x UI board peripheral" 180 bool "No peripheral is enabled"
|
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
D | exynos_dsim.txt | 29 Should contain DSI peripheral nodes (see MIPI DSI bindings [1]).
|
/linux-4.4.14/arch/arm64/boot/dts/qcom/ |
D | msm8916.dtsi | 314 dr_mode = "peripheral"; 336 dr_mode = "peripheral";
|
/linux-4.4.14/Documentation/fb/ |
D | sh7760fb.txt | 37 PFC registers PCCR and PCDR must be set to peripheral mode.
|
/linux-4.4.14/Documentation/devicetree/bindings/crypto/ |
D | fsl-sec6.txt | 75 across the peripheral bus for purposes of processing
|
D | fsl-sec4.txt | 146 across the peripheral bus for purposes of processing
|
/linux-4.4.14/Documentation/arm/Atmel/ |
D | README | 124 When collecting nodes for a particular peripheral or topic, the identifier have to
|
/linux-4.4.14/drivers/usb/musb/ |
D | Kconfig | 14 it's being used with, including the USB peripheral role,
|
/linux-4.4.14/arch/powerpc/boot/dts/fsl/ |
D | mpc8536ds.dtsi | 241 dr_mode = "peripheral";
|
/linux-4.4.14/drivers/usb/host/ |
D | Kconfig | 10 host/peripheral/OTG USB controllers. 367 full-speed devices either in host or peripheral mode. This 662 host side or peripheral side roles. Enable this option if your 692 The R8A66597 is a USB 2.0 host and peripheral controller. 704 The Renesas USBHS is a USB 2.0 host and peripheral controller.
|
/linux-4.4.14/arch/powerpc/boot/dts/ |
D | mgcoge.dts | 219 mode = "peripheral";
|
D | mpc8308_p1m.dts | 164 dr_mode = "peripheral";
|
D | mpc8272ads.dts | 181 mode = "peripheral";
|
D | mpc8308rdb.dts | 139 dr_mode = "peripheral";
|
D | mpc8349emitx.dts | 212 dr_mode = "peripheral";
|
/linux-4.4.14/arch/arm/mach-bcm/ |
D | Kconfig | 48 integrating several peripheral interfaces including multiple Gigabit
|
/linux-4.4.14/Documentation/misc-devices/ |
D | spear-pcie-gadget.txt | 85 memory, which is to be made visible to PCIe host. Similarly any other peripheral
|
/linux-4.4.14/Documentation/arm/pxa/ |
D | mfp.txt | 146 corresponding peripheral, thus set_irq_wake() can be called with 147 the peripheral IRQ to enable the wakeup.
|
/linux-4.4.14/drivers/usb/gadget/legacy/ |
D | Kconfig | 3 # (a) a peripheral controller, and 30 USB peripheral controller driver. Then you can use host-side 333 plus the ability to handle altsettings. Not all peripheral
|
/linux-4.4.14/drivers/staging/most/Documentation/ABI/ |
D | sysfs-class-most.txt | 50 Indicates the type of peripheral interface the current device
|
/linux-4.4.14/arch/mips/include/asm/ |
D | sgiarcs.h | 51 system, processor, cache, adapter, controller, peripheral, memory enumerator
|
/linux-4.4.14/Documentation/devicetree/bindings/c6x/ |
D | dscr.txt | 12 enable (and disable in some cases) SoC pin drivers, select peripheral clock
|
/linux-4.4.14/drivers/misc/ |
D | Kconfig | 193 tristate "Device driver for Atmel SSC peripheral" 197 Serial Communication peripheral (SSC). 199 The SSC peripheral supports a wide variety of serial frame based
|
/linux-4.4.14/Documentation/power/ |
D | states.txt | 74 and put into low-power states. In many cases, all peripheral buses lose power
|
/linux-4.4.14/drivers/uio/ |
D | Kconfig | 111 Generic driver for accessing a peripheral connected to an eLBC port
|
/linux-4.4.14/Documentation/video4linux/ |
D | fimc.txt | 65 to the SoC peripheral camera input at runtime and optionally to control internal
|
/linux-4.4.14/drivers/firmware/ |
D | Kconfig | 17 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
|
/linux-4.4.14/arch/arm64/boot/dts/arm/ |
D | vexpress-v2m-rs1.dtsi | 393 /* IO FPGA peripheral clock */
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
D | mpc5200.txt | 176 cascaded off of peripheral interrupt 0, which the driver interprets as a
|
/linux-4.4.14/drivers/spi/ |
D | Kconfig | 119 Enable support for a SPI bus via the Blackfin SPORT peripheral. 464 for serial peripheral interface (SPI) mini-core. SPI in master
|
/linux-4.4.14/Documentation/s390/ |
D | cds.txt | 111 peripheral attachments like disk devices (aka. DASDs), tapes, communication 132 During its startup the Linux/390 system checks for peripheral devices. Each
|
/linux-4.4.14/drivers/input/serio/ |
D | Kconfig | 103 Say Y here if you want to use the PSIF peripheral on AVR32 devices
|
/linux-4.4.14/Documentation/driver-model/ |
D | platform.txt | 15 host bridges to peripheral buses, and most controllers integrated
|
/linux-4.4.14/Documentation/usb/ |
D | gadget_serial.txt | 123 This will also automatically load the underlying gadget peripheral
|
/linux-4.4.14/arch/arm/mach-imx/ |
D | Kconfig | 27 platforms, it can be attached or removed from the peripheral
|
/linux-4.4.14/arch/arc/ |
D | Kconfig | 502 when there is no real usable peripheral such as EMAC.
|
/linux-4.4.14/Documentation/spi/ |
D | spi-summary | 87 appropriate low-pincount peripheral bus. 295 controller driver. An example would be peripheral-specific DMA tuning
|