# SPDX-License-Identifier: GPL-2.0-only # # Industrial I/O generic buffer implementations # # When adding new entries keep the list in alphabetical order config [31mCONFIG_IIO_BUFFER_CB[0m tristate "IIO callback buffer used for push in-kernel interfaces" help Should be selected by any drivers that do in-kernel push usage. That is, those where the data is pushed to the consumer. config [31mCONFIG_IIO_BUFFER_DMA[0m tristate help Provides the generic [31mCONFIG_IIO[0m DMA buffer infrastructure that can be used by drivers for devices with DMA support to implement the [31mCONFIG_IIO[0m buffer. Should be selected by drivers that want to use the generic DMA buffer infrastructure. config [31mCONFIG_IIO_BUFFER_DMAENGINE[0m tristate select [31mCONFIG_IIO_BUFFER_DMA[0m help Provides a bonding of the generic [31mCONFIG_IIO[0m DMA buffer infrastructure with the DMAengine framework. This can be used by converter drivers with a DMA port connected to an external DMA controller which is supported by the DMAengine framework. Should be selected by drivers that want to use this functionality. config [31mCONFIG_IIO_BUFFER_HW_CONSUMER[0m tristate "Industrial I/O HW buffering" help Provides a way to bonding when an [31mCONFIG_IIO[0m device has a direct connection to another device in hardware. In this case buffers for data transfers are handled by hardware. Should be selected by drivers that want to use the generic Hw consumer interface. config [31mCONFIG_IIO_KFIFO_BUF[0m tristate "Industrial I/O buffering based on kfifo" help [31mCONFIG_A[0m simple fifo based on kfifo. Note that this currently provides no buffer events so it is up to userspace to work out how often to read from the buffer. config [31mCONFIG_IIO_TRIGGERED_BUFFER[0m tristate select [31mCONFIG_IIO_TRIGGER[0m select [31mCONFIG_IIO_KFIFO_BUF[0m help Provides helper functions for setting up triggered buffers. |