• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 552 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.

DM8168 HDMI audio channel status bits

StuJ
Prodigy 210 points

In our application, we supply the DM8168 HDMI wrapper's audio FIFO with 16bit/sample PCM data, encoded at 48KHz.  I understand the HDMI core converts this data to  IEC 61937/IEC 60958 format prior to transmission to the sink.  I've noticed that the 60958 channel status bits indicate the sample rate to be 44.1KHz instead.  Our values for TMDS = 148500, N = 6144, CTS = 148500.  

How can I configure the HDMI core to generate channel status bits indicating the correct 48KHz sample rate?

Thanks,

Stu

  • 0
    TI__Intellectual 925 points

    Stu,

    We have  done some critical bug fixes and code cleanup for the HDMI audio on the latest PSP release. You can find the patches from the arago tree. I hope these patches will solve the issue.

    http://arago-project.org/git/projects/?p=linux-omap3.git;a=shortlog;h=refs/heads/ti81xx-master

    Please apply the following patches or try with the latest codes from the arago tree

    2012-12-05 sujith TI81XX: HDMI - Changeing the scan type to UNDER_SCAN.
    2012-12-05 sujith TI81xx - Including the header for types.
    2012-12-05 sujith TI81XX - HDMI Updates/bug fix.
    2012-12-05 Raj, Deepu TI81XX: HDMI audio bug fixes and code cleanup
    2012-12-05  sujith TI81XX:  HDMI - EDID parsing features updates
    2012-12-05 sujith TI81xx HDMI - Misc comment updates
    2012-12-05 sujith TI81xx : HDMI : Bug fix - msleep / mutual exclusion...

    Please try with the above patches and let me know the issue is solved or not.

    Regards,

    Deepu Raj

  • 0 in reply to Deepu Raj
    Prodigy 210 points

    The latest PSP does include the fix for this issue.  It's working much better now.

    Thanks!