Lines Matching refs:to

5 Running CAIF over SPI needs some extra setup, owing to the nature of SPI.
6 Two extra GPIOs have been added in order to negotiate the transfers
9 Please note that running as a slave implies that you need to keep up
18 SPI slave device part, which is the module that you have to write if
19 you want to run SPI CAIF on a new hardware. This part takes care of
20 the physical hardware, both with regard to SPI and to GPIOs.
26 	In order to implement a SPI device you will, as a minimum,
27 	need to implement the following
32 	This function is called by the CAIF SPI interface to give
33 	you a chance to set up your hardware to be ready to receive
37 	to map to different CAIF SPI slave devices.
42 	(SPI_INT) GPIO needs to change state. The boolean value of the xfer
44 	deasserted (LOW). The dev parameter can be used to map to different CAIF
51 	This function is called by the CAIF SPI slave device in order to
52 	signal a change of state of the input GPIO (SS) to the interface.
53 	Only active edges are mandatory to be reported.
55 	not to introduce latency). The ifc parameter should be the pointer
60 	This function is called by the CAIF SPI slave device in order to
64 	not to introduce latency). The ifc parameter should be the pointer
72 		Indicate clock speed (used to calculate toggle delays).
75 		Assign your private data (can be used to map to your structure).
78 		Add name of driver to connect to ("cfspi_sspi").
83 In order to optimize throughput, a number of SPI padding options are provided.
86 The padding needs to be correctly configured on both sides of the link.
119 	/* You only need to trigger on an edge to the active state of the
121 	 * called with the parameter assert set to true. It is OK
122 	 * (and even advised) to call the ss_cb() function in IRQ context in
123 	 * order not to add any delay. */
131 	 * in something similar to this. The only thing you need to
132 	 * do is to call the xfer_done_cb() function, providing the pointer
133 	 * to the CAIF SPI interface. It is OK to call this function
140 	 * set up your DMA here and make sure that you are ready to
152 	/* If xfer is true then you should assert the SPI_INT to indicate to
153 	 * the master that you are ready to receive the data from the master
154 	 * SPI. If xfer is false then you should de-assert SPI_INT to indicate
195 		printk(KERN_WARNING "sspi_init: failed to register dev.\n");