Lines Matching full:chipselect

44  * - MMC depends on a different chipselect management policy than the
46  *   to issue multiple spi_message requests with the chipselect active,
52  * - We tell the controller to keep the chipselect active from the
56  *   However, many cards seem OK with chipselect flapping up/down
141 	/* chipselect will always be inactive after setup() */  in mmc_cs_off()
385 	/* disable chipselect on errors and some success cases */  in mmc_spi_response_get()
483 	/* send command, leaving chipselect active */  in mmc_spi_command_send()
500 	/* after no-data commands and STOP_TRANSMISSION, chipselect off */  in mmc_spi_command_send()
685  * before dropping chipselect.
992 	 * Do a burst with chipselect active-high.  We need to do this to  in mmc_spi_initsequence()
993 	 * meet the requirement of 74 clock cycles with both chipselect  in mmc_spi_initsequence()
1001 	 * SPI protocol.  Another is that when chipselect is released while  in mmc_spi_initsequence()
1003 	 * with chipselect high before the card will stop driving its output.  in mmc_spi_initsequence()
1077 		 *   - Chipselect is usually active low...  in mmc_spi_set_ios()
1096 			 * chipselect should be low (it is active low)  in mmc_spi_set_ios()
1099 			 * FIXME no, chipselect can be high since the  in mmc_spi_set_ios()