All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: lrg@ti.com, alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] ASoC: pcm: allow backend hardware to be freed in pause state
Date: Sun, 09 Dec 2012 15:09:34 -0800	[thread overview]
Message-ID: <50C51A2E.80209@codeaurora.org> (raw)
In-Reply-To: <20121209152805.GF6511@opensource.wolfsonmicro.com>

On 12/9/2012 7:28 AM, Mark Brown wrote:
> On Thu, Dec 06, 2012 at 10:39:59AM -0800, Patrick Lai wrote:
>> When front-end PCM session is in paused state, back-end
>> PCM session will be put in paused state as well if given
>> front-end PCM session is the only client of given back-end.
>> Then, application closes front-end PCM session, DPCM
>> framework will not allow back-end enters HW_FREE state
>> so back-end will never get shutdown completely.
>
> I'm not entirely sure what this patch is generated against but it
> doesn't appear to apply to either -next or to v3.7-rc7 - can you check
> and regenerate please?
>

I generated this patch against tag v3.7-rc6. I just did a rebase against 
tag v3.7-rc7. I did not encounter merge error. I will regenerate patch again

Thanks
Patrick

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2012-12-09 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 18:39 [PATCH] ASoC: pcm: allow backend hardware to be freed in pause state Patrick Lai
2012-12-07 13:37 ` Liam Girdwood
2012-12-09 15:28 ` Mark Brown
2012-12-09 23:09   ` Patrick Lai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-12 16:49 Patrick Lai
2012-12-15 14:49 ` Mark Brown
2012-12-20  3:36 Patrick Lai
2012-12-20 10:29 ` Liam Girdwood
2012-12-20 16:00 ` Mark Brown

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=50C51A2E.80209@codeaurora.org \
    --to=plai@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.