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.

TAS2572: Driver code for Qualcomm platform

Part Number: TAS2572

Hi Team,

Please help to provide driver code for Qualcomm platform. Thanks.

 

Best regards,

Terry

  • Hi,

    Our team will take a look at your questions and get back with further comments this week after the holiday on Monday.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • Hi Terry

    Let me know the Operating System, windows, Linux, Android or baremetal?

    If Linux or Android, pls specify the kernel version.

  • Hi Shenghao,

    Operating system is Android 16. The Linux kernel version should be 6.12.

    Thanks.

    Best regards,

    Terry

  • https://tidrive.ext.ti.com/u/5g4bRLOOGyD0DhtI/44a3f155-a8d4-46c0-9cb0-73aa25487dc3?l

    access code: 83XV|Duj

    code: 6.12.55.7z

    Guideline: Guideline for Audio AMP Linux driver porting.pdf

  • Hi Shenghao,

    Our platform is Qualcom SW6100, a new wearable SOC. The TAS2572 is connect to the LPI(low power island) side. The application core control the SmartPA through AHB bus. Then the DSP control SmartPA through the I2C port. We need drivers compatible with Qualcomm architecture. 

  • the DSP control SmartPA through

    Do you mean the driver is not the linux driver, but the baremetal driver?

  • Hi Shenghao

    It's Linux driver. But the driver can't control the I2C directory. The driver should read/write the SmartPA's registers through AHB bus.  The bus connect all the cores in the SOC.

    Has the TAS2572 or similar module been integrated on Qualcomm platform. Qualcomm's mobile phone platform has always been based on this architecture. 

    Below is abstract from Qualcomm documents

    Registers in the digital codec are programmed using the AHB bus from APSS
    Registers in the analog codec are programmed using the SoundWire interface and AHB bus from APSS

  • Where will the target driver run on, dsp or AP?

  • Dear Shenghao

    I believe the driver is run on the AP. A case has been submitted to Qualcomm for bringing up 3rd smart PA. I will update the description from Qualcomm as far as possible.

    By the way. Have any of your other customers used this smart PA on Qualcomm platform?

  • We have many QCom Cases on Mobile phone and tablet, but less experience on QCom Wearable platform. since you believe the driver run on AP, I'm sure that your device will use alsa to control the audio path. 

    As you know, the driver we upstream to the Linux Community use the system API for regsiter RW. Qcom can definitly register the register read/write operations for the i2c bus, which is controlled by DSP, within the Linux system. This way, system functions can also access the DSP-controlled i2c bus, allowing all standard i2c drivers to be ported to this system without modification.

    If Qcom have not work taht way, I think the task for the driver become simple and easy. What you do on the driver code is to replace the register R/W system API with the dsp-based register R/W API.

  • Dear Shenghao,

    We now blocking on the smart PA driver. 

    It reports:

    [ 101.019982][ T1189] tas25xx 12-004b: Direct firmware load for tismartpa_driver_tuning.bin failed with error -2
    [ 101.030457][ T1189] tas25xx 12-004b: Falling back to sysfs fallback for: tismartpa_driver_tuning.bin
    [ 101.049009][ T1189] tas25xx 12-004b: firmware is not ready, tismartpa_driver_tuning.bin
    [ 101.141650][ T1] init: Control message: Could not find 'aidl/vendor.qti.hardware.pal.IPAL/default' for ctl.interface_start from pid: 710 (/system/bin/servicemanager)
    [ 101.157888][ T1189] tas25xx 12-004b: Direct firmware load for tismartpa_driver_tuning.bin failed with error -2
    [ 101.168269][ T1189] tas25xx 12-004b: Falling back to sysfs fallback for: tismartpa_driver_tuning.bin
    [ 101.189007][ T1189] tas25xx 12-004b: firmware is not ready, tismartpa_driver_tuning.bin

    It seems miss the firmware.

    Please help for below:

    How to generate the firmware?

    Does the firmware generator need any Key?

    Where the firmware should be pushed to?

  • Our Software expert has already share the gudieline last Saturday and I found some guy from your team has setup a conf-call every day. Do you want sstill kee this thread?