| David Brownell | 8ae12a0 | 2006-01-08 13:34:19 -0800 | [diff] [blame] | 1 | # |
| 2 | # SPI driver configuration |
| 3 | # |
| 4 | # NOTE: the reason this doesn't show SPI slave support is mostly that |
| 5 | # nobody's needed a slave side API yet. The master-role API is not |
| 6 | # fully appropriate there, so it'd need some thought to do well. |
| 7 | # |
| 8 | menu "SPI support" |
| 9 | |
| 10 | config SPI |
| 11 | bool "SPI support" |
| 12 | help |
| 13 | The "Serial Peripheral Interface" is a low level synchronous |
| 14 | protocol. Chips that support SPI can have data transfer rates |
| 15 | up to several tens of Mbit/sec. Chips are addressed with a |
| 16 | controller and a chipselect. Most SPI slaves don't support |
| 17 | dynamic device discovery; some are even write-only or read-only. |
| 18 | |
| 19 | SPI is widely used by microcontollers to talk with sensors, |
| 20 | eeprom and flash memory, codecs and various other controller |
| 21 | chips, analog to digital (and d-to-a) converters, and more. |
| 22 | MMC and SD cards can be accessed using SPI protocol; and for |
| 23 | DataFlash cards used in MMC sockets, SPI must always be used. |
| 24 | |
| 25 | SPI is one of a family of similar protocols using a four wire |
| 26 | interface (select, clock, data in, data out) including Microwire |
| 27 | (half duplex), SSP, SSI, and PSP. This driver framework should |
| 28 | work with most such devices and controllers. |
| 29 | |
| 30 | config SPI_DEBUG |
| 31 | boolean "Debug support for SPI drivers" |
| 32 | depends on SPI && DEBUG_KERNEL |
| 33 | help |
| 34 | Say "yes" to enable debug messaging (like dev_dbg and pr_debug), |
| 35 | sysfs, and debugfs support in SPI controller and protocol drivers. |
| 36 | |
| 37 | # |
| 38 | # MASTER side ... talking to discrete SPI slave chips including microcontrollers |
| 39 | # |
| 40 | |
| 41 | config SPI_MASTER |
| 42 | # boolean "SPI Master Support" |
| 43 | boolean |
| 44 | default SPI |
| 45 | help |
| 46 | If your system has an master-capable SPI controller (which |
| 47 | provides the clock and chipselect), you can enable that |
| 48 | controller and the protocol drivers for the SPI slave chips |
| 49 | that are connected. |
| 50 | |
| 51 | comment "SPI Master Controller Drivers" |
| 52 | depends on SPI_MASTER |
| 53 | |
| David Brownell | 9904f22 | 2006-01-08 13:34:26 -0800 | [diff] [blame^] | 54 | config SPI_BITBANG |
| 55 | tristate "Bitbanging SPI master" |
| 56 | depends on SPI_MASTER && EXPERIMENTAL |
| 57 | help |
| 58 | With a few GPIO pins, your system can bitbang the SPI protocol. |
| 59 | Select this to get SPI support through I/O pins (GPIO, parallel |
| 60 | port, etc). Or, some systems' SPI master controller drivers use |
| 61 | this code to manage the per-word or per-transfer accesses to the |
| 62 | hardware shift registers. |
| 63 | |
| 64 | This is library code, and is automatically selected by drivers that |
| 65 | need it. You only need to select this explicitly to support driver |
| 66 | modules that aren't part of this kernel tree. |
| David Brownell | 8ae12a0 | 2006-01-08 13:34:19 -0800 | [diff] [blame] | 67 | |
| 68 | # |
| 69 | # Add new SPI master controllers in alphabetical order above this line |
| 70 | # |
| 71 | |
| 72 | |
| 73 | # |
| 74 | # There are lots of SPI device types, with sensors and memory |
| 75 | # being probably the most widely used ones. |
| 76 | # |
| 77 | comment "SPI Protocol Masters" |
| 78 | depends on SPI_MASTER |
| 79 | |
| 80 | |
| 81 | # |
| 82 | # Add new SPI protocol masters in alphabetical order above this line |
| 83 | # |
| 84 | |
| 85 | |
| 86 | # (slave support would go here) |
| 87 | |
| 88 | endmenu # "SPI support" |
| 89 | |