• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 226 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5728: EDMA driver migration

Lawrence Wong
Genius 15770 points
Part Number: AM5728

Customer is in the process of porting a multi-channel audio driver from existing product (AM437x running linux 3.14.26) to the AM57xx running linux 4.14. There seems to be compatibility issues. Their audio driver makes extensive use of the edma engine to efficiently transfer audio data with very minimal processor overhead. The edma engine has changed a lot. Some of the changes are easy to accommodate but some look more involved. For instance, edma_alloc_channel used to take a callback function which was triggered at the end of the transfer, while the new function does not. Even that porting that kind of change to the new kernel looks manageable to customer but before they embark on a ton of work they wanted to know if the edma code is still expected to work (going from 3.14.26 to 4.14)? They are curious as to why it was changed so much?

  • 0
    TI__Mastermind 44585 points

    Hi Lawrence,

    During a given year, TI’s LTS version migration only happens once per year and it occurs towards the end of the second quarter. The LTS migration usually signifies newer version of Kernel, U-boot, Toolchain, Yocto Project and etc. Depending on the Kernel version, new functions could be introduced and it would require driver update. Please have the customer run the command "git log" in the <kernl_dir>/drivers/dma/ti folder to get a history of the changes.

    Looking at our document for known issues, I do not see any known bugs with the driver. I am wondering if there is any specific feature that the customer is concerned about

    Regards,
    Krunal