You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Topology: Need to manage multiple configurations per DAI #697
We need the ability to expose multiple configurations per DAI in the topology file, and means for the driver to pass the relevant configuration over IPC to the firmware.
One example is support for 8 or 16 kHz for a Bluetooth HFP link.
this was filed initially as thesofproject/soft#11. Making sure this is tracked at the kernel level as well.
Interesting issue. I'm not quite sure what change in kernel driver is required at this moment, but I will review at full stacks, driver/topology files/firmware. I will come up with the solution.
@fredoh9 ASoC topology supports this already but is likely untested. You will need too
Driver
Write a simple topology with one DAI that has 2 or more configs.
Make sure the alsatplg compiler adds both configs in the binary file.
make sure sound/soc/topology.c parses both DAI configs.
Make sure sound/soc/sof/topology.c parses both configs and send IPC for both configs.
Firmware
FW should receive both configs and add to dai.c (only one supported today, we can have a list of configs)
By default FW will use config 0. @keyonjie is working on logic to select the best config based on stream params and topology. We may also need to add a manual config selection method too.
@wenqingfu Actually #758 simply acknowledges the presence of multiple configs but adds an additional check for the assigned default hardware configuration and chooses that one to be send to the firmware. I think it is more work involved with this issues than just that. And based on @lgirdwood 's notes above, all the hardware configs should eventually be sent to the firmware via IPC, but first the firmware would need some reworks to allow handling multiple configurations on the same DAI.
Activity
fredoh9 commentedon Mar 22, 2019
Interesting issue. I'm not quite sure what change in kernel driver is required at this moment, but I will review at full stacks, driver/topology files/firmware. I will come up with the solution.
lgirdwood commentedon Mar 22, 2019
@fredoh9 ASoC topology supports this already but is likely untested. You will need too
Driver
Firmware
fredoh9 commentedon Mar 23, 2019
@lgirdwood wow, thank you for detailed guideline. Will work on it.
wenqingfu commentedon Mar 28, 2019
@fredoh9 #758 may close this ticket
dragosht commentedon Mar 29, 2019
@wenqingfu Actually #758 simply acknowledges the presence of multiple configs but adds an additional check for the assigned default hardware configuration and chooses that one to be send to the firmware. I think it is more work involved with this issues than just that. And based on @lgirdwood 's notes above, all the hardware configs should eventually be sent to the firmware via IPC, but first the firmware would need some reworks to allow handling multiple configurations on the same DAI.
plbossart commentedon Jun 16, 2021
we have a multi-configuration support for SSP, let's close this.
jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal …