TAS2X63EVM: Driver for Linux

Driver code is public via this linking: tas256xsw-android/tas2563-android-driver - Software for TAS256x on Android Platforms - TAS2563 Android Driver (ti.com)

May I collect your project infomation?

1. how many pcs of tas2563?
2. kernel version
3. platform, mtk, qcom or i.mx, etc
4. apci-arch or dt-arch?

Hi,

Please find the details below.

1. how many pcs of tas2563 =>  100000+
2. kernel version  => 5.15.0-67-generic
3. platform, mtk, qcom or i.mx, etc  => INGENIC (Processor: T40)
4. apci-arch or dt-arch?  => MIPS32ISA
   
   Here is the architecture Block of our processor for reference.
   
   
   
   
   The driver link attached in the response is the android driver. We are using embedded linux. Hence we will be needing the driver of TAS2563 for embedded linux.
   
   Please suggest how we should move ahead in such case

Best regards,

Mukesh Prajapati

Hi Mukesh

1. how many pcs of tas2563 =>  100000+ I means how many pieces of tas2563 will be deplyed on each device, one, two or four?
2. Both Android and Linux use the same Linux Kernel, their driver code is no difference. Only difference is in the framework and application. As to driver, the difference is how to register the sound card into system. 
3. What kind issue have met when you integrated our driver into your platform.

1.Each device will have one amplifier.

2.The link below has many options for drivers. Which link or zip amplifier driver file should we use in our embedded linux application on ingenic platform?

https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/

Stereo branch and set mono in dts file

Hi,

Can you please share the user sample code how to access the tas2563 linux driver on linux platform.

Thanks

There's a set of audio test tools in Linux. You can use these tools to verify the driver, such as amixer, aplay, etc.

set platform i2s first

amixer “Configuration” 0/1/2, etc

aplay xxx.wav  

HI,

• As you mentioned in dts we need to define mono, can you explain how can we do the same because in the dts which is here: https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/tree/dts.readme, there is no such parameters in the same.
• we did generated the files using end system integration user guide, we would like to know where we need to save the files such as .bin and .ftccg file on device so that driver can load it from there
  
  • Are the files in headers and debug_cfg also needs to be used? if yes then can you let us know where to store these files in device so that driver can use the same and what functionality these two folders provides?

Hi, 

The code you use in only for mono. You won't define mono in dts.

For bin file, you will compile into image or copy into /lib/firmware

We may as well have a quick conf-call tomorrow. My email is shenghao-ding@ti.com

Looking forward to your feedback.

BR

Shenghao Ding

HI,

Have sent you an email about the same.

Hi,

Do we need to add the function of the Optional features like IV Sense, BOOST MODE, Brownout Detection in the Linux separately or the Linux Driver will all the function to control all the registers which is mentioned in the data sheet? 

All have done in the tas2563 driver and its dsp.

How can we call those function or what are the commands for set the value ? (i.e : I want to set Brownout Value and Enable BOOST Mode).

Set the brownout and boost registers.

You can find the data sheet in this link: TAS2563 data sheet, product information and support | TI.com

Hi Shenghao,

we wanted to check if we have two equaliser profiles, is that mean that there will be two binary files will be generated? if thats the case how can we switch among these profiles in run time without restarting the amplifier using linux driver, as from driver documents it looks like it load the bin file when the device is boot up, how we switch in run time these profiles?

Only one binary file, one binary file can store multiple eq profiles.

In alsa, the switching is via kcontrol. Our current tas2563 driver has already done this.

amixer cset numid=6,iface=MIXER,name='Configuration' 1

See tas2563-codec.c, following kcontrols,Configuration and Program Kcontrols are for firmware.

static const struct snd_kcontrol_new tas2563_snd_controls[] = {
	SOC_SINGLE_TLV("Amp Output Level", TAS2563_PlaybackConfigurationReg0,
		0, 0x16, 0,
		tas2563_digital_tlv),
	SOC_SINGLE_EXT("Program", SND_SOC_NOPM, 0, 0x00FF, 0, 
		tas2563_program_get, tas2563_program_put),
	SOC_SINGLE_EXT("Configuration", SND_SOC_NOPM, 0, 0x00FF, 0,
		tas2563_configuration_get, tas2563_configuration_put),
	SOC_SINGLE_EXT("Calibration", SND_SOC_NOPM, 0, 0x00FF, 0,
		tas2563_calibration_get, tas2563_calibration_put),
	SOC_ENUM_EXT("VBoost Ctrl", vboost_ctl_enum[0],
		tas2563_vboost_ctl_get, tas2563_vboost_ctl_put),
	SOC_ENUM_EXT("Pdm switch Ctrl", pdm_ctl_enum[0],
		tas2563_pdm_ctl_get, tas2563_pdm_ctl_put),
};

Hi Shenghao,

What is the delay when we switch from one profile to another on the tas2563 chip?

Before profile-switching, power off the adio path first. The delay depend on the i2c bitrate and the qty of dsp paramters, for 400kHz, about 60~100ms (the data is test in audio framework, including CPU scheduling).

We have another way to save the EQ params and dsp firmware, that is save as array, and save it into the header file. This method is widely used in the platform without filesystem. The array can be made by PPC3. Maybe it is easy for you to handle.

do you mean there should not be any signal played while switching or we need to reset the audio amplifier before profile switch?