Rework PCM ops callback mechanism

- Fix issues regarding PCM ops callbacks via AVIRT
- As PCMs are created, the PCM ops are set according to the Audio
  Path's needs. A default PCM ops table is applied for all PCMs,
  which includes callbacks such as open, and hw_free, since AVIRT
  requires these for intermediate processing, whether or not a given
  Audio Path may need them.
- Separate PCM ops into separate playback and capture ops tables

Signed-off-by: Mark Farrugia <mark.farrugia@fiberdyne.com.au>

1 files changed, 2 insertions, 1 deletions

diff --git a/dummy/dummy.c b/dummy/dummy.c
index 872ade9..f683b92 100644
--- a/dummy/dummy.c
+++ b/dummy/dummy.c
@@ -272,7 +272,8 @@ static struct snd_avirt_audiopath dummyap_module = {
 	.name = "Dummy Audio Path",
 	.version = { 0, 0, 1 },
 	.hw = &dummyap_hw,
-	.pcm_ops = &dummyap_pcm_ops,
+	.pcm_playback_ops = &dummyap_pcm_ops,
+	.pcm_capture_ops = &dummyap_pcm_ops,
 	.configure = dummy_configure,
 };