Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Patrick Lai <plai@codeaurora.org>
Cc: asishb@codeaurora.org, lkasam@codeaurora.org,
	alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	gsantosh@codeaurora.org
Subject: Re: ALSA framework problem: FE disconnected, BE still connected!
Date: Fri, 19 Apr 2013 11:27:22 +0100	[thread overview]
Message-ID: <20130419102722.GT13687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <51705700.8090005@codeaurora.org>


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

On Thu, Apr 18, 2013 at 01:26:40PM -0700, Patrick Lai wrote:
> On 4/18/2013 9:58 AM, Mark Brown wrote:

> >Please submit patches in hte form covered in SubmittingPatches.

> We are not sure if the solution is correct. Change from Kasam will skip

Even if you're not sure it's best to post as a normal patch so if the
patch is a good solution it can be applied.

> the step which trigger stop the hardware and directly call hardware
> free. Is it expected that every driver internally stops the hardware
> before freeing the hardware resource if not stopped?

That seems silly.

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

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



      reply	other threads:[~2013-04-19 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 16:56 ALSA framework problem: FE disconnected, BE still connected! lkasam
2013-04-18 16:58 ` Mark Brown
2013-04-18 20:26   ` Patrick Lai
2013-04-19 10:27     ` Mark Brown [this message]

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=20130419102722.GT13687@opensource.wolfsonmicro.com \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=asishb@codeaurora.org \
    --cc=gsantosh@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    --cc=lkasam@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox