On Thu, Jan 15, 2015 at 01:40:49PM +0900, jiwang wrote:
> Can we have a more generic fix to this issue?
> Or shall we set owner field for all machine drivers?
Ideally we should do both.
signature.asc
Description: Digital signature
At Wed, 14 Jan 2015 16:34:15 +,
Mark Brown wrote:
>
> 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
>
At Thu, 15 Jan 2015 13:40:49 +0900,
jiwang wrote:
>
> Hi
> On 01/14/2015 10:43 PM, Fabio Estevam wrote:
> > On Wed, Jan 14, 2015 at 10:57 AM, Lars-Peter Clausen
> > wrote:
> >
> >> My personal opinion on this is that disallowing module removal while a
> >> driver registered by the module when is
Hi
On 01/14/2015 10:43 PM, Fabio Estevam wrote:
On Wed, Jan 14, 2015 at 10:57 AM, Lars-Peter Clausen 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. Whe
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
> Hm
On Wed, Jan 14, 2015 at 10:57 AM, Lars-Peter Clausen 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
At Wed, 14 Jan 2015 13:57:03 +0100,
Lars-Peter Clausen wrote:
>
> On 01/14/2015 01:02 PM, Mark Brown wrote:
> [...]
> >>> I don't think that we need to prevent module unload when a stream is
> >>> active.
> >>> From a framework point of view is not different from hot-unplug. I don't
> >>> see a
At Wed, 14 Jan 2015 12:02:28 +,
Mark Brown wrote:
>
> On Wed, Jan 14, 2015 at 11:50:48AM +0100, Takashi Iwai wrote:
> > Lars-Peter Clausen wrote:
>
> > > > OK, so it's not about active stream. From the reporter's description,
> > > > I supposed that the module gets unloaded while playing a s
On 01/14/2015 01:02 PM, Mark Brown wrote:
[...]
I don't think that we need to prevent module unload when a stream is active.
From a framework point of view is not different from hot-unplug. I don't
see a reason why we'd jump through hoops to actively forbid removing the
module once it works jus
On Wed, Jan 14, 2015 at 11:50:48AM +0100, Takashi Iwai wrote:
> Lars-Peter Clausen wrote:
> > > OK, so it's not about active stream. From the reporter's description,
> > > I supposed that the module gets unloaded while playing a stream, which
> > > shouldn't be allowed.
> > Well one of the ways
At Wed, 14 Jan 2015 11:00:47 +0100,
Lars-Peter Clausen wrote:
>
> On 01/14/2015 09:47 AM, Takashi Iwai wrote:
> > At Wed, 14 Jan 2015 09:15:36 +0100,
> > Lars-Peter Clausen wrote:
> >>
> >> On 01/14/2015 08:43 AM, Takashi Iwai wrote:
> >>> At Tue, 13 Jan 2015 21:54:12 +,
> >>> Mark Brown wrote
On 01/14/2015 09:47 AM, Takashi Iwai wrote:
At Wed, 14 Jan 2015 09:15:36 +0100,
Lars-Peter Clausen wrote:
On 01/14/2015 08:43 AM, Takashi Iwai wrote:
At Tue, 13 Jan 2015 21:54:12 +,
Mark Brown wrote:
On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
Wang, Jiada (ESD) wrote:
On 01/14/2015 09:25 AM, jiwang wrote:
Hi
On 01/14/2015 05:15 PM, Lars-Peter Clausen wrote:
On 01/14/2015 08:43 AM, Takashi Iwai wrote:
At Tue, 13 Jan 2015 21:54:12 +,
Mark Brown wrote:
On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
Wang, Jiada (ESD) wrote:
I am using i
At Wed, 14 Jan 2015 09:15:36 +0100,
Lars-Peter Clausen wrote:
>
> On 01/14/2015 08:43 AM, Takashi Iwai wrote:
> > At Tue, 13 Jan 2015 21:54:12 +,
> > Mark Brown wrote:
> >>
> >> On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
> >>> Wang, Jiada (ESD) wrote:
> >>
> I am using
Hi
On 01/14/2015 05:15 PM, Lars-Peter Clausen wrote:
On 01/14/2015 08:43 AM, Takashi Iwai wrote:
At Tue, 13 Jan 2015 21:54:12 +,
Mark Brown wrote:
On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
Wang, Jiada (ESD) wrote:
I am using i.MX6Q sabreSD board, which have imx_wm89
On 01/14/2015 08:43 AM, Takashi Iwai wrote:
At Tue, 13 Jan 2015 21:54:12 +,
Mark Brown wrote:
On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
Wang, Jiada (ESD) wrote:
I am using i.MX6Q sabreSD board, which have imx_wm892 machine driver, wm8962
codec and SSI CPU DAI,
I
At Tue, 13 Jan 2015 21:54:12 +,
Mark Brown wrote:
>
> On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
> > Wang, Jiada (ESD) wrote:
>
> > > I am using i.MX6Q sabreSD board, which have imx_wm892 machine driver,
> > > wm8962 codec and SSI CPU DAI,
>
> > > I got Kernel crash when
On Tue, Jan 13, 2015 at 06:24:44PM +0100, Takashi Iwai wrote:
> Wang, Jiada (ESD) wrote:
> > I am using i.MX6Q sabreSD board, which have imx_wm892 machine driver,
> > wm8962 codec and SSI CPU DAI,
> > I got Kernel crash when unloading audio drivers (playback stream is active)
> > modprobe -r snd
At Fri, 9 Jan 2015 11:39:32 +,
Wang, Jiada (ESD) wrote:
>
> Hi Community
>
> I am using i.MX6Q sabreSD board, which have imx_wm892 machine driver, wm8962
> codec and SSI CPU DAI,
>
> I got Kernel crash when unloading audio drivers (playback stream is active)
> modprobe -r snd_soc_imx_wm8962
19 matches
Mail list logo
