This repository has been archived by the owner on May 18, 2022. It is now read-only.
forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ASoC: SOF: partition audio-specific parts from the SOF core
This patch makes elaborate changes to the SOF core device structure and IPC RX/TX. At the high-level, the changes fall into 3 main categories: Audio-related members in the struct snd_sof_dev: These are now partiioned into struct sof_audio_dev that is created , maintained and used by the audio client. Along with these, all the other topology related structs for such as snd_sof_widget, snd_sof_route etc have all been moved to sof-audio.h. The snd_sof_dev member in all the topology related structs has been replaced with a member that represents the component driver that creates the topology. The sof_audio_dev handle that is created by the audio client is stored as private data in the MFD client struct but the core should never touch this. IPC TX/RX for MFD clients: IPC TX/RX for MFD clients can be performed by calling the sof_client_tx_message() API. If the clients want to receive IPC's from the DSP, they should register for the type of IPC's they'd like to receive. Audio-specific PM sequence: Previously, when the PCI device was resumed, the topology was reconstructed in its resume callback. But this will now be handled by the audio client device's resume callback. Also, the audio client's suspend callback should handle suspending streams. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
- Loading branch information
Showing
17 changed files
with
1,299 additions
and
1,121 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.