134 		LOG_ERR("invalid direction: %d", dir);  in sai_get_properties()
149  *	3) What this piece of code does is it makes the SYNC direction
150  *	use the ASYNC direction's BCLK that comes from its input pad.
178  *	direction will have the BYP bit toggled.
271 	 * the direction (TX/RX) we're enabling. Enabling the  in sai_config_set()
272 	 * data line for the opposite direction will lead to FIFO  in sai_config_set()
273 	 * overrun/underrun when working with a SYNC direction.  in sai_config_set()
277 	 * which one configures both direction but only starts  in sai_config_set()
278 	 * the SYNC direction which would lead to a FIFO underrun.  in sai_config_set()
463 	 * here as they do not disable the ASYNC direction.  in sai_dir_disable()
464 	 * Since the software logic assures that the ASYNC direction  in sai_dir_disable()
465 	 * is not disabled before the SYNC direction, we can force  in sai_dir_disable()
466 	 * the disablement of the given direction.  in sai_dir_disable()
550 		LOG_ERR("invalid direction: %d", dir);  in sai_trigger_pause()
562 	LOG_DBG("pause on direction %d", dir);  in sai_trigger_pause()
591 		LOG_ERR("invalid direction: %d", dir);  in sai_trigger_stop()
603 	LOG_DBG("stop on direction %d", dir);  in sai_trigger_stop()
639  *	SYNC and ASYNC for each direction. As such, there are 4 possible combinations
651  *		a) The target direction. This is the direction on which we want to perform the
653  *		b) The SYNC direction. This is, well, the direction that's in SYNC with the other
654  *		direction.
655  *		c) The ASYNC direction.
657  *	Of course, the target direction may differ from the SYNC or ASYNC directions, but it
660  *	If the target direction is the same as the SYNC direction then we can safely perform the
661  *	software reset on the target direction as there's nothing depending on it. We also want
662  *	to do a software reset on the ASYNC direction. We can only do this if the ASYNC direction
665  *	If the target direction is the same as the ASYNC direction then we can only perform a
666  *	software reset on it only if the SYNC direction wasn't software enabled (i.e: through an
677 		 * software reset only on the targeted direction.  in sai_tx_rx_sw_reset()
712 		LOG_ERR("invalid direction: %d", dir);  in sai_trigger_start()
733 	LOG_DBG("start on direction %d", dir);  in sai_trigger_start()
763 	 * TODO: for now we only support 1 data line per direction.  in sai_trigger_start()