• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 467 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.

TAS2563: Make the codec driver work without cpu-dai binding?

Len Hsu2
Intellectual 2440 points
Part Number: TAS2563

Hi team,

I have a customer design-in TAS2563 and have some setting questions.

For now they are loading the codec driver, but because they do not have cpu-dai so they can't work the probe function.

Is there any way that cam Make the codec driver work without cpu-dai binding?

Another question, is the bin file that PPC3 generate only setting for register? 

Or the bin file also set for other setting at the codec?

  • 0
    TI__Guru** 109825 points

    Hi Len,

    Regarding the driver question, I'll have to check this with some colleagues that are on holiday right now. I'll get some feedback as soon as they're back in office.

    Bin file contains all the register settings based on the PPC3 tuning, this includes both the content from "Tuning and Audio Processing" and "Device Control". All the configuration for TAS2563 has to be load on the registers. What do you mean by "other setting at the codec"?

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    TI__Intellectual 2440 points

    Hi Ivan,

    Thanks for your quick reply.

    I think about I got the "only setting on the registers" part.

    Another question, can the customer load the bin file at PPC3 ? Or PPC3 only can load the project file?

    Do we have a reference PPC3 file for TAS2563QFN EVM that can provide to our customer?

    Best Regards,

    Len

  • 0 in reply to Len Hsu2
    TI__Guru** 109825 points

    Hi Len,

    bin file is mean to be used only by the driver on the end system, it cannot be load into PPC3.
    PPC3 can only load project file or cfg script which you can load into the I2C monitor.

    The default PPC3 settings should be able to initialize the device, although the speaker has to be characterized so that speaker protection algorithm is running properly. One way to test the basic functionality of TAS2563 would be to use the ROM mode:

    • ROM mode can be load by going to Device Control panel, then select ROM Mode on the list from the top-right corner, then click on Apply
    • Or you can generate configuration files by End System Integration, then in the Application list select ROM Mode

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    TI__Intellectual 2440 points

    Hi Ivan,

    About "Make the codec driver work without cpu-dai binding" this question, the customer still can't let the driver work.

    So is there any way can let the driver work without cpu-dai binding?

    Best Regards,

    Len

  • +1 in reply to Len Hsu2
    TI__Guru** 109825 points

    HI Len,

    Here is some feedback I've got from the team:

    " 

    Kindly help to confirm the Operation system, Linux?

    Platform?

    For Linux audio Arch, that is alsa, Tas2563 cannot be registered as a independent codec,

    it is only a slave-mode smartpa, whose workings depends on the external clk.

    One more thing, dai means digital audio interface, without cpu-dai binding, system can’t create

    An audio driver node, so tas2563 driver can not work properly.

    "

    Best regards,
    -Ivan Salazar
    Applications Engineer