drivers/spi/spi_nxp_lpspi/Kconfig

# Copyright 2018, 2024-2025 NXP
# SPDX-License-Identifier: Apache-2.0

config SPI_NXP_LPSPI
	bool "NXP LPSPI peripheral"
	default y
	depends on DT_HAS_NXP_LPSPI_ENABLED
	depends on CLOCK_CONTROL
	select PINCTRL
	help
	  Enable driver support for NXP LPSPI.

if SPI_NXP_LPSPI

config SPI_NXP_LPSPI_DMA
	bool "NXP LPSPI DMA-based Driver"
	default y
	select DMA
	depends on $(dt_compat_any_has_prop,$(DT_COMPAT_NXP_LPSPI),dmas)
	help
	  Enable DMA-based transfers for LPSPI peripherals
	  that have a dmas property specified in their DT node.
	  The DMA based driver prioritizes bandwidth over latency, due to
	  DMA being more efficient for larger data transfers, to avoid CPU
	  having to be utilized to do the work. However, setting up a DMA
	  transfer is more complicated setup than just starting the transfer
	  immediately with CPU, so there could be more latency between
	  the point of requesting a transfer and when it actually starts.

config SPI_NXP_LPSPI_CPU
	bool "NXP LPSPI CPU-based driver"
	default y
	depends on $(dt_compat_any_not_has_prop,$(DT_COMPAT_NXP_LPSPI),dmas) || !SPI_NXP_LPSPI_DMA
	depends on !SPI_NXP_LPSPI_CPU_RTIO
	help
	  Enable "normal" CPU based SPI driver for LPSPI.
	  This has lower latency than DMA-based driver but over the
	  longer transfers will likely have less bandwidth and use more CPU time.

config SPI_NXP_LPSPI_CPU_RTIO
	bool "NXP LPSPI RTIO-based driver"
	default y
	depends on $(dt_compat_any_not_has_prop,$(DT_COMPAT_NXP_LPSPI),dmas) || !SPI_NXP_LPSPI_DMA
	depends on SPI_RTIO
	help
	  Enable native RTIO-based driver for LPSPI.
	  This driver optimizes latency by starting/resuming transfers directly
	  from the ISR context in a non-blocking and asynchronous fashion. However,
	  it does not include DMA usage.

config SPI_NXP_LPSPI_TXFIFO_WAIT_CYCLES
	int "Number of CPU cycles to wait on TX fifo empty"
	default 0 if DEBUG
	default 10000
	help
	  This option most likely does not need changed.
	  The drivers tend to need to wait on confirming the transmit command
	  is consumed by the hardware by checking of the TX fifo is emptied.
	  This option gives a maximum number of CPU cycles to wait on that check.
	  The special value of 0 means infinite, which can be useful for debugging
	  for if there is some programming error that causes TX fifo not to empty.
	  The default of 10000 is arbitrary.

if SPI_NXP_LPSPI_CPU_RTIO

config SPI_NXP_RTIO_SQ_SIZE
	int "Number of available submission queue entries"
	default 8 # Sensible default that covers most common spi transactions
	help
	  When RTIO is use with SPI each driver holds a context with which blocking
	  API calls use to perform SPI transactions. This queue needs to be as deep
	  as the longest set of spi_buf_sets used, where normal SPI operations are
	  used (equal length buffers). It may need to be slightly deeper where the
	  spi buffer sets for transmit/receive are not always matched equally in
	  length as these are transformed into normal transceives.

endif # SPI_NXP_LPSPI_CPU_RTIO

endif # SPI_NXP_LPSPI