From: jiwang <jiada_wang@mentor.com>
To: Fabio Estevam <festevam@gmail.com>, Lars-Peter Clausen <lars@metafoo.de>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Frkuska, Joshua" <Joshua_Frkuska@mentor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: [alsa-devel] unload Audio drivers while playback stream is active case kernel crash
Date: Thu, 15 Jan 2015 13:40:49 +0900 [thread overview]
Message-ID: <54B744D1.3040809@mentor.com> (raw)
In-Reply-To: <CAOMZO5AQEyb9in0hRn+7zcpE5r8zwVUFjCqAqNOmLMCGYka3Pg@mail.gmail.com>
Hi
On 01/14/2015 10:43 PM, Fabio Estevam wrote:
> On Wed, Jan 14, 2015 at 10:57 AM, Lars-Peter Clausen <lars@metafoo.de> wrote:
>
>> My personal opinion on this is that disallowing module removal while a
>> driver registered by the module when is in use, while there is no technical
>> reason to do so, is a anti-feature. Whether in ALSA or elsewhere.
>>
>> But looking at the source it seems that this is a core feature of ALSA and
>> at least for the card module itself it will do the ref-counting when a
>> stream is started/stopped. And we even support setting the owner of a card
>> in ASoC. It's just that pretty much no ASoC card driver bothers to set the
>> owner field in the snd_soc_card struct. So this particular problem can be
>> fixed by updating the imx-wm8962 driver to set the owner field.
> Thanks, Lars_Peter. This fixes the issue:
>
> root@freescale /$ modprobe -r snd_soc_imx_wm8962
> modprobe: can't unload module snd_soc_imx_wm8962: Resource temporarily
> unavailable
>
> Will send a patch with your suggestion soon.
I think by set owner field in imx_wm8962 machine driver can fix the
crash I saw on sabreSD board,
but as this is a generic issue which I suppose should exist on other
boards with different
machine drivers.
Can we have a more generic fix to this issue?
Or shall we set owner field for all machine drivers?
Thanks,
Jiada
next prev parent reply other threads:[~2015-01-15 4:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 11:39 unload Audio drivers while playback stream is active case kernel crash Wang, Jiada (ESD)
2015-01-13 17:24 ` Takashi Iwai
2015-01-13 21:54 ` [alsa-devel] " Mark Brown
2015-01-14 7:43 ` Takashi Iwai
2015-01-14 8:15 ` Lars-Peter Clausen
2015-01-14 8:25 ` jiwang
2015-01-14 9:34 ` Lars-Peter Clausen
2015-01-14 8:47 ` [alsa-devel] " Takashi Iwai
2015-01-14 10:00 ` Lars-Peter Clausen
2015-01-14 10:50 ` [alsa-devel] " Takashi Iwai
2015-01-14 12:02 ` Mark Brown
2015-01-14 12:57 ` Lars-Peter Clausen
2015-01-14 13:06 ` Takashi Iwai
2015-01-14 13:43 ` [alsa-devel] " Fabio Estevam
2015-01-15 4:40 ` jiwang [this message]
2015-01-15 6:14 ` Takashi Iwai
2015-01-15 10:52 ` [alsa-devel] " Mark Brown
2015-01-14 13:01 ` Takashi Iwai
2015-01-14 16:34 ` Mark Brown
2015-01-15 6:21 ` Takashi Iwai
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=54B744D1.3040809@mentor.com \
--to=jiada_wang@mentor.com \
--cc=Joshua_Frkuska@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).