On Wed, 3 Oct 2018 08:47:00 -0700 David Frey <dpfrey@xxxxxxxxx> wrote: > Hi, > > I have noticed that CONFIG_IIO_TRIGGERED_BUFFER doesn't have any > description in Kconfig. I'm not an expert on Kconfig, but I believe > this means that it is not possible to set the config option explicitly > using menuconfig. I see this as a problem because it means that you > can't really build the necessary kernel config to support an out of tree > driver which depends on CONFIG_IIO_TRIGGERED_BUFFER. If I'm wrong about > this, please let me know why. The basic answer is that it's a trade off between presenting more complex options in menuconfig for in kernel drivers and supporting easy out of tree builds. Is it particularly important for your usecase to have your driver built out of tree and is not possible to patch the kernel to allow it if you need to? So basically provide a strong argument for why and lets see what others think about this. Jonathan > > Thanks, > David
