| /linux-2.6.39/drivers/spi/ |
| D | Kconfig | 2 # SPI driver configuration
4 # NOTE: the reason this doesn't show SPI slave support is mostly that
8 menuconfig SPI config
9 bool "SPI support"
13 protocol. Chips that support SPI can have data transfer rates
15 controller and a chipselect. Most SPI slaves don't support
18 SPI is widely used by microcontrollers to talk with sensors,
21 MMC and SD cards can be accessed using SPI protocol; and for
22 DataFlash cards used in MMC sockets, SPI must always be used.
24 SPI is one of a family of similar protocols using a four wire
[all …]
|
| /linux-2.6.39/Documentation/devicetree/bindings/spi/ |
| D | spi-bus.txt | 1 SPI (Serial Peripheral Interface) busses
3 SPI busses can be described with a node for the SPI master device
4 and a set of child nodes for each SPI slave on the bus. For this
5 discussion, it is assumed that the system's SPI controller is in
6 SPI master mode. This binding does not describe SPI controllers
9 The SPI master node requires the following properties:
11 address on the SPI bus.
13 - compatible - name of SPI bus controller following generic names
15 No other properties are required in the SPI bus node. It is assumed
16 that a driver for an SPI bus device will understand that it is an SPI bus.
[all …]
|
| D | fsl-spi.txt | 1 * SPI (Serial Peripheral Interface)
4 - cell-index : QE SPI subblock index.
8 - mode : the SPI operation mode, it can be "cpu" or "cpu-qe".
20 The gpios will be referred to as reg = <index> in the SPI child nodes.
21 If unspecified, a single SPI device without a chip select can be used.
|
| /linux-2.6.39/Documentation/networking/caif/ |
| D | spi_porting.txt | 1 - CAIF SPI porting -
3 - CAIF SPI basics:
5 Running CAIF over SPI needs some extra setup, owing to the nature of SPI.
8 CAIF over SPI is a SPI slave chip and two GPIOs (more details below).
12 - CAIF SPI framework:
14 To make porting as easy as possible, the CAIF SPI has been divided in
16 generic functionality such as length framing, SPI frame negotiation
17 and SPI frame delivery and transmission. The other part is the CAIF
18 SPI slave device part, which is the module that you have to write if
19 you want to run SPI CAIF on a new hardware. This part takes care of
[all …]
|
| /linux-2.6.39/drivers/staging/iio/gyro/ |
| D | Kconfig | 7 tristate "Analog Devices ADIS16060 Yaw Rate Gyroscope with SPI driver"
8 depends on SPI
11 yaw rate gyroscope with SPI.
14 tristate "Analog Devices ADIS16080/100 Yaw Rate Gyroscope with SPI driver"
15 depends on SPI
18 Gyroscope with SPI.
22 depends on SPI
28 tristate "Analog Devices ADIS16260 Digital Gyroscope Sensor SPI driver"
29 depends on SPI
|
| /linux-2.6.39/Documentation/blackfin/ |
| D | bfin-spi-notes.txt | 1 SPI Chip Select behavior:
3 With the Blackfin on-chip SPI peripheral, there is some logic tied to the CPHA
5 controlled by software (CPHA=1). However, the Linux SPI bus driver assumes that
7 the entire SPI transfer. - And not just bits_per_word duration.
9 In most cases you can utilize SPI MODE_3 instead of MODE_0 to work-around this
10 behavior. If your SPI slave device in question requires SPI MODE_0 or MODE_2
11 timing, you can utilize the GPIO controlled SPI Slave Select option instead.
|
| /linux-2.6.39/Documentation/spi/ |
| D | spi-summary | 1 Overview of Linux kernel SPI support
6 What is SPI?
8 The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial
11 standardization body. SPI uses a master/slave configuration.
21 SPI masters use a fourth "chip select" line to activate a given SPI slave
23 in parallel. All SPI slaves support chipselects; they are usually active
28 SPI slave functions are usually not interoperable between vendors
29 (except for commodities like SPI memory chips).
31 - SPI may be used for request/response style device protocols, as with
43 - Sometimes SPI is used to daisy-chain devices, like shift registers.
[all …]
|
| D | spidev | 1 SPI devices have a limited userspace API, supporting basic half-duplex
2 read() and write() access to SPI slave devices. Using ioctl() requests,
17 as SPI slaves, which you may need to change quite often.
29 Set up the other device characteristics (bits per word, SPI clocking,
36 When you do that, the sysfs node for the SPI device will include a child
39 busybox; it's less featureful, but often enough.) For a SPI device with
46 /sys/devices/.../spiB.C ... as usual, the SPI device node will
47 be a child of its SPI master controller.
61 by having kernel code remove the SPI device, probably by removing the driver
62 for its SPI controller (so its spi_master vanishes).
[all …]
|
| D | spi-lm70llp | 1 spi_lm70llp : LM70-LLP parport-to-SPI adapter
14 temperature sensor evaluation board to the kernel's SPI core subsystem.
16 This is a SPI master controller driver. It can be used in conjunction with
17 (layered under) the LM70 logical driver (a "SPI protocol driver").
19 into a SPI bus with a single device, which will be driven by the generic
47 Note that since the LM70 uses a "3-wire" variant of SPI, the SI/SO pin
50 pin low. This can't be shared with true SPI devices, but other 3-wire
55 spi_write_then_read() call. It performs Mode 0 (SPI/Microwire) bitbanging.
77 o David Brownell for mentoring the SPI-side driver development.
|
| D | butterfly | 19 SPI protocol drivers interact with the AVR, and could even let the AVR
21 easily with a "real SPI controller", instead of this bitbanger.
24 The first cable connections will hook Linux up to one SPI bus, with the
40 (a) flash new firmware that disables SPI (set PRR.2, and disable pullups
50 Or you could flash firmware making the AVR into an SPI slave (keeping the
52 the driver for your custom SPI-based protocol.
54 The "USI" controller, using J405, can also be used for a second SPI bus.
55 That would let you talk to the AVR using custom SPI-with-USI firmware,
|
| D | ep93xx_spi | 1 Cirrus EP93xx SPI controller driver HOWTO
4 ep93xx_spi driver brings SPI master support for EP93xx SPI controller. Chip
15 arch/arm/mach-ep93xx/*.c). In this example we configure MMC over SPI through
|
| /linux-2.6.39/drivers/staging/iio/accel/ |
| D | Kconfig | 8 depends on SPI
17 depends on SPI
26 depends on SPI
35 depends on SPI
44 depends on SPI
51 depends on SPI
60 depends on SPI
63 Currently this only supports the device via an SPI interface.
67 depends on SPI
71 Say yes here to build SPI support for the ST microelectronics
[all …]
|
| /linux-2.6.39/drivers/staging/iio/imu/ |
| D | Kconfig | 7 tristate "Analog Devices ADIS16300 IMU SPI driver"
8 depends on SPI
16 tristate "Analog Devices ADIS16350/54/55/60/62/64/65 IMU SPI driver"
17 depends on SPI
25 tristate "Analog Devices ADIS16400/5 IMU SPI driver"
26 depends on SPI
|
| /linux-2.6.39/drivers/staging/iio/meter/ |
| D | Kconfig | 8 depends on SPI
15 depends on SPI
22 depends on SPI
31 depends on SPI
38 depends on SPI || I2C
54 tristate "support SPI bus connection"
55 depends on ADE7854 && SPI
58 Say Y here if you have ADE7854/58/68/78 hooked to a SPI bus.
|
| /linux-2.6.39/drivers/staging/iio/dds/ |
| D | Kconfig | 8 depends on SPI
15 depends on SPI
25 depends on SPI
35 depends on SPI
42 depends on SPI
49 depends on SPI
56 depends on SPI
|
| /linux-2.6.39/Documentation/hwmon/ |
| D | lm70 | 21 SPI/Microwire Bus interface.
24 the driver accesses the LM70 using SPI communication: 16 SCLK cycles
28 SPI support.
30 As a real (in-tree) example of this "SPI protocol driver" interfacing
31 with a "SPI master controller driver", see drivers/spi/spi_lm70llp.c
34 The TMP121/TMP123 are very similar; main differences are 4 wire SPI inter-
|
| /linux-2.6.39/drivers/net/caif/ |
| D | Kconfig | 17 tristate "CAIF SPI transport driver for slave interface"
21 The CAIF Link layer SPI Protocol driver for Slave SPI interface.
23 platform specific SPI device. A sample CAIF SPI Platform device is
|
| /linux-2.6.39/sound/spi/ |
| D | Kconfig | 1 #SPI drivers
4 bool "SPI sound devices"
5 depends on SPI
8 Support for sound devices connected via the SPI bus.
|
| /linux-2.6.39/drivers/staging/iio/dac/ |
| D | Kconfig | 8 depends on SPI
11 AD5664R convertors (DAC). This driver uses the common SPI interface.
14 tristate "Analog Devices AD5444/6, AD5620/40/60 and AD5542A/12A DAC SPI driver"
15 depends on SPI
|
| /linux-2.6.39/drivers/staging/iio/adc/ |
| D | Kconfig | 53 depends on SPI
63 depends on SPI
91 depends on SPI
118 depends on SPI
125 SPI analog to digital convertors (ADC).
133 depends on SPI
139 AD7887 SPI analog to digital convertor (ADC).
157 depends on SPI
171 depends on SPI
|
| /linux-2.6.39/drivers/staging/iio/addac/ |
| D | Kconfig | 13 tristate "support SPI bus connection"
14 depends on SPI && ADT7316
17 Say yes here to build SPI bus support for Analog Devices ADT7316/7/8
|
| /linux-2.6.39/drivers/net/wireless/libertas/ |
| D | Kconfig | 30 tristate "Marvell Libertas 8686 SPI 802.11b/g cards"
31 depends on LIBERTAS && SPI
33 A driver for Marvell Libertas 8686 SPI devices.
|
| /linux-2.6.39/arch/cris/arch-v32/drivers/ |
| D | Kconfig | 662 select SPI
673 # independent of MMC_SPI, so we'll keep SPI non-dependent on the
675 # for the board-info file until a separate non-MMC SPI board file
678 # configure non-MMC SPI ports together with MMC_SPI ports (if multiple
679 # SPI ports are enabled).
687 SPI master controller on Axis ETRAX FS and later. The
695 This enables using GPIO pins port as a SPI master controller
700 tristate "SPI using synchronous serial port 0 (sser0)"
708 or for devices using the SPI protocol on that port. Say m if you
713 bool "DMA for SPI on sser0 enabled"
[all …]
|
| /linux-2.6.39/drivers/net/wireless/wl1251/ |
| D | Kconfig | 14 tristate "TI wl1251 SPI support"
17 This module adds support for the SPI interface of adapters using
19 the SPI bus.
|
| /linux-2.6.39/arch/arm/mach-u300/ |
| D | Kconfig | 85 bool "SSP/SPI dummy chip"
86 select SPI
91 SPI device to be used for loopback tests. Regularly used
92 to test reference designs. If you're not testing SPI,
94 SPI framework and ARM PL022 support.
|