btashton commented on pull request #2039: URL: https://github.com/apache/incubator-nuttx/pull/2039#issuecomment-714266238
> So @btashton you want the userspace provide a buffer/FIFO to driver and avoid the memory copy? > > 1. Sensor normally connect through the external bus(I2C, SPI, UART) and never tightly couple with SoC, so I expect the special memory buffer management like GPU/Display/Video isn't required and memory can be always allocated inside kernel. > > 2. We can expose the internal buffer and queue offset to userspace like what fb or alsa driver done. I would rather let @v01d respond, I'm probably speaking too much for him on this. But I think the point is we are moving the buffer from the application to the kernel and by doing that causing this extra copy to happen as well as complicating things like flushing the sensor buffer. IIO has the one-shot via sysfs so I suppose that kind of read would be similar to what exists today, I guess the question is can the driver be optional in that case? ADI and ST both have been involved in the IIO efforts in Linux so there certainly is buy-in for this kind of abstraction from companies who really care. I have only used it in the context of some of the ADI RF frontends. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
