2 * Copyright (C) 2005 David Brownell
4 * This program is free software; you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation; either version 2 of the License, or
7 * (at your option) any later version.
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
14 * You should have received a copy of the GNU General Public License
15 * along with this program; if not, write to the Free Software
16 * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
22 #include <linux/device.h>
23 #include <linux/mod_devicetable.h>
24 #include <linux/slab.h>
27 * INTERFACES between SPI master-side drivers and SPI infrastructure.
28 * (There's no SPI slave support for Linux yet...)
30 extern struct bus_type spi_bus_type;
33 * struct spi_device - Master side proxy for an SPI slave device
34 * @dev: Driver model representation of the device.
35 * @master: SPI controller used with the device.
36 * @max_speed_hz: Maximum clock rate to be used with this chip
37 * (on this board); may be changed by the device's driver.
38 * The spi_transfer.speed_hz can override this for each transfer.
39 * @chip_select: Chipselect, distinguishing chips handled by @master.
40 * @mode: The spi mode defines how data is clocked out and in.
41 * This may be changed by the device's driver.
42 * The "active low" default for chipselect mode can be overridden
43 * (by specifying SPI_CS_HIGH) as can the "MSB first" default for
44 * each word in a transfer (by specifying SPI_LSB_FIRST).
45 * @bits_per_word: Data transfers involve one or more words; word sizes
46 * like eight or 12 bits are common. In-memory wordsizes are
47 * powers of two bytes (e.g. 20 bit samples use 32 bits).
48 * This may be changed by the device's driver, or left at the
49 * default (0) indicating protocol words are eight bit bytes.
50 * The spi_transfer.bits_per_word can override this for each transfer.
51 * @irq: Negative, or the number passed to request_irq() to receive
52 * interrupts from this device.
53 * @controller_state: Controller's runtime state
54 * @controller_data: Board-specific definitions for controller, such as
55 * FIFO initialization parameters; from board_info.controller_data
56 * @modalias: Name of the driver to use with this device, or an alias
57 * for that name. This appears in the sysfs "modalias" attribute
58 * for driver coldplugging, and in uevents used for hotplugging
60 * A @spi_device is used to interchange data between an SPI slave
61 * (usually a discrete chip) and CPU memory.
63 * In @dev, the platform_data is used to hold information about this
64 * device that's meaningful to the device's protocol driver, but not
65 * to its controller. One example might be an identifier for a chip
66 * variant with slightly different functionality; another might be
67 * information about how this particular board wires the chip's pins.
71 struct spi_master *master;
75 #define SPI_CPHA 0x01 /* clock phase */
76 #define SPI_CPOL 0x02 /* clock polarity */
77 #define SPI_MODE_0 (0|0) /* (original MicroWire) */
78 #define SPI_MODE_1 (0|SPI_CPHA)
79 #define SPI_MODE_2 (SPI_CPOL|0)
80 #define SPI_MODE_3 (SPI_CPOL|SPI_CPHA)
81 #define SPI_CS_HIGH 0x04 /* chipselect active high? */
82 #define SPI_LSB_FIRST 0x08 /* per-word bits-on-wire */
83 #define SPI_3WIRE 0x10 /* SI/SO signals shared */
84 #define SPI_LOOP 0x20 /* loopback mode */
85 #define SPI_NO_CS 0x40 /* 1 dev/bus, no chipselect */
86 #define SPI_READY 0x80 /* slave pulls low to pause */
89 void *controller_state;
90 void *controller_data;
91 char modalias[SPI_NAME_SIZE];
94 * likely need more hooks for more protocol options affecting how
95 * the controller talks to each chip, like:
96 * - memory packing (12 bit samples into low bits, others zeroed)
98 * - drop chipselect after each word
104 static inline struct spi_device *to_spi_device(struct device *dev)
106 return dev ? container_of(dev, struct spi_device, dev) : NULL;
109 /* most drivers won't need to care about device refcounting */
110 static inline struct spi_device *spi_dev_get(struct spi_device *spi)
112 return (spi && get_device(&spi->dev)) ? spi : NULL;
115 static inline void spi_dev_put(struct spi_device *spi)
118 put_device(&spi->dev);
121 /* ctldata is for the bus_master driver's runtime state */
122 static inline void *spi_get_ctldata(struct spi_device *spi)
124 return spi->controller_state;
127 static inline void spi_set_ctldata(struct spi_device *spi, void *state)
129 spi->controller_state = state;
132 /* device driver data */
134 static inline void spi_set_drvdata(struct spi_device *spi, void *data)
136 dev_set_drvdata(&spi->dev, data);
139 static inline void *spi_get_drvdata(struct spi_device *spi)
141 return dev_get_drvdata(&spi->dev);
149 * struct spi_driver - Host side "protocol" driver
150 * @id_table: List of SPI devices supported by this driver
151 * @probe: Binds this driver to the spi device. Drivers can verify
152 * that the device is actually present, and may need to configure
153 * characteristics (such as bits_per_word) which weren't needed for
154 * the initial configuration done during system setup.
155 * @remove: Unbinds this driver from the spi device
156 * @shutdown: Standard shutdown callback used during system state
157 * transitions such as powerdown/halt and kexec
158 * @suspend: Standard suspend callback used during system state transitions
159 * @resume: Standard resume callback used during system state transitions
160 * @driver: SPI device drivers should initialize the name and owner
161 * field of this structure.
163 * This represents the kind of device driver that uses SPI messages to
164 * interact with the hardware at the other end of a SPI link. It's called
165 * a "protocol" driver because it works through messages rather than talking
166 * directly to SPI hardware (which is what the underlying SPI controller
167 * driver does to pass those messages). These protocols are defined in the
168 * specification for the device(s) supported by the driver.
170 * As a rule, those device protocols represent the lowest level interface
171 * supported by a driver, and it will support upper level interfaces too.
172 * Examples of such upper levels include frameworks like MTD, networking,
173 * MMC, RTC, filesystem character device nodes, and hardware monitoring.
176 const struct spi_device_id *id_table;
177 int (*probe)(struct spi_device *spi);
178 int (*remove)(struct spi_device *spi);
179 void (*shutdown)(struct spi_device *spi);
180 int (*suspend)(struct spi_device *spi, pm_message_t mesg);
181 int (*resume)(struct spi_device *spi);
182 struct device_driver driver;
185 static inline struct spi_driver *to_spi_driver(struct device_driver *drv)
187 return drv ? container_of(drv, struct spi_driver, driver) : NULL;
190 extern int spi_register_driver(struct spi_driver *sdrv);
193 * spi_unregister_driver - reverse effect of spi_register_driver
194 * @sdrv: the driver to unregister
197 static inline void spi_unregister_driver(struct spi_driver *sdrv)
200 driver_unregister(&sdrv->driver);
205 * struct spi_master - interface to SPI master controller
206 * @dev: device interface to this driver
207 * @bus_num: board-specific (and often SOC-specific) identifier for a
208 * given SPI controller.
209 * @num_chipselect: chipselects are used to distinguish individual
210 * SPI slaves, and are numbered from zero to num_chipselects.
211 * each slave has a chipselect signal, but it's common that not
212 * every chipselect is connected to a slave.
213 * @dma_alignment: SPI controller constraint on DMA buffers alignment.
214 * @mode_bits: flags understood by this controller driver
215 * @flags: other constraints relevant to this driver
216 * @setup: updates the device mode and clocking records used by a
217 * device's SPI controller; protocol code may call this. This
218 * must fail if an unrecognized or unsupported mode is requested.
219 * It's always safe to call this unless transfers are pending on
220 * the device whose settings are being modified.
221 * @transfer: adds a message to the controller's transfer queue.
222 * @cleanup: frees controller-specific state
224 * Each SPI master controller can communicate with one or more @spi_device
225 * children. These make a small bus, sharing MOSI, MISO and SCK signals
226 * but not chip select signals. Each device may be configured to use a
227 * different clock rate, since those shared signals are ignored unless
228 * the chip is selected.
230 * The driver for an SPI controller manages access to those devices through
231 * a queue of spi_message transactions, copying data between CPU memory and
232 * an SPI slave device. For each such message it queues, it calls the
233 * message's completion function when the transaction completes.
238 /* other than negative (== assign one dynamically), bus_num is fully
239 * board-specific. usually that simplifies to being SOC-specific.
240 * example: one SOC has three SPI controllers, numbered 0..2,
241 * and one board's schematics might show it using SPI-2. software
242 * would normally use bus_num=2 for that controller.
246 /* chipselects will be integral to many controllers; some others
247 * might use board-specific GPIOs.
251 /* some SPI controllers pose alignment requirements on DMAable
252 * buffers; let protocol drivers know about these requirements.
256 /* spi_device.mode flags understood by this controller driver */
259 /* other constraints relevant to this driver */
261 #define SPI_MASTER_HALF_DUPLEX BIT(0) /* can't do full duplex */
262 #define SPI_MASTER_NO_RX BIT(1) /* can't do buffer read */
263 #define SPI_MASTER_NO_TX BIT(2) /* can't do buffer write */
265 /* lock and mutex for SPI bus locking */
266 spinlock_t bus_lock_spinlock;
267 struct mutex bus_lock_mutex;
269 /* flag indicating that the SPI bus is locked for exclusive use */
272 /* Setup mode and clock, etc (spi driver may call many times).
274 * IMPORTANT: this may be called when transfers to another
275 * device are active. DO NOT UPDATE SHARED REGISTERS in ways
276 * which could break those transfers.
278 int (*setup)(struct spi_device *spi);
280 /* bidirectional bulk transfers
282 * + The transfer() method may not sleep; its main role is
283 * just to add the message to the queue.
284 * + For now there's no remove-from-queue operation, or
285 * any other request management
286 * + To a given spi_device, message queueing is pure fifo
288 * + The master's main job is to process its message queue,
289 * selecting a chip then transferring data
290 * + If there are multiple spi_device children, the i/o queue
291 * arbitration algorithm is unspecified (round robin, fifo,
292 * priority, reservations, preemption, etc)
294 * + Chipselect stays active during the entire message
295 * (unless modified by spi_transfer.cs_change != 0).
296 * + The message transfers use clock and SPI mode parameters
297 * previously established by setup() for this device
299 int (*transfer)(struct spi_device *spi,
300 struct spi_message *mesg);
302 /* called on release() to free memory provided by spi_master */
303 void (*cleanup)(struct spi_device *spi);
306 static inline void *spi_master_get_devdata(struct spi_master *master)
308 return dev_get_drvdata(&master->dev);
311 static inline void spi_master_set_devdata(struct spi_master *master, void *data)
313 dev_set_drvdata(&master->dev, data);
316 static inline struct spi_master *spi_master_get(struct spi_master *master)
318 if (!master || !get_device(&master->dev))
323 static inline void spi_master_put(struct spi_master *master)
326 put_device(&master->dev);
330 /* the spi driver core manages memory for the spi_master classdev */
331 extern struct spi_master *
332 spi_alloc_master(struct device *host, unsigned size);
334 extern int spi_register_master(struct spi_master *master);
335 extern void spi_unregister_master(struct spi_master *master);
337 extern struct spi_master *spi_busnum_to_master(u16 busnum);
339 /*---------------------------------------------------------------------------*/
342 * I/O INTERFACE between SPI controller and protocol drivers
344 * Protocol drivers use a queue of spi_messages, each transferring data
345 * between the controller and memory buffers.
347 * The spi_messages themselves consist of a series of read+write transfer
348 * segments. Those segments always read the same number of bits as they
349 * write; but one or the other is easily ignored by passing a null buffer
350 * pointer. (This is unlike most types of I/O API, because SPI hardware
353 * NOTE: Allocation of spi_transfer and spi_message memory is entirely
354 * up to the protocol driver, which guarantees the integrity of both (as
355 * well as the data buffers) for as long as the message is queued.
359 * struct spi_transfer - a read/write buffer pair
360 * @tx_buf: data to be written (dma-safe memory), or NULL
361 * @rx_buf: data to be read (dma-safe memory), or NULL
362 * @tx_dma: DMA address of tx_buf, if @spi_message.is_dma_mapped
363 * @rx_dma: DMA address of rx_buf, if @spi_message.is_dma_mapped
364 * @len: size of rx and tx buffers (in bytes)
365 * @speed_hz: Select a speed other than the device default for this
366 * transfer. If 0 the default (from @spi_device) is used.
367 * @bits_per_word: select a bits_per_word other than the device default
368 * for this transfer. If 0 the default (from @spi_device) is used.
369 * @cs_change: affects chipselect after this transfer completes
370 * @delay_usecs: microseconds to delay after this transfer before
371 * (optionally) changing the chipselect status, then starting
372 * the next transfer or completing this @spi_message.
373 * @transfer_list: transfers are sequenced through @spi_message.transfers
375 * SPI transfers always write the same number of bytes as they read.
376 * Protocol drivers should always provide @rx_buf and/or @tx_buf.
377 * In some cases, they may also want to provide DMA addresses for
378 * the data being transferred; that may reduce overhead, when the
379 * underlying driver uses dma.
381 * If the transmit buffer is null, zeroes will be shifted out
382 * while filling @rx_buf. If the receive buffer is null, the data
383 * shifted in will be discarded. Only "len" bytes shift out (or in).
384 * It's an error to try to shift out a partial word. (For example, by
385 * shifting out three bytes with word size of sixteen or twenty bits;
386 * the former uses two bytes per word, the latter uses four bytes.)
388 * In-memory data values are always in native CPU byte order, translated
389 * from the wire byte order (big-endian except with SPI_LSB_FIRST). So
390 * for example when bits_per_word is sixteen, buffers are 2N bytes long
391 * (@len = 2N) and hold N sixteen bit words in CPU byte order.
393 * When the word size of the SPI transfer is not a power-of-two multiple
394 * of eight bits, those in-memory words include extra bits. In-memory
395 * words are always seen by protocol drivers as right-justified, so the
396 * undefined (rx) or unused (tx) bits are always the most significant bits.
398 * All SPI transfers start with the relevant chipselect active. Normally
399 * it stays selected until after the last transfer in a message. Drivers
400 * can affect the chipselect signal using cs_change.
402 * (i) If the transfer isn't the last one in the message, this flag is
403 * used to make the chipselect briefly go inactive in the middle of the
404 * message. Toggling chipselect in this way may be needed to terminate
405 * a chip command, letting a single spi_message perform all of group of
406 * chip transactions together.
408 * (ii) When the transfer is the last one in the message, the chip may
409 * stay selected until the next transfer. On multi-device SPI busses
410 * with nothing blocking messages going to other devices, this is just
411 * a performance hint; starting a message to another device deselects
412 * this one. But in other cases, this can be used to ensure correctness.
413 * Some devices need protocol transactions to be built from a series of
414 * spi_message submissions, where the content of one message is determined
415 * by the results of previous messages and where the whole transaction
416 * ends when the chipselect goes intactive.
418 * The code that submits an spi_message (and its spi_transfers)
419 * to the lower layers is responsible for managing its memory.
420 * Zero-initialize every field you don't set up explicitly, to
421 * insulate against future API updates. After you submit a message
422 * and its transfers, ignore them until its completion callback.
424 struct spi_transfer {
425 /* it's ok if tx_buf == rx_buf (right?)
426 * for MicroWire, one buffer must be null
427 * buffers must work with dma_*map_single() calls, unless
428 * spi_message.is_dma_mapped reports a pre-existing mapping
437 unsigned cs_change:1;
442 struct list_head transfer_list;
446 * struct spi_message - one multi-segment SPI transaction
447 * @transfers: list of transfer segments in this transaction
448 * @spi: SPI device to which the transaction is queued
449 * @is_dma_mapped: if true, the caller provided both dma and cpu virtual
450 * addresses for each transfer buffer
451 * @complete: called to report transaction completions
452 * @context: the argument to complete() when it's called
453 * @actual_length: the total number of bytes that were transferred in all
454 * successful segments
455 * @status: zero for success, else negative errno
456 * @queue: for use by whichever driver currently owns the message
457 * @state: for use by whichever driver currently owns the message
459 * A @spi_message is used to execute an atomic sequence of data transfers,
460 * each represented by a struct spi_transfer. The sequence is "atomic"
461 * in the sense that no other spi_message may use that SPI bus until that
462 * sequence completes. On some systems, many such sequences can execute as
463 * as single programmed DMA transfer. On all systems, these messages are
464 * queued, and might complete after transactions to other devices. Messages
465 * sent to a given spi_device are alway executed in FIFO order.
467 * The code that submits an spi_message (and its spi_transfers)
468 * to the lower layers is responsible for managing its memory.
469 * Zero-initialize every field you don't set up explicitly, to
470 * insulate against future API updates. After you submit a message
471 * and its transfers, ignore them until its completion callback.
474 struct list_head transfers;
476 struct spi_device *spi;
478 unsigned is_dma_mapped:1;
480 /* REVISIT: we might want a flag affecting the behavior of the
481 * last transfer ... allowing things like "read 16 bit length L"
482 * immediately followed by "read L bytes". Basically imposing
483 * a specific message scheduling algorithm.
485 * Some controller drivers (message-at-a-time queue processing)
486 * could provide that as their default scheduling algorithm. But
487 * others (with multi-message pipelines) could need a flag to
488 * tell them about such special cases.
491 /* completion is reported through a callback */
492 void (*complete)(void *context);
494 unsigned actual_length;
497 /* for optional use by whatever driver currently owns the
498 * spi_message ... between calls to spi_async and then later
499 * complete(), that's the spi_master controller driver.
501 struct list_head queue;
505 static inline void spi_message_init(struct spi_message *m)
507 memset(m, 0, sizeof *m);
508 INIT_LIST_HEAD(&m->transfers);
512 spi_message_add_tail(struct spi_transfer *t, struct spi_message *m)
514 list_add_tail(&t->transfer_list, &m->transfers);
518 spi_transfer_del(struct spi_transfer *t)
520 list_del(&t->transfer_list);
523 /* It's fine to embed message and transaction structures in other data
524 * structures so long as you don't free them while they're in use.
527 static inline struct spi_message *spi_message_alloc(unsigned ntrans, gfp_t flags)
529 struct spi_message *m;
531 m = kzalloc(sizeof(struct spi_message)
532 + ntrans * sizeof(struct spi_transfer),
536 struct spi_transfer *t = (struct spi_transfer *)(m + 1);
538 INIT_LIST_HEAD(&m->transfers);
539 for (i = 0; i < ntrans; i++, t++)
540 spi_message_add_tail(t, m);
545 static inline void spi_message_free(struct spi_message *m)
550 extern int spi_setup(struct spi_device *spi);
551 extern int spi_async(struct spi_device *spi, struct spi_message *message);
552 extern int spi_async_locked(struct spi_device *spi,
553 struct spi_message *message);
555 /*---------------------------------------------------------------------------*/
557 /* All these synchronous SPI transfer routines are utilities layered
558 * over the core async transfer primitive. Here, "synchronous" means
559 * they will sleep uninterruptibly until the async transfer completes.
562 extern int spi_sync(struct spi_device *spi, struct spi_message *message);
563 extern int spi_sync_locked(struct spi_device *spi, struct spi_message *message);
564 extern int spi_bus_lock(struct spi_master *master);
565 extern int spi_bus_unlock(struct spi_master *master);
568 * spi_write - SPI synchronous write
569 * @spi: device to which data will be written
571 * @len: data buffer size
574 * This writes the buffer and returns zero or a negative error code.
575 * Callable only from contexts that can sleep.
578 spi_write(struct spi_device *spi, const u8 *buf, size_t len)
580 struct spi_transfer t = {
584 struct spi_message m;
586 spi_message_init(&m);
587 spi_message_add_tail(&t, &m);
588 return spi_sync(spi, &m);
592 * spi_read - SPI synchronous read
593 * @spi: device from which data will be read
595 * @len: data buffer size
598 * This reads the buffer and returns zero or a negative error code.
599 * Callable only from contexts that can sleep.
602 spi_read(struct spi_device *spi, u8 *buf, size_t len)
604 struct spi_transfer t = {
608 struct spi_message m;
610 spi_message_init(&m);
611 spi_message_add_tail(&t, &m);
612 return spi_sync(spi, &m);
615 /* this copies txbuf and rxbuf data; for small transfers only! */
616 extern int spi_write_then_read(struct spi_device *spi,
617 const u8 *txbuf, unsigned n_tx,
618 u8 *rxbuf, unsigned n_rx);
621 * spi_w8r8 - SPI synchronous 8 bit write followed by 8 bit read
622 * @spi: device with which data will be exchanged
623 * @cmd: command to be written before data is read back
626 * This returns the (unsigned) eight bit number returned by the
627 * device, or else a negative error code. Callable only from
628 * contexts that can sleep.
630 static inline ssize_t spi_w8r8(struct spi_device *spi, u8 cmd)
635 status = spi_write_then_read(spi, &cmd, 1, &result, 1);
637 /* return negative errno or unsigned value */
638 return (status < 0) ? status : result;
642 * spi_w8r16 - SPI synchronous 8 bit write followed by 16 bit read
643 * @spi: device with which data will be exchanged
644 * @cmd: command to be written before data is read back
647 * This returns the (unsigned) sixteen bit number returned by the
648 * device, or else a negative error code. Callable only from
649 * contexts that can sleep.
651 * The number is returned in wire-order, which is at least sometimes
654 static inline ssize_t spi_w8r16(struct spi_device *spi, u8 cmd)
659 status = spi_write_then_read(spi, &cmd, 1, (u8 *) &result, 2);
661 /* return negative errno or unsigned value */
662 return (status < 0) ? status : result;
665 /*---------------------------------------------------------------------------*/
668 * INTERFACE between board init code and SPI infrastructure.
670 * No SPI driver ever sees these SPI device table segments, but
671 * it's how the SPI core (or adapters that get hotplugged) grows
672 * the driver model tree.
674 * As a rule, SPI devices can't be probed. Instead, board init code
675 * provides a table listing the devices which are present, with enough
676 * information to bind and set up the device's driver. There's basic
677 * support for nonstatic configurations too; enough to handle adding
678 * parport adapters, or microcontrollers acting as USB-to-SPI bridges.
682 * struct spi_board_info - board-specific template for a SPI device
683 * @modalias: Initializes spi_device.modalias; identifies the driver.
684 * @platform_data: Initializes spi_device.platform_data; the particular
685 * data stored there is driver-specific.
686 * @controller_data: Initializes spi_device.controller_data; some
687 * controllers need hints about hardware setup, e.g. for DMA.
688 * @irq: Initializes spi_device.irq; depends on how the board is wired.
689 * @max_speed_hz: Initializes spi_device.max_speed_hz; based on limits
690 * from the chip datasheet and board-specific signal quality issues.
691 * @bus_num: Identifies which spi_master parents the spi_device; unused
692 * by spi_new_device(), and otherwise depends on board wiring.
693 * @chip_select: Initializes spi_device.chip_select; depends on how
694 * the board is wired.
695 * @mode: Initializes spi_device.mode; based on the chip datasheet, board
696 * wiring (some devices support both 3WIRE and standard modes), and
697 * possibly presence of an inverter in the chipselect path.
699 * When adding new SPI devices to the device tree, these structures serve
700 * as a partial device template. They hold information which can't always
701 * be determined by drivers. Information that probe() can establish (such
702 * as the default transfer wordsize) is not included here.
704 * These structures are used in two places. Their primary role is to
705 * be stored in tables of board-specific device descriptors, which are
706 * declared early in board initialization and then used (much later) to
707 * populate a controller's device tree after the that controller's driver
708 * initializes. A secondary (and atypical) role is as a parameter to
709 * spi_new_device() call, which happens after those controller drivers
710 * are active in some dynamic board configuration models.
712 struct spi_board_info {
713 /* the device name and module name are coupled, like platform_bus;
714 * "modalias" is normally the driver name.
716 * platform_data goes to spi_device.dev.platform_data,
717 * controller_data goes to spi_device.controller_data,
720 char modalias[SPI_NAME_SIZE];
721 const void *platform_data;
722 void *controller_data;
725 /* slower signaling on noisy or low voltage boards */
729 /* bus_num is board specific and matches the bus_num of some
730 * spi_master that will probably be registered later.
732 * chip_select reflects how this chip is wired to that master;
733 * it's less than num_chipselect.
738 /* mode becomes spi_device.mode, and is essential for chips
739 * where the default of SPI_CS_HIGH = 0 is wrong.
743 /* ... may need additional spi_device chip config data here.
744 * avoid stuff protocol drivers can set; but include stuff
745 * needed to behave without being bound to a driver:
746 * - quirks like clock rate mattering when not selected
752 spi_register_board_info(struct spi_board_info const *info, unsigned n);
754 /* board init code may ignore whether SPI is configured or not */
756 spi_register_board_info(struct spi_board_info const *info, unsigned n)
761 /* If you're hotplugging an adapter with devices (parport, usb, etc)
762 * use spi_new_device() to describe each device. You can also call
763 * spi_unregister_device() to start making that device vanish, but
764 * normally that would be handled by spi_unregister_master().
766 * You can also use spi_alloc_device() and spi_add_device() to use a two
767 * stage registration sequence for each spi_device. This gives the caller
768 * some more control over the spi_device structure before it is registered,
769 * but requires that caller to initialize fields that would otherwise
770 * be defined using the board info.
772 extern struct spi_device *
773 spi_alloc_device(struct spi_master *master);
776 spi_add_device(struct spi_device *spi);
778 extern struct spi_device *
779 spi_new_device(struct spi_master *, struct spi_board_info *);
782 spi_unregister_device(struct spi_device *spi)
785 device_unregister(&spi->dev);
788 extern const struct spi_device_id *
789 spi_get_device_id(const struct spi_device *sdev);
791 #endif /* __LINUX_SPI_H */