From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@kernel.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: Thu, 18 Apr 2013 13:26:40 -0700 [thread overview]
Message-ID: <51705700.8090005@codeaurora.org> (raw)
In-Reply-To: <20130418165844.GN13687@opensource.wolfsonmicro.com>
On 4/18/2013 9:58 AM, Mark Brown wrote:
> On Thu, Apr 18, 2013 at 09:56:25AM -0700, lkasam@codeaurora.org wrote:
>> Hi Liam,
>> We have a problem encountered in ALSA framework wrt FE/BE disconnection and
>> fix to it is mentioned in below code change. please check it and provide
>> your valuable comments.
>
> Please submit patches in hte form covered in SubmittingPatches.
Hi Mark,
We are not sure if the solution is correct. Change from Kasam will skip
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?
Thanks
Patrick
>
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2013-04-18 20:26 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 [this message]
2013-04-19 10:27 ` 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=51705700.8090005@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=asishb@codeaurora.org \
--cc=broonie@kernel.org \
--cc=gsantosh@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=lkasam@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.