Lines Matching refs:that

89 Many microcontrollers that can run Linux integrate one or more I/O
108    implies that its data is written half a clock before the first
117 trailing clock edge (CPHA=1), that's SPI mode 1.
119 Note that the clock mode is relevant as soon as the chipselect goes
130 main source code, and you should certainly read that chapter of the
171    /sys/bus/spi/devices/spiB.C ... symlink to that physical
175 	that should be used with this device (for hotplug/coldplug)
184 Note that the actual location of the controller's class state depends
194 chips that do support some of automated discovery/enumeration.
205 maybe coupling it with code to initialize pin configurations, so that
215 	/* if your mach-* infrastructure doesn't support kernels that can
291 is wired, plus chip-specific constraints like an important delay that's
294 (There's also "controller_data", information that may be useful to the
300 that is likely the SPI_CS_HIGH bit in the spi_device.mode field, since
301 sharing a bus with a device that interprets chipselect "backwards" is
304 Then your board initialization code would register that table with the SPI
305 infrastructure, so that it's available later when the SPI master controller
313 onto a card that's maybe just thirty square centimeters.  On such systems,
326 board info based on the board that was hotplugged.  Of course, you'd later
327 call at least spi_unregister_device() when that board is removed.
379 or after probe() fails, the driver guarantees that it won't submit
402 	transfer in that atomic group, and potentially saving costs
408     around hardware errata that force the use of bounce buffering).
412     that you've already provided the relevant DMA addresses.
418     of that spi_message is aborted.
422     may be issued only in contexts that may sleep, and they're all
430     wrappers, doing exactly that.
435 done to the device.  However, that can also be called at any time
436 that no message is pending for that device.
443 Note that there are two types of memory your driver must manage as part
448     Don't use the stack, or anything that's declared "static".
467 to get the driver-private data allocated for that device.
478 The driver will initialize the fields of that spi_master, including the
485 publish it to the rest of the system. At that time, device nodes for the
495 Bus numbering is important, since that's how Linux identifies a given
499 and spi_board_info for devices connected to it would use that number.
516 	that's in progress for other SPI devices.
520 		** When you code setup(), ASSUME that the controller
525 	state it dynamically associates with that device.  If you do that,
526 	be sure to provide the cleanup() method to free that state.
530 	that a message is coming in soon, so the subsystem requests the
536 	that there are no more messages pending in the queue and it may
542 	queuing transfers that arrive in the meantime. When the driver is
550 	queuing transfers that arrive in the meantime. When the driver is
565 	This must not sleep. Its responsibility is to arrange that the