1/* 2 * Copyright (C) 2005 David Brownell 3 * 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. 8 * 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. 13 * 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. 17 */ 18 19#ifndef __LINUX_SPI_H 20#define __LINUX_SPI_H 21 22#include <linux/device.h> 23#include <linux/mod_devicetable.h> 24#include <linux/slab.h> 25#include <linux/kthread.h> 26 27/* 28 * INTERFACES between SPI master-side drivers and SPI infrastructure. 29 * (There's no SPI slave support for Linux yet...) 30 */ 31extern struct bus_type spi_bus_type; 32 33/** 34 * struct spi_device - Master side proxy for an SPI slave device 35 * @dev: Driver model representation of the device. 36 * @master: SPI controller used with the device. 37 * @max_speed_hz: Maximum clock rate to be used with this chip 38 * (on this board); may be changed by the device's driver. 39 * The spi_transfer.speed_hz can override this for each transfer. 40 * @chip_select: Chipselect, distinguishing chips handled by @master. 41 * @mode: The spi mode defines how data is clocked out and in. 42 * This may be changed by the device's driver. 43 * The "active low" default for chipselect mode can be overridden 44 * (by specifying SPI_CS_HIGH) as can the "MSB first" default for 45 * each word in a transfer (by specifying SPI_LSB_FIRST). 46 * @bits_per_word: Data transfers involve one or more words; word sizes 47 * like eight or 12 bits are common. In-memory wordsizes are 48 * powers of two bytes (e.g. 20 bit samples use 32 bits). 49 * This may be changed by the device's driver, or left at the 50 * default (0) indicating protocol words are eight bit bytes. 51 * The spi_transfer.bits_per_word can override this for each transfer. 52 * @irq: Negative, or the number passed to request_irq() to receive 53 * interrupts from this device. 54 * @controller_state: Controller's runtime state 55 * @controller_data: Board-specific definitions for controller, such as 56 * FIFO initialization parameters; from board_info.controller_data 57 * @modalias: Name of the driver to use with this device, or an alias 58 * for that name. This appears in the sysfs "modalias" attribute 59 * for driver coldplugging, and in uevents used for hotplugging 60 * @cs_gpio: gpio number of the chipselect line (optional, -EINVAL when 61 * when not using a GPIO line) 62 * 63 * A @spi_device is used to interchange data between an SPI slave 64 * (usually a discrete chip) and CPU memory. 65 * 66 * In @dev, the platform_data is used to hold information about this 67 * device that's meaningful to the device's protocol driver, but not 68 * to its controller. One example might be an identifier for a chip 69 * variant with slightly different functionality; another might be 70 * information about how this particular board wires the chip's pins. 71 */ 72struct spi_device { 73 struct device dev; 74 struct spi_master *master; 75 u32 max_speed_hz; 76 u8 chip_select; 77 u8 mode; 78#define SPI_CPHA 0x01 /* clock phase */ 79#define SPI_CPOL 0x02 /* clock polarity */ 80#define SPI_MODE_0 (0|0) /* (original MicroWire) */ 81#define SPI_MODE_1 (0|SPI_CPHA) 82#define SPI_MODE_2 (SPI_CPOL|0) 83#define SPI_MODE_3 (SPI_CPOL|SPI_CPHA) 84#define SPI_CS_HIGH 0x04 /* chipselect active high? */ 85#define SPI_LSB_FIRST 0x08 /* per-word bits-on-wire */ 86#define SPI_3WIRE 0x10 /* SI/SO signals shared */ 87#define SPI_LOOP 0x20 /* loopback mode */ 88#define SPI_NO_CS 0x40 /* 1 dev/bus, no chipselect */ 89#define SPI_READY 0x80 /* slave pulls low to pause */ 90 u8 bits_per_word; 91 int irq; 92 void *controller_state; 93 void *controller_data; 94 char modalias[SPI_NAME_SIZE]; 95 int cs_gpio; /* chip select gpio */ 96 97 /* 98 * likely need more hooks for more protocol options affecting how 99 * the controller talks to each chip, like: 100 * - memory packing (12 bit samples into low bits, others zeroed) 101 * - priority 102 * - drop chipselect after each word 103 * - chipselect delays 104 * - ... 105 */ 106}; 107 108static inline struct spi_device *to_spi_device(struct device *dev) 109{ 110 return dev ? container_of(dev, struct spi_device, dev) : NULL; 111} 112 113/* most drivers won't need to care about device refcounting */ 114static inline struct spi_device *spi_dev_get(struct spi_device *spi) 115{ 116 return (spi && get_device(&spi->dev)) ? spi : NULL; 117} 118 119static inline void spi_dev_put(struct spi_device *spi) 120{ 121 if (spi) 122 put_device(&spi->dev); 123} 124 125/* ctldata is for the bus_master driver's runtime state */ 126static inline void *spi_get_ctldata(struct spi_device *spi) 127{ 128 return spi->controller_state; 129} 130 131static inline void spi_set_ctldata(struct spi_device *spi, void *state) 132{ 133 spi->controller_state = state; 134} 135 136/* device driver data */ 137 138static inline void spi_set_drvdata(struct spi_device *spi, void *data) 139{ 140 dev_set_drvdata(&spi->dev, data); 141} 142 143static inline void *spi_get_drvdata(struct spi_device *spi) 144{ 145 return dev_get_drvdata(&spi->dev); 146} 147 148struct spi_message; 149 150 151 152/** 153 * struct spi_driver - Host side "protocol" driver 154 * @id_table: List of SPI devices supported by this driver 155 * @probe: Binds this driver to the spi device. Drivers can verify 156 * that the device is actually present, and may need to configure 157 * characteristics (such as bits_per_word) which weren't needed for 158 * the initial configuration done during system setup. 159 * @remove: Unbinds this driver from the spi device 160 * @shutdown: Standard shutdown callback used during system state 161 * transitions such as powerdown/halt and kexec 162 * @suspend: Standard suspend callback used during system state transitions 163 * @resume: Standard resume callback used during system state transitions 164 * @driver: SPI device drivers should initialize the name and owner 165 * field of this structure. 166 * 167 * This represents the kind of device driver that uses SPI messages to 168 * interact with the hardware at the other end of a SPI link. It's called 169 * a "protocol" driver because it works through messages rather than talking 170 * directly to SPI hardware (which is what the underlying SPI controller 171 * driver does to pass those messages). These protocols are defined in the 172 * specification for the device(s) supported by the driver. 173 * 174 * As a rule, those device protocols represent the lowest level interface 175 * supported by a driver, and it will support upper level interfaces too. 176 * Examples of such upper levels include frameworks like MTD, networking, 177 * MMC, RTC, filesystem character device nodes, and hardware monitoring. 178 */ 179struct spi_driver { 180 const struct spi_device_id *id_table; 181 int (*probe)(struct spi_device *spi); 182 int (*remove)(struct spi_device *spi); 183 void (*shutdown)(struct spi_device *spi); 184 int (*suspend)(struct spi_device *spi, pm_message_t mesg); 185 int (*resume)(struct spi_device *spi); 186 struct device_driver driver; 187}; 188 189static inline struct spi_driver *to_spi_driver(struct device_driver *drv) 190{ 191 return drv ? container_of(drv, struct spi_driver, driver) : NULL; 192} 193 194extern int spi_register_driver(struct spi_driver *sdrv); 195 196/** 197 * spi_unregister_driver - reverse effect of spi_register_driver 198 * @sdrv: the driver to unregister 199 * Context: can sleep 200 */ 201static inline void spi_unregister_driver(struct spi_driver *sdrv) 202{ 203 if (sdrv) 204 driver_unregister(&sdrv->driver); 205} 206 207/** 208 * module_spi_driver() - Helper macro for registering a SPI driver 209 * @__spi_driver: spi_driver struct 210 * 211 * Helper macro for SPI drivers which do not do anything special in module 212 * init/exit. This eliminates a lot of boilerplate. Each module may only 213 * use this macro once, and calling it replaces module_init() and module_exit() 214 */ 215#define module_spi_driver(__spi_driver) \ 216 module_driver(__spi_driver, spi_register_driver, \ 217 spi_unregister_driver) 218 219/** 220 * struct spi_master - interface to SPI master controller 221 * @dev: device interface to this driver 222 * @list: link with the global spi_master list 223 * @bus_num: board-specific (and often SOC-specific) identifier for a 224 * given SPI controller. 225 * @num_chipselect: chipselects are used to distinguish individual 226 * SPI slaves, and are numbered from zero to num_chipselects. 227 * each slave has a chipselect signal, but it's common that not 228 * every chipselect is connected to a slave. 229 * @dma_alignment: SPI controller constraint on DMA buffers alignment. 230 * @mode_bits: flags understood by this controller driver 231 * @flags: other constraints relevant to this driver 232 * @bus_lock_spinlock: spinlock for SPI bus locking 233 * @bus_lock_mutex: mutex for SPI bus locking 234 * @bus_lock_flag: indicates that the SPI bus is locked for exclusive use 235 * @setup: updates the device mode and clocking records used by a 236 * device's SPI controller; protocol code may call this. This 237 * must fail if an unrecognized or unsupported mode is requested. 238 * It's always safe to call this unless transfers are pending on 239 * the device whose settings are being modified. 240 * @transfer: adds a message to the controller's transfer queue. 241 * @cleanup: frees controller-specific state 242 * @queued: whether this master is providing an internal message queue 243 * @kworker: thread struct for message pump 244 * @kworker_task: pointer to task for message pump kworker thread 245 * @pump_messages: work struct for scheduling work to the message pump 246 * @queue_lock: spinlock to syncronise access to message queue 247 * @queue: message queue 248 * @cur_msg: the currently in-flight message 249 * @busy: message pump is busy 250 * @running: message pump is running 251 * @rt: whether this queue is set to run as a realtime task 252 * @prepare_transfer_hardware: a message will soon arrive from the queue 253 * so the subsystem requests the driver to prepare the transfer hardware 254 * by issuing this call 255 * @transfer_one_message: the subsystem calls the driver to transfer a single 256 * message while queuing transfers that arrive in the meantime. When the 257 * driver is finished with this message, it must call 258 * spi_finalize_current_message() so the subsystem can issue the next 259 * transfer 260 * @unprepare_transfer_hardware: there are currently no more messages on the 261 * queue so the subsystem notifies the driver that it may relax the 262 * hardware by issuing this call 263 * @cs_gpios: Array of GPIOs to use as chip select lines; one per CS 264 * number. Any individual value may be -EINVAL for CS lines that 265 * are not GPIOs (driven by the SPI controller itself). 266 * 267 * Each SPI master controller can communicate with one or more @spi_device 268 * children. These make a small bus, sharing MOSI, MISO and SCK signals 269 * but not chip select signals. Each device may be configured to use a 270 * different clock rate, since those shared signals are ignored unless 271 * the chip is selected. 272 * 273 * The driver for an SPI controller manages access to those devices through 274 * a queue of spi_message transactions, copying data between CPU memory and 275 * an SPI slave device. For each such message it queues, it calls the 276 * message's completion function when the transaction completes. 277 */ 278struct spi_master { 279 struct device dev; 280 281 struct list_head list; 282 283 /* other than negative (== assign one dynamically), bus_num is fully 284 * board-specific. usually that simplifies to being SOC-specific. 285 * example: one SOC has three SPI controllers, numbered 0..2, 286 * and one board's schematics might show it using SPI-2. software 287 * would normally use bus_num=2 for that controller. 288 */ 289 s16 bus_num; 290 291 /* chipselects will be integral to many controllers; some others 292 * might use board-specific GPIOs. 293 */ 294 u16 num_chipselect; 295 296 /* some SPI controllers pose alignment requirements on DMAable 297 * buffers; let protocol drivers know about these requirements. 298 */ 299 u16 dma_alignment; 300 301 /* spi_device.mode flags understood by this controller driver */ 302 u16 mode_bits; 303 304 /* other constraints relevant to this driver */ 305 u16 flags; 306#define SPI_MASTER_HALF_DUPLEX BIT(0) /* can't do full duplex */ 307#define SPI_MASTER_NO_RX BIT(1) /* can't do buffer read */ 308#define SPI_MASTER_NO_TX BIT(2) /* can't do buffer write */ 309 310 /* lock and mutex for SPI bus locking */ 311 spinlock_t bus_lock_spinlock; 312 struct mutex bus_lock_mutex; 313 314 /* flag indicating that the SPI bus is locked for exclusive use */ 315 bool bus_lock_flag; 316 317 /* Setup mode and clock, etc (spi driver may call many times). 318 * 319 * IMPORTANT: this may be called when transfers to another 320 * device are active. DO NOT UPDATE SHARED REGISTERS in ways 321 * which could break those transfers. 322 */ 323 int (*setup)(struct spi_device *spi); 324 325 /* bidirectional bulk transfers 326 * 327 * + The transfer() method may not sleep; its main role is 328 * just to add the message to the queue. 329 * + For now there's no remove-from-queue operation, or 330 * any other request management 331 * + To a given spi_device, message queueing is pure fifo 332 * 333 * + The master's main job is to process its message queue, 334 * selecting a chip then transferring data 335 * + If there are multiple spi_device children, the i/o queue 336 * arbitration algorithm is unspecified (round robin, fifo, 337 * priority, reservations, preemption, etc) 338 * 339 * + Chipselect stays active during the entire message 340 * (unless modified by spi_transfer.cs_change != 0). 341 * + The message transfers use clock and SPI mode parameters 342 * previously established by setup() for this device 343 */ 344 int (*transfer)(struct spi_device *spi, 345 struct spi_message *mesg); 346 347 /* called on release() to free memory provided by spi_master */ 348 void (*cleanup)(struct spi_device *spi); 349 350 /* 351 * These hooks are for drivers that want to use the generic 352 * master transfer queueing mechanism. If these are used, the 353 * transfer() function above must NOT be specified by the driver. 354 * Over time we expect SPI drivers to be phased over to this API. 355 */ 356 bool queued; 357 struct kthread_worker kworker; 358 struct task_struct *kworker_task; 359 struct kthread_work pump_messages; 360 spinlock_t queue_lock; 361 struct list_head queue; 362 struct spi_message *cur_msg; 363 bool busy; 364 bool running; 365 bool rt; 366 367 int (*prepare_transfer_hardware)(struct spi_master *master); 368 int (*transfer_one_message)(struct spi_master *master, 369 struct spi_message *mesg); 370 int (*unprepare_transfer_hardware)(struct spi_master *master); 371 /* gpio chip select */ 372 int *cs_gpios; 373}; 374 375static inline void *spi_master_get_devdata(struct spi_master *master) 376{ 377 return dev_get_drvdata(&master->dev); 378} 379 380static inline void spi_master_set_devdata(struct spi_master *master, void *data) 381{ 382 dev_set_drvdata(&master->dev, data); 383} 384 385static inline struct spi_master *spi_master_get(struct spi_master *master) 386{ 387 if (!master || !get_device(&master->dev)) 388 return NULL; 389 return master; 390} 391 392static inline void spi_master_put(struct spi_master *master) 393{ 394 if (master) 395 put_device(&master->dev); 396} 397 398/* PM calls that need to be issued by the driver */ 399extern int spi_master_suspend(struct spi_master *master); 400extern int spi_master_resume(struct spi_master *master); 401 402/* Calls the driver make to interact with the message queue */ 403extern struct spi_message *spi_get_next_queued_message(struct spi_master *master); 404extern void spi_finalize_current_message(struct spi_master *master); 405 406/* the spi driver core manages memory for the spi_master classdev */ 407extern struct spi_master * 408spi_alloc_master(struct device *host, unsigned size); 409 410extern int spi_register_master(struct spi_master *master); 411extern void spi_unregister_master(struct spi_master *master); 412 413extern struct spi_master *spi_busnum_to_master(u16 busnum); 414 415/*---------------------------------------------------------------------------*/ 416 417/* 418 * I/O INTERFACE between SPI controller and protocol drivers 419 * 420 * Protocol drivers use a queue of spi_messages, each transferring data 421 * between the controller and memory buffers. 422 * 423 * The spi_messages themselves consist of a series of read+write transfer 424 * segments. Those segments always read the same number of bits as they 425 * write; but one or the other is easily ignored by passing a null buffer 426 * pointer. (This is unlike most types of I/O API, because SPI hardware 427 * is full duplex.) 428 * 429 * NOTE: Allocation of spi_transfer and spi_message memory is entirely 430 * up to the protocol driver, which guarantees the integrity of both (as 431 * well as the data buffers) for as long as the message is queued. 432 */ 433 434/** 435 * struct spi_transfer - a read/write buffer pair 436 * @tx_buf: data to be written (dma-safe memory), or NULL 437 * @rx_buf: data to be read (dma-safe memory), or NULL 438 * @tx_dma: DMA address of tx_buf, if @spi_message.is_dma_mapped 439 * @rx_dma: DMA address of rx_buf, if @spi_message.is_dma_mapped 440 * @len: size of rx and tx buffers (in bytes) 441 * @speed_hz: Select a speed other than the device default for this 442 * transfer. If 0 the default (from @spi_device) is used. 443 * @bits_per_word: select a bits_per_word other than the device default 444 * for this transfer. If 0 the default (from @spi_device) is used. 445 * @cs_change: affects chipselect after this transfer completes 446 * @delay_usecs: microseconds to delay after this transfer before 447 * (optionally) changing the chipselect status, then starting 448 * the next transfer or completing this @spi_message. 449 * @transfer_list: transfers are sequenced through @spi_message.transfers 450 * 451 * SPI transfers always write the same number of bytes as they read. 452 * Protocol drivers should always provide @rx_buf and/or @tx_buf. 453 * In some cases, they may also want to provide DMA addresses for 454 * the data being transferred; that may reduce overhead, when the 455 * underlying driver uses dma. 456 * 457 * If the transmit buffer is null, zeroes will be shifted out 458 * while filling @rx_buf. If the receive buffer is null, the data 459 * shifted in will be discarded. Only "len" bytes shift out (or in). 460 * It's an error to try to shift out a partial word. (For example, by 461 * shifting out three bytes with word size of sixteen or twenty bits; 462 * the former uses two bytes per word, the latter uses four bytes.) 463 * 464 * In-memory data values are always in native CPU byte order, translated 465 * from the wire byte order (big-endian except with SPI_LSB_FIRST). So 466 * for example when bits_per_word is sixteen, buffers are 2N bytes long 467 * (@len = 2N) and hold N sixteen bit words in CPU byte order. 468 * 469 * When the word size of the SPI transfer is not a power-of-two multiple 470 * of eight bits, those in-memory words include extra bits. In-memory 471 * words are always seen by protocol drivers as right-justified, so the 472 * undefined (rx) or unused (tx) bits are always the most significant bits. 473 * 474 * All SPI transfers start with the relevant chipselect active. Normally 475 * it stays selected until after the last transfer in a message. Drivers 476 * can affect the chipselect signal using cs_change. 477 * 478 * (i) If the transfer isn't the last one in the message, this flag is 479 * used to make the chipselect briefly go inactive in the middle of the 480 * message. Toggling chipselect in this way may be needed to terminate 481 * a chip command, letting a single spi_message perform all of group of 482 * chip transactions together. 483 * 484 * (ii) When the transfer is the last one in the message, the chip may 485 * stay selected until the next transfer. On multi-device SPI busses 486 * with nothing blocking messages going to other devices, this is just 487 * a performance hint; starting a message to another device deselects 488 * this one. But in other cases, this can be used to ensure correctness. 489 * Some devices need protocol transactions to be built from a series of 490 * spi_message submissions, where the content of one message is determined 491 * by the results of previous messages and where the whole transaction 492 * ends when the chipselect goes intactive. 493 * 494 * The code that submits an spi_message (and its spi_transfers) 495 * to the lower layers is responsible for managing its memory. 496 * Zero-initialize every field you don't set up explicitly, to 497 * insulate against future API updates. After you submit a message 498 * and its transfers, ignore them until its completion callback. 499 */ 500struct spi_transfer { 501 /* it's ok if tx_buf == rx_buf (right?) 502 * for MicroWire, one buffer must be null 503 * buffers must work with dma_*map_single() calls, unless 504 * spi_message.is_dma_mapped reports a pre-existing mapping 505 */ 506 const void *tx_buf; 507 void *rx_buf; 508 unsigned len; 509 510 dma_addr_t tx_dma; 511 dma_addr_t rx_dma; 512 513 unsigned cs_change:1; 514 u8 bits_per_word; 515 u16 delay_usecs; 516 u32 speed_hz; 517 518 struct list_head transfer_list; 519}; 520 521/** 522 * struct spi_message - one multi-segment SPI transaction 523 * @transfers: list of transfer segments in this transaction 524 * @spi: SPI device to which the transaction is queued 525 * @is_dma_mapped: if true, the caller provided both dma and cpu virtual 526 * addresses for each transfer buffer 527 * @complete: called to report transaction completions 528 * @context: the argument to complete() when it's called 529 * @actual_length: the total number of bytes that were transferred in all 530 * successful segments 531 * @status: zero for success, else negative errno 532 * @queue: for use by whichever driver currently owns the message 533 * @state: for use by whichever driver currently owns the message 534 * 535 * A @spi_message is used to execute an atomic sequence of data transfers, 536 * each represented by a struct spi_transfer. The sequence is "atomic" 537 * in the sense that no other spi_message may use that SPI bus until that 538 * sequence completes. On some systems, many such sequences can execute as 539 * as single programmed DMA transfer. On all systems, these messages are 540 * queued, and might complete after transactions to other devices. Messages 541 * sent to a given spi_device are alway executed in FIFO order. 542 * 543 * The code that submits an spi_message (and its spi_transfers) 544 * to the lower layers is responsible for managing its memory. 545 * Zero-initialize every field you don't set up explicitly, to 546 * insulate against future API updates. After you submit a message 547 * and its transfers, ignore them until its completion callback. 548 */ 549struct spi_message { 550 struct list_head transfers; 551 552 struct spi_device *spi; 553 554 unsigned is_dma_mapped:1; 555 556 /* REVISIT: we might want a flag affecting the behavior of the 557 * last transfer ... allowing things like "read 16 bit length L" 558 * immediately followed by "read L bytes". Basically imposing 559 * a specific message scheduling algorithm. 560 * 561 * Some controller drivers (message-at-a-time queue processing) 562 * could provide that as their default scheduling algorithm. But 563 * others (with multi-message pipelines) could need a flag to 564 * tell them about such special cases. 565 */ 566 567 /* completion is reported through a callback */ 568 void (*complete)(void *context); 569 void *context; 570 unsigned actual_length; 571 int status; 572 573 /* for optional use by whatever driver currently owns the 574 * spi_message ... between calls to spi_async and then later 575 * complete(), that's the spi_master controller driver. 576 */ 577 struct list_head queue; 578 void *state; 579}; 580 581static inline void spi_message_init(struct spi_message *m) 582{ 583 memset(m, 0, sizeof *m); 584 INIT_LIST_HEAD(&m->transfers); 585} 586 587static inline void 588spi_message_add_tail(struct spi_transfer *t, struct spi_message *m) 589{ 590 list_add_tail(&t->transfer_list, &m->transfers); 591} 592 593static inline void 594spi_transfer_del(struct spi_transfer *t) 595{ 596 list_del(&t->transfer_list); 597} 598 599/** 600 * spi_message_init_with_transfers - Initialize spi_message and append transfers 601 * @m: spi_message to be initialized 602 * @xfers: An array of spi transfers 603 * @num_xfers: Number of items in the xfer array 604 * 605 * This function initializes the given spi_message and adds each spi_transfer in 606 * the given array to the message. 607 */ 608static inline void 609spi_message_init_with_transfers(struct spi_message *m, 610struct spi_transfer *xfers, unsigned int num_xfers) 611{ 612 unsigned int i; 613 614 spi_message_init(m); 615 for (i = 0; i < num_xfers; ++i) 616 spi_message_add_tail(&xfers[i], m); 617} 618 619/* It's fine to embed message and transaction structures in other data 620 * structures so long as you don't free them while they're in use. 621 */ 622 623static inline struct spi_message *spi_message_alloc(unsigned ntrans, gfp_t flags) 624{ 625 struct spi_message *m; 626 627 m = kzalloc(sizeof(struct spi_message) 628 + ntrans * sizeof(struct spi_transfer), 629 flags); 630 if (m) { 631 unsigned i; 632 struct spi_transfer *t = (struct spi_transfer *)(m + 1); 633 634 INIT_LIST_HEAD(&m->transfers); 635 for (i = 0; i < ntrans; i++, t++) 636 spi_message_add_tail(t, m); 637 } 638 return m; 639} 640 641static inline void spi_message_free(struct spi_message *m) 642{ 643 kfree(m); 644} 645 646extern int spi_setup(struct spi_device *spi); 647extern int spi_async(struct spi_device *spi, struct spi_message *message); 648extern int spi_async_locked(struct spi_device *spi, 649 struct spi_message *message); 650 651/*---------------------------------------------------------------------------*/ 652 653/* All these synchronous SPI transfer routines are utilities layered 654 * over the core async transfer primitive. Here, "synchronous" means 655 * they will sleep uninterruptibly until the async transfer completes. 656 */ 657 658extern int spi_sync(struct spi_device *spi, struct spi_message *message); 659extern int spi_sync_locked(struct spi_device *spi, struct spi_message *message); 660extern int spi_bus_lock(struct spi_master *master); 661extern int spi_bus_unlock(struct spi_master *master); 662 663/** 664 * spi_write - SPI synchronous write 665 * @spi: device to which data will be written 666 * @buf: data buffer 667 * @len: data buffer size 668 * Context: can sleep 669 * 670 * This writes the buffer and returns zero or a negative error code. 671 * Callable only from contexts that can sleep. 672 */ 673static inline int 674spi_write(struct spi_device *spi, const void *buf, size_t len) 675{ 676 struct spi_transfer t = { 677 .tx_buf = buf, 678 .len = len, 679 }; 680 struct spi_message m; 681 682 spi_message_init(&m); 683 spi_message_add_tail(&t, &m); 684 return spi_sync(spi, &m); 685} 686 687/** 688 * spi_read - SPI synchronous read 689 * @spi: device from which data will be read 690 * @buf: data buffer 691 * @len: data buffer size 692 * Context: can sleep 693 * 694 * This reads the buffer and returns zero or a negative error code. 695 * Callable only from contexts that can sleep. 696 */ 697static inline int 698spi_read(struct spi_device *spi, void *buf, size_t len) 699{ 700 struct spi_transfer t = { 701 .rx_buf = buf, 702 .len = len, 703 }; 704 struct spi_message m; 705 706 spi_message_init(&m); 707 spi_message_add_tail(&t, &m); 708 return spi_sync(spi, &m); 709} 710 711/** 712 * spi_sync_transfer - synchronous SPI data transfer 713 * @spi: device with which data will be exchanged 714 * @xfers: An array of spi_transfers 715 * @num_xfers: Number of items in the xfer array 716 * Context: can sleep 717 * 718 * Does a synchronous SPI data transfer of the given spi_transfer array. 719 * 720 * For more specific semantics see spi_sync(). 721 * 722 * It returns zero on success, else a negative error code. 723 */ 724static inline int 725spi_sync_transfer(struct spi_device *spi, struct spi_transfer *xfers, 726 unsigned int num_xfers) 727{ 728 struct spi_message msg; 729 730 spi_message_init_with_transfers(&msg, xfers, num_xfers); 731 732 return spi_sync(spi, &msg); 733} 734 735/* this copies txbuf and rxbuf data; for small transfers only! */ 736extern int spi_write_then_read(struct spi_device *spi, 737 const void *txbuf, unsigned n_tx, 738 void *rxbuf, unsigned n_rx); 739 740/** 741 * spi_w8r8 - SPI synchronous 8 bit write followed by 8 bit read 742 * @spi: device with which data will be exchanged 743 * @cmd: command to be written before data is read back 744 * Context: can sleep 745 * 746 * This returns the (unsigned) eight bit number returned by the 747 * device, or else a negative error code. Callable only from 748 * contexts that can sleep. 749 */ 750static inline ssize_t spi_w8r8(struct spi_device *spi, u8 cmd) 751{ 752 ssize_t status; 753 u8 result; 754 755 status = spi_write_then_read(spi, &cmd, 1, &result, 1); 756 757 /* return negative errno or unsigned value */ 758 return (status < 0) ? status : result; 759} 760 761/** 762 * spi_w8r16 - SPI synchronous 8 bit write followed by 16 bit read 763 * @spi: device with which data will be exchanged 764 * @cmd: command to be written before data is read back 765 * Context: can sleep 766 * 767 * This returns the (unsigned) sixteen bit number returned by the 768 * device, or else a negative error code. Callable only from 769 * contexts that can sleep. 770 * 771 * The number is returned in wire-order, which is at least sometimes 772 * big-endian. 773 */ 774static inline ssize_t spi_w8r16(struct spi_device *spi, u8 cmd) 775{ 776 ssize_t status; 777 u16 result; 778 779 status = spi_write_then_read(spi, &cmd, 1, (u8 *) &result, 2); 780 781 /* return negative errno or unsigned value */ 782 return (status < 0) ? status : result; 783} 784 785/*---------------------------------------------------------------------------*/ 786 787/* 788 * INTERFACE between board init code and SPI infrastructure. 789 * 790 * No SPI driver ever sees these SPI device table segments, but 791 * it's how the SPI core (or adapters that get hotplugged) grows 792 * the driver model tree. 793 * 794 * As a rule, SPI devices can't be probed. Instead, board init code 795 * provides a table listing the devices which are present, with enough 796 * information to bind and set up the device's driver. There's basic 797 * support for nonstatic configurations too; enough to handle adding 798 * parport adapters, or microcontrollers acting as USB-to-SPI bridges. 799 */ 800 801/** 802 * struct spi_board_info - board-specific template for a SPI device 803 * @modalias: Initializes spi_device.modalias; identifies the driver. 804 * @platform_data: Initializes spi_device.platform_data; the particular 805 * data stored there is driver-specific. 806 * @controller_data: Initializes spi_device.controller_data; some 807 * controllers need hints about hardware setup, e.g. for DMA. 808 * @irq: Initializes spi_device.irq; depends on how the board is wired. 809 * @max_speed_hz: Initializes spi_device.max_speed_hz; based on limits 810 * from the chip datasheet and board-specific signal quality issues. 811 * @bus_num: Identifies which spi_master parents the spi_device; unused 812 * by spi_new_device(), and otherwise depends on board wiring. 813 * @chip_select: Initializes spi_device.chip_select; depends on how 814 * the board is wired. 815 * @mode: Initializes spi_device.mode; based on the chip datasheet, board 816 * wiring (some devices support both 3WIRE and standard modes), and 817 * possibly presence of an inverter in the chipselect path. 818 * 819 * When adding new SPI devices to the device tree, these structures serve 820 * as a partial device template. They hold information which can't always 821 * be determined by drivers. Information that probe() can establish (such 822 * as the default transfer wordsize) is not included here. 823 * 824 * These structures are used in two places. Their primary role is to 825 * be stored in tables of board-specific device descriptors, which are 826 * declared early in board initialization and then used (much later) to 827 * populate a controller's device tree after the that controller's driver 828 * initializes. A secondary (and atypical) role is as a parameter to 829 * spi_new_device() call, which happens after those controller drivers 830 * are active in some dynamic board configuration models. 831 */ 832struct spi_board_info { 833 /* the device name and module name are coupled, like platform_bus; 834 * "modalias" is normally the driver name. 835 * 836 * platform_data goes to spi_device.dev.platform_data, 837 * controller_data goes to spi_device.controller_data, 838 * irq is copied too 839 */ 840 char modalias[SPI_NAME_SIZE]; 841 const void *platform_data; 842 void *controller_data; 843 int irq; 844 845 /* slower signaling on noisy or low voltage boards */ 846 u32 max_speed_hz; 847 848 849 /* bus_num is board specific and matches the bus_num of some 850 * spi_master that will probably be registered later. 851 * 852 * chip_select reflects how this chip is wired to that master; 853 * it's less than num_chipselect. 854 */ 855 u16 bus_num; 856 u16 chip_select; 857 858 /* mode becomes spi_device.mode, and is essential for chips 859 * where the default of SPI_CS_HIGH = 0 is wrong. 860 */ 861 u8 mode; 862 863 /* ... may need additional spi_device chip config data here. 864 * avoid stuff protocol drivers can set; but include stuff 865 * needed to behave without being bound to a driver: 866 * - quirks like clock rate mattering when not selected 867 */ 868}; 869 870#ifdef CONFIG_SPI 871extern int 872spi_register_board_info(struct spi_board_info const *info, unsigned n); 873#else 874/* board init code may ignore whether SPI is configured or not */ 875static inline int 876spi_register_board_info(struct spi_board_info const *info, unsigned n) 877 { return 0; } 878#endif 879 880 881/* If you're hotplugging an adapter with devices (parport, usb, etc) 882 * use spi_new_device() to describe each device. You can also call 883 * spi_unregister_device() to start making that device vanish, but 884 * normally that would be handled by spi_unregister_master(). 885 * 886 * You can also use spi_alloc_device() and spi_add_device() to use a two 887 * stage registration sequence for each spi_device. This gives the caller 888 * some more control over the spi_device structure before it is registered, 889 * but requires that caller to initialize fields that would otherwise 890 * be defined using the board info. 891 */ 892extern struct spi_device * 893spi_alloc_device(struct spi_master *master); 894 895extern int 896spi_add_device(struct spi_device *spi); 897 898extern struct spi_device * 899spi_new_device(struct spi_master *, struct spi_board_info *); 900 901static inline void 902spi_unregister_device(struct spi_device *spi) 903{ 904 if (spi) 905 device_unregister(&spi->dev); 906} 907 908extern const struct spi_device_id * 909spi_get_device_id(const struct spi_device *sdev); 910 911#endif /* __LINUX_SPI_H */ 912