Lines Matching +full:memory +full:- +full:controller

1 /* SPDX-License-Identifier: GPL-2.0+ */
59  * enum spi_mem_data_dir - describes the direction of a SPI memory data
60  *			   transfer from the controller perspective
62  * @SPI_MEM_DATA_IN: data coming from the SPI memory
63  * @SPI_MEM_DATA_OUT: data sent to the SPI memory
72  * struct spi_mem_op - describes a SPI memory operation
74  *		sent MSB-first.
96  * @data.buf.in: input buffer (must be DMA-able)
97  * @data.buf.out: output buffer (must be DMA-able)
142  * struct spi_mem_dirmap_info - Direct mapping information
144  *	     the memory device is accessed
148  * These information are used by the controller specific implementation to know
149  * the portion of memory that is directly mapped and the spi_mem_op that should
152  * direction is directly encoded in the ->op_tmpl.data.dir field.
161  * struct spi_mem_dirmap_desc - Direct mapping descriptor
162  * @mem: the SPI memory device this direct mapping is attached to
164  * @nodirmap: set to 1 if the SPI controller does not implement
165  *	      ->mem_ops->dirmap_create() or when this function returned an
167  *	      calls will use spi_mem_exec_op() to access the memory. This is a
169  *	      no matter whether the controller supports direct mapping or not
170  * @priv: field pointing to controller specific data
173  * spi_mem_dirmap_create() and controller implementation of ->create_dirmap()
174  * can create/attach direct mapping resources to the descriptor in the ->priv
185  * struct spi_mem - describes a SPI memory device
188  * @name: name of the SPI memory device
190  * Extra information that describe the SPI memory device and may be needed by
191  * the controller to properly handle this device should be placed here.
193  * One example would be the device size since some controller expose their SPI
194  * mem devices through a io-mapped region.
203  * struct spi_mem_set_drvdata() - attach driver private data to a SPI mem
205  * @mem: memory device
206  * @data: data to attach to the memory device
210 	mem->drvpriv = data;  in spi_mem_set_drvdata()
214  * struct spi_mem_get_drvdata() - get driver private data attached to a SPI mem
216  * @mem: memory device
222 	return mem->drvpriv;  in spi_mem_get_drvdata()
226  * struct spi_controller_mem_ops - SPI memory operations
227  * @adjust_op_size: shrink the data xfer of an operation to match controller's
230  * @supports_op: check if an operation is supported by the controller
231  * @exec_op: execute a SPI memory operation
232  * @get_name: get a custom name for the SPI mem device from the controller.
233  *	      This might be needed if the controller driver has been ported
236  *	      Note that if the implementation of this function allocates memory
238  *	      have a ->free_name() function.
240  *		   access the memory device. This method is optional
241  * @dirmap_destroy: destroy a memory descriptor previous created by
242  *		    ->dirmap_create()
243  * @dirmap_read: read data from the memory device using the direct mapping
244  *		 created by ->dirmap_create(). The function can return less
249  * @dirmap_write: write data to the memory device using the direct mapping
250  *		  created by ->dirmap_create(). The function can return less
255  * @poll_status: poll memory device status until (status & mask) == match or
260  * high-level interface to execute SPI memory operation, which is usually the
263  * Note on ->dirmap_{read,write}(): drivers should avoid accessing the direct
265  * SPI mem transaction to finish, and this will make real-time maintainers
291  * struct spi_controller_mem_caps - SPI memory controller capabilities
301 	((ctlr)->mem_caps && (ctlr)->mem_caps->cap)
304  * struct spi_mem_driver - SPI memory driver
306  * @probe: probe a SPI memory. Usually where detection/initialization takes
308  * @remove: remove a SPI memory
315  * SPI controllers know more about the SPI memory they interact with, and
343 	return -ENOTSUPP;  in spi_controller_dma_map_mem_op_data()