[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150114163415.GV4160@sirena.org.uk>
Date: Wed, 14 Jan 2015 16:34:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Takashi Iwai <tiwai@...e.de>
Cc: Lars-Peter Clausen <lars@...afoo.de>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"Wang, Jiada (ESD)" <Jiada_Wang@...tor.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"Frkuska, Joshua" <Joshua_Frkuska@...tor.com>
Subject: Re: [alsa-devel] unload Audio drivers while playback stream is
active case kernel crash
On Wed, Jan 14, 2015 at 02:01:33PM +0100, Takashi Iwai wrote:
> Mark Brown wrote:
> > > Above all, disallowing the module unload while using is the common
> > > behavior of any other drivers. Why do we have to be a rebel against
> > > all civil manner? :)
> > That's not true for everything
> Hmm, which driver does behave so intentionally? I'm interested in the
> supposed reason behind it.
Relatively few of the subsystems in drivers have references to
module_get().
> > and for ASoC I'd tend to assume that the
> > user knows what they're doing and has a good reason for it; it's
> > certainly something that can be helpful in development.
> The module unload is never considered to be equivalent with hot
> unplug It's more than that.
I'm not sure that's the case from a user perspective.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists