From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>, Vinod Koul <vinod.koul@intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: PM issue with Intel SST Atom driver
Date: Mon, 24 Apr 2017 09:22:38 -0500 [thread overview]
Message-ID: <d4e73746-40f7-8929-bdc4-5bf54aef982d@linux.intel.com> (raw)
In-Reply-To: <s5hefwib075.wl-tiwai@suse.de>
On 4/24/17 4:54 AM, Takashi Iwai wrote:
> On Mon, 24 Apr 2017 11:52:44 +0200,
> Vinod Koul wrote:
>>
>> On Mon, Apr 24, 2017 at 11:43:47AM +0200, Takashi Iwai wrote:
>>> On Mon, 24 Apr 2017 11:12:14 +0200,
>>> Vinod Koul wrote:
>>>>
>>>> On Mon, Apr 24, 2017 at 11:00:45AM +0200, Takashi Iwai wrote:
>>>>
>>>>> Removing ignore_suspend makes the PM succeeds. But it hits some other
>>>>> ugly kernel bugs.
>>>>
>>>> Okay have you marked .nonatomic = true for the machine DAIs?
>>>
>>> Ah that's it. The patch below seems fixing the PM and the nonatomic
>>> problems. I'm not sure about the nonatomic flag for the compress
>>> stream, though.
>>
>> Well we dont have upstream decoders so it wont be used in this case.
>>
>>> Also I fiddled only with FE. Do we need the same flags for BE? The
>>> others don't look setting like that, so I left so.
>>
>> I dont remember if BE needs or not FE should suffice.
>
> OK then I leave it as is.
>
> When I submit the fix, I should put Cc to stable, and wonder which
> version we assure the nonatomic ops in SST driver. Did the code base
> support nonatomic ops from the beginning?
can we take this opportunity to align all drivers?
The .nonatomic=true is set in all drivers for the BE, except for
cht_bsw_max98090_ti.c
It's either needed for all or not needed for all...
>
>
> thanks,
>
> Takashi
>
>>
>>>
>>>
>>> thanks,
>>>
>>> Takashi
>>>
>>> ---
>>> sound/soc/intel/boards/bytcr_rt5640.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> --- a/sound/soc/intel/boards/bytcr_rt5640.c
>>> +++ b/sound/soc/intel/boards/bytcr_rt5640.c
>>> @@ -646,7 +646,7 @@ static struct snd_soc_dai_link byt_rt564
>>> .codec_dai_name = "snd-soc-dummy-dai",
>>> .codec_name = "snd-soc-dummy",
>>> .platform_name = "sst-mfld-platform",
>>> - .ignore_suspend = 1,
>>> + .nonatomic = true,
>>> .dynamic = 1,
>>> .dpcm_playback = 1,
>>> .dpcm_capture = 1,
>>> @@ -659,7 +659,6 @@ static struct snd_soc_dai_link byt_rt564
>>> .codec_dai_name = "snd-soc-dummy-dai",
>>> .codec_name = "snd-soc-dummy",
>>> .platform_name = "sst-mfld-platform",
>>> - .ignore_suspend = 1,
>>> .nonatomic = true,
>>> .dynamic = 1,
>>> .dpcm_playback = 1,
>>> @@ -672,6 +671,7 @@ static struct snd_soc_dai_link byt_rt564
>>> .codec_dai_name = "snd-soc-dummy-dai",
>>> .codec_name = "snd-soc-dummy",
>>> .platform_name = "sst-mfld-platform",
>>> + .nonatomic = true,
>>> },
>>> /* back ends */
>>> {
>>
>> --
>> ~Vinod
>>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2017-04-24 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 13:42 PM issue with Intel SST Atom driver Takashi Iwai
2017-04-24 5:01 ` Vinod Koul
2017-04-24 7:15 ` Takashi Iwai
2017-04-24 9:00 ` Takashi Iwai
2017-04-24 9:12 ` Vinod Koul
2017-04-24 9:43 ` Takashi Iwai
2017-04-24 9:52 ` Vinod Koul
2017-04-24 9:54 ` Takashi Iwai
2017-04-24 11:02 ` Vinod Koul
2017-04-24 14:22 ` Pierre-Louis Bossart [this message]
2017-04-24 16:27 ` Vinod Koul
2017-04-24 18:32 ` Takashi Iwai
2017-04-25 3:04 ` Vinod Koul
2017-04-24 19:01 ` Pierre-Louis Bossart
2017-04-25 3:06 ` Vinod Koul
2017-04-24 9:09 ` Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4e73746-40f7-8929-bdc4-5bf54aef982d@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox