Re: [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock

2019-03-18 Thread Jiada Wang
Hi Fabrizio On 2019/03/14 3:19, Fabrizio Castro wrote: Hello Jiada, From: Jiada Wang Sent: 13 March 2019 11:56 Subject: Re: [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock Hi Geert On 2019/03/12 18:15, Geert Uytterhoeven wrote: Hi Jiada, Fabrizio, On Thu, Mar 7

RE: [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock

2019-03-13 Thread Fabrizio Castro
Hello Jiada, > From: Jiada Wang > Sent: 13 March 2019 11:56 > Subject: Re: [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential > deadlock > > Hi Geert > > On 2019/03/12 18:15, Geert Uytterhoeven wrote: > > Hi Jiada, Fabrizio, > > > > On Thu

Re: [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock

2019-03-13 Thread Jiada Wang
Hi Geert On 2019/03/12 18:15, Geert Uytterhoeven wrote: Hi Jiada, Fabrizio, On Thu, Mar 7, 2019 at 7:17 AM Jiada Wang wrote: lockdep warns us that priv->lock and k->k_lock can cause a deadlock when after acquire of k->k_lock, process is interrupted by src, while in another routine of src

Re: [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock

2019-03-12 Thread Geert Uytterhoeven
Hi Jiada, Fabrizio, On Thu, Mar 7, 2019 at 7:17 AM Jiada Wang wrote: > lockdep warns us that priv->lock and k->k_lock can cause a > deadlock when after acquire of k->k_lock, process is interrupted > by src, while in another routine of src .init, k->k_lock is > acquired with priv->lock held. > >

[PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock

2019-03-06 Thread Jiada Wang
lockdep warns us that priv->lock and k->k_lock can cause a deadlock when after acquire of k->k_lock, process is interrupted by src, while in another routine of src .init, k->k_lock is acquired with priv->lock held. This patch avoids a potential deadlock by not calling soc_device_match() in SRC