-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
data reset during u-dma-buf creation #55
Comments
Thank you for the issue. u-dma-buf will clear the buffer when it is created. What is the purpose of using u-dma-buf? |
Thanks. |
I am using u-dma-buf because I had no caching problems using it. /dev/mem surely is the better fit for my problem but I always have caching issues using it. But if the ram is reset on purpose using udmabuf I will try /dev/mem again. |
Thank you for your reply. If you want to enable caching and access, try uiomem. https://github.com/ikwzm/uiomem/tree/v1.0.0-alpha.1 Prepare the following device tree.
|
Hi,
I would like to use u-dma-buf to transfer data between two processors in an Ultrascale+ platform. The problem is, that one Processor is running much earlier and producing data much earlier than the other processor which is running the Linux OS and uses the u-dma-buf module.
So there is data in the specified memory but during the boot of the Linux OS and the creation of the u-dma-buf it is reset. I am creating the u-dma-buf via a device tree entry nearly identical to the one in the documentation. If i remove the udmabuf node and only leave the reserved-memory node the data remains in the buffer.
Is there a simple solution to this anybody can think of? I tried removing the reusable option but this only results in a kernel panic.
Thanks
The text was updated successfully, but these errors were encountered: