Searched +full:gpio +full:- +full:mosi (Results 1 – 15 of 15) sorted by relevance
| /Documentation/devicetree/bindings/spi/ |
| D | spi-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/spi/spi-gpio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: SPI-GPIO devicetree bindings 10 - Rob Herring <robh@kernel.org> 13 This represents a group of 3-n GPIO lines used for bit-banged SPI on 14 dedicated GPIO lines. 17 - $ref: "/schemas/spi/spi-controller.yaml#" 21 const: spi-gpio [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,kirkwood-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,88f6180-pinctrl", 8 "marvell,88f6190-pinctrl", "marvell,88f6192-pinctrl", 9 "marvell,88f6281-pinctrl", "marvell,88f6282-pinctrl", 10 "marvell,98dx4122-pinctrl", "marvell,98dx1135-pinctrl" 11 - reg: register specifier of MPP registers 14 It also support the 88f6281-based variant in the 98dx412x Bobcat SoCs. 24 mpp0 0 gpio, nand(io2), spi(cs) 25 mpp1 1 gpo, nand(io3), spi(mosi) 28 mpp4 4 gpio, nand(io6), uart0(rxd), ptp(clk) [all …]
|
| D | marvell,armada-370-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,88f6710-pinctrl" 8 - reg: register specifier of MPP registers 16 mpp0 0 gpio, uart0(rxd) 18 mpp2 2 gpio, i2c0(sck), uart0(txd) 19 mpp3 3 gpio, i2c0(sda), uart0(rxd) 20 mpp4 4 gpio, vdd(cpu-pd) 22 mpp6 6 gpio, ge0(txd0), sata0(prsnt), tdm(rst), audio(sdo) 24 mpp8 8 gpio, ge0(txd2), uart0(rts), tdm(drx), audio(bclk) 26 mpp10 10 gpio, ge0(txctl), uart0(cts), tdm(fsync), audio(sdi) [all …]
|
| D | marvell,armada-375-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,88f6720-pinctrl" 8 - reg: register specifier of MPP registers 16 mpp0 0 gpio, dev(ad2), spi0(cs1), spi1(cs1) 17 mpp1 1 gpio, dev(ad3), spi0(mosi), spi1(mosi) 18 mpp2 2 gpio, dev(ad4), ptp(evreq), led(c0), audio(sdi) 19 mpp3 3 gpio, dev(ad5), ptp(trig), led(p3), audio(mclk) 20 mpp4 4 gpio, dev(ad6), spi0(miso), spi1(miso) 21 mpp5 5 gpio, dev(ad7), spi0(cs2), spi1(cs2) 22 mpp6 6 gpio, dev(ad0), led(p1), audio(lrclk) [all …]
|
| D | marvell,dove-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,dove-pinctrl" 8 - clocks: (optional) phandle of pdma clock 9 - reg: register specifiers of MPP, MPP4, and PMU MPP registers 18 mpp0 0 gpio, pmu, uart2(rts), sdio0(cd), lcd0(pwm), pmu* 19 mpp1 1 gpio, pmu, uart2(cts), sdio0(wp), lcd1(pwm), pmu* 20 mpp2 2 gpio, pmu, uart2(txd), sdio0(buspwr), sata(prsnt), 22 mpp3 3 gpio, pmu, uart2(rxd), sdio0(ledctrl), sata(act), 23 uart1(cts), lcd-spi(cs1), pmu* 24 mpp4 4 gpio, pmu, uart3(rts), sdio1(cd), spi1(miso), pmu* [all …]
|
| D | marvell,armada-39x-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,88f6920-pinctrl", "marvell,88f6925-pinctrl" or 8 "marvell,88f6928-pinctrl" depending on the specific variant of the 10 - reg: register specifier of MPP registers 18 mpp0 0 gpio, ua0(rxd) 19 mpp1 1 gpio, ua0(txd) 20 mpp2 2 gpio, i2c0(sck) 21 mpp3 3 gpio, i2c0(sda) 22 mpp4 4 gpio, ua1(txd), ua0(rts), smi(mdc) 23 mpp5 5 gpio, ua1(rxd), ua0(cts), smi(mdio) [all …]
|
| D | marvell,armada-38x-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,88f6810-pinctrl", "marvell,88f6820-pinctrl" or 8 "marvell,88f6828-pinctrl" depending on the specific variant of the 10 - reg: register specifier of MPP registers 18 mpp0 0 gpio, ua0(rxd) 19 mpp1 1 gpio, ua0(txd) 20 mpp2 2 gpio, i2c0(sck) 21 mpp3 3 gpio, i2c0(sda) 22 mpp4 4 gpio, ge(mdc), ua1(txd), ua0(rts) 23 mpp5 5 gpio, ge(mdio), ua1(rxd), ua0(cts) [all …]
|
| D | marvell,armada-xp-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,mv78230-pinctrl", "marvell,mv78260-pinctrl", 8 "marvell,mv78460-pinctrl" 9 - reg: register specifier of MPP registers 21 mpp0 0 gpio, ge0(txclkout), lcd(d0) 22 mpp1 1 gpio, ge0(txd0), lcd(d1) 23 mpp2 2 gpio, ge0(txd1), lcd(d2) 24 mpp3 3 gpio, ge0(txd2), lcd(d3) 25 mpp4 4 gpio, ge0(txd3), lcd(d4) 26 mpp5 5 gpio, ge0(txctl), lcd(d5) [all …]
|
| D | marvell,armada-98dx3236-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,98dx3236-pinctrl" or "marvell,98dx4251-pinctrl" 8 - reg: register specifier of MPP registers 14 mpp0 0 gpo, spi0(mosi), dev(ad8) 15 mpp1 1 gpio, spi0(miso), dev(ad9) 17 mpp3 3 gpio, spi0(cs0), dev(ad11) 18 mpp4 4 gpio, spi0(cs1), smi(mdc), dev(cs0) 19 mpp5 5 gpio, pex(rsto), sd0(cmd), dev(bootcs) 21 mpp7 7 gpio, sd0(d0), dev(ale0) 22 mpp8 8 gpio, sd0(d1), dev(ale1) [all …]
|
| /Documentation/devicetree/bindings/arm/marvell/ |
| D | cp110-system-controller.txt | 6 giving access to numerous features: clocks, pin-muxing and many other 11 - compatible: must be: "syscon", "simple-mfd"; 12 - reg: register area of the CP110 system controller 18 ------- 23 - a set of core clocks 24 - a set of gatable clocks 28 - The first cell must be 0 or 1. 0 for the core clocks and 1 for the 30 - The second cell identifies the particular core clock or gatable 34 - Core clocks 35 - 0 0 APLL [all …]
|
| D | ap806-system-controller.txt | 6 giving access to numerous features: clocks, pin-muxing and many other 11 - compatible: must be: "syscon", "simple-mfd"; 12 - reg: register area of the AP806 system controller 18 ------- 24 - 0: reference clock of CPU cluster 0 25 - 1: reference clock of CPU cluster 1 26 - 2: fixed PLL at 1200 Mhz 27 - 3: MSS clock, derived from the fixed PLL 31 - compatible: must be one of: 32 * "marvell,ap806-clock" [all …]
|
| /Documentation/driver-api/ |
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data 9 duplex protocol; for each bit shifted out the MOSI line (one per clock) 12 additional chipselect line is usually active-low (nCS); four signals are 24 hardware, which may be as simple as a set of GPIO pins or as complex as 33 board-specific initialization code. A :c:type:`struct spi_driver 46 .. kernel-doc:: include/linux/spi/spi.h 49 .. kernel-doc:: drivers/spi/spi.c 52 .. kernel-doc:: drivers/spi/spi.c
|
| /Documentation/devicetree/bindings/leds/irled/ |
| D | spi-ir-led.txt | 4 The IR LED switch is connected to the MOSI line of the SPI device and the data 8 - compatible: should be "ir-spi-led". 11 - duty-cycle: 8 bit balue that represents the percentage of one period 13 - led-active-low: boolean value that specifies whether the output is 15 - power-supply: specifies the power source. It can either be a regulator 16 or a gpio which enables a regulator, i.e. a regulator-fixed as 18 Documentation/devicetree/bindings/regulator/fixed-regulator.yaml 23 compatible = "ir-spi-led"; 25 spi-max-frequency = <5000000>; 26 power-supply = <&vdd_led>; [all …]
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 2 Subsystem drivers using GPIO 5 Note that standard kernel drivers exist for common GPIO tasks and will provide 6 the right in-kernel and userspace APIs/ABIs for the job, and that these 10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO 13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger, 14 i.e. a LED will turn on/off in response to a GPIO line going high or low 15 (and that LED may in turn use the leds-gpio as per above). 17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line 20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your 21 GPIO line cannot generate interrupts, so it needs to be periodically polled [all …]
|
| /Documentation/spi/ |
| D | spi-summary.rst | 5 02-Feb-2012 8 ------------ 15 and parallel data lines with "Master Out, Slave In" (MOSI) or "Master In, 17 clocking modes through which data is exchanged; mode-0 and mode-3 are most 32 - SPI may be used for request/response style device protocols, as with 35 - It may also be used to stream data in either direction (half duplex), 38 - Some devices may use eight bit words. Others may use different word 39 lengths, such as streams of 12-bit or 20-bit digital samples. 41 - Words are usually sent with their most significant bit (MSB) first, 44 - Sometimes SPI is used to daisy-chain devices, like shift registers. [all …]
|