• Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 501 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.

About keystone udma driver

user4626994
Prodigy 60 points

Hi,

This is my first contact to e2e site where is suitable place?
I would like to request review my Linux keystone driver patches.

We recently saw some linux driver's side problems around keystone DSP.
I hear that problems were unfortunately invited DSP processor crash,
stopping our system services as a result.
We have to make more stable by the middle of this month.

Now, the DSP quality improvement tasks are raised to highest priority
activities to catch up schedule delay of our system service in.

That's why, I've started to trace current keystone drivers source code
in terms of linux, exclusive or resource management implementations.
(Now is only source trace. I am going to get target board around May)

I tried to make and attach patches as below.
  dma: keystone: optimize the udma lock implementation
  dma: keystone: change the type of udma_lock to mutex
  dma: keystone: Fix potential invalid reference to udma device pointer
  dma: keystone: Fix wrong instantiation and termination on udma-chan
  dma: keystone: make sense: the way of atomic list traversing

[Target archive: md5sum]
 9d4a3afebece61a46fc5bd948f34cdbc *mcsdk-3_01_04_07.arago.src.tar.gz

I would like to be reviewed them by keystone DSP linux driver's experts,
and gets any useful technical advices or comments.
And more (if possible), pick some of them to apply from next mcsdk version.

If some of my patches are confirmed in e2e here, we can apply or verify them
on our target system.

Best regards,
Toshikazu Nakayama.3323.udma-patches.zip

  • TI__Guru* 81335 points

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com). Please read all the links below my signature.

    We will get back to you on the above query shortly. Thank you for your patience.

    Thank you.

    PS: We strongly recommend you to create new e2e thread for your queries instead of following up on an old/closed e2e thread, new threads gets more attention than old threads and can provide link of old threads or information on the new post for clarity and faster response.

  • in reply to Raja
    TI__Guru 50170 points

    Hi, Toshikazu,

    Could you elaborate more details about the failure sympton and what application/test was running at the time of system crash? Was the test done on a TI EVM and what device is it? Without knowing the issue, we can only walk through the files and see if there is anything trivial.

    Rex

  • in reply to Rex Chang
    Prodigy 60 points

    Hi, Rex.

    Thanks for your suggestion but I can not test about my report problems yet.

    I am going to investigate them shortly after. And, if I can reproduce problem,

    I'll send additional report problem with their test case or environment information.

    Thanks a lot,

    Toshikazu