[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70f873a4-5b41-aede-55b5-8a731c892198@amd.com>
Date: Wed, 22 Feb 2023 02:35:55 +0530
From: "Mukunda,Vijendar" <vijendar.mukunda@....com>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
vkoul@...nel.org
Cc: alsa-devel@...a-project.org, amadeuszx.slawinski@...ux.intel.com,
Mario.Limonciello@....com, Sunil-kumar.Dommati@....com,
Basavaraj.Hiregoudar@....com, Mastan.Katragadda@....com,
Arungopal.kondaveeti@....com,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Sanyog Kale <sanyog.r.kale@...el.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V3 3/8] soundwire: amd: register SoundWire manager dai ops
On 21/02/23 21:29, Pierre-Louis Bossart wrote:
>
>
>> +static const struct snd_soc_dai_ops amd_sdw_dai_ops = {
>> + .hw_params = amd_sdw_hw_params,
> don't you need a .prepare to deal with suspend-resume?
DSP based solution is not implemented yet.
As per our understanding In .prepare () callback, there is
no extra logic needs to be implemented. Because of it,
we have dropped .prepare() callback.
>
>> + .hw_free = amd_sdw_hw_free,
>> + .set_stream = amd_pcm_set_sdw_stream,
>> + .get_stream = amd_get_sdw_stream,
>> +};
Powered by blists - more mailing lists