All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH] ASoC: pcm: allow backend hardware to be freed in pause state
Date: Sat, 15 Dec 2012 23:49:53 +0900	[thread overview]
Message-ID: <20121215144952.GD22033@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1355330980-25189-1-git-send-email-plai@codeaurora.org>


[-- Attachment #1.1: Type: text/plain, Size: 1112 bytes --]

On Wed, Dec 12, 2012 at 08:49:40AM -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.

This still doesn't apply against mainline, applying to v3.7 gives:

$ git am -3 --signoff /tmp/fnord
Applying: ASoC: pcm: allow backend hardware to be freed in pause state
Using index info to reconstruct a base tree...
error: patch failed: sound/soc/soc-pcm.c:1240
error: sound/soc/soc-pcm.c: patch does not apply
Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Cannot fall back to three-way merge.
Patch failed at 0001 ASoC: pcm: allow backend hardware to be freed in pause state

I can't see what's wrong but that's making me worry about applying it
by hand as it seems likely that there's some aspect of it thatd' be
missed; the plain patch program also has similar issues.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-12-15 14:49 UTC|newest]

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

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=20121215144952.GD22033@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=plai@codeaurora.org \
    /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.