From: Keyon <yang.jie@linux.intel.com>
To: Michael Trimarchi <michael@amarulasolutions.com>,
Jie Yang <yang.jie@intel.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
liam.r.girdwood@intel.com
Subject: Re: [PATCH] ASoC: Intel: fix a compiling issue
Date: Thu, 16 Apr 2015 16:17:48 +0800 [thread overview]
Message-ID: <552F702C.9080205@linux.intel.com> (raw)
In-Reply-To: <CAOf5uwnLucwnHgfeaqopcky3Vsbf=RTL_BKT+fr9jNei_bYN2A@mail.gmail.com>
On 2015年04月13日 12:50, Michael Trimarchi wrote:
> Hi
>
> On Apr 13, 2015 4:44 AM, "Jie Yang" <yang.jie@intel.com> wrote:
>> Fix the compiling issue that we don't have snd_soc_suspend/resume()
>> when CONFIG_PM_SLEEP is not defined.
>>
>> Signed-off-by: Jie Yang <yang.jie@intel.com>
>> ---
>> sound/soc/intel/haswell/sst-haswell-pcm.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/sound/soc/intel/haswell/sst-haswell-pcm.c
> b/sound/soc/intel/haswell/sst-haswell-pcm.c
>> index 23ae040..f84eb14 100644
>> --- a/sound/soc/intel/haswell/sst-haswell-pcm.c
>> +++ b/sound/soc/intel/haswell/sst-haswell-pcm.c
>> @@ -1313,8 +1313,9 @@ static void hsw_pcm_complete(struct device *dev)
>> dev_err(dev, "failed to restore context for PCM
> %d\n", i);
>> }
>>
>> +#ifdef CONFIG_PM_SLEEP
>> snd_soc_resume(pdata->soc_card->dev);
>> -
>> +#endif
> I think it's better to include an empy version for this configuration
>
> Michael
do you mean that adding line such like:
#define snd_soc_resume NULL
we have that in soc-core.c, but only the non-null version is exported.
~Keyon
>
>> err = sst_hsw_dsp_runtime_resume(hsw);
>> if (err < 0)
>> return;
>> @@ -1367,7 +1368,9 @@ static int hsw_pcm_prepare(struct device *dev)
>> sst_hsw_dsp_runtime_sleep(hsw);
>> }
>>
>> +#ifdef CONFIG_PM_SLEEP
>> snd_soc_suspend(pdata->soc_card->dev);
>> +#endif
>> snd_soc_poweroff(pdata->soc_card->dev);
>>
>> pdata->pm_state = HSW_PM_STATE_D3;
>> --
>> 1.9.1
>>
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-04-16 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 2:47 [PATCH] ASoC: Intel: fix a compiling issue Jie Yang
2015-04-13 4:50 ` Michael Trimarchi
2015-04-16 8:17 ` Keyon [this message]
2015-04-18 12:11 ` Mark Brown
2015-04-18 12:19 ` Michael Trimarchi
2015-04-18 17:03 ` Mark Brown
2015-04-19 1:39 ` Jie, Yang
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=552F702C.9080205@linux.intel.com \
--to=yang.jie@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=michael@amarulasolutions.com \
--cc=yang.jie@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