From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH 00/14] SPDIF support Date: Mon, 2 Sep 2013 15:57:22 +0100 Message-ID: <20130902145722.GA12808@n2100.arm.linux.org.uk> References: <20130831123458.GF6617@n2100.arm.linux.org.uk> <52220B9A.9000007@metafoo.de> <20130831191414.GG6617@n2100.arm.linux.org.uk> <20130831193431.GI6617@n2100.arm.linux.org.uk> <20130902144713.GR3084@sirena.org.uk> <20130902145207.GY6617@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from caramon.arm.linux.org.uk (caramon.arm.linux.org.uk [78.32.30.218]) by alsa0.perex.cz (Postfix) with ESMTP id E8C3A26518D for ; Mon, 2 Sep 2013 16:57:35 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20130902145207.GY6617@n2100.arm.linux.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: Thomas Petazzoni , Andrew Lunn , alsa-devel@alsa-project.org, Lars-Peter Clausen , Jason Cooper , Jean-Francois Moine , Takashi Iwai , Liam Girdwood , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth List-Id: alsa-devel@alsa-project.org On Mon, Sep 02, 2013 at 03:52:07PM +0100, Russell King - ARM Linux wrote: > On Mon, Sep 02, 2013 at 03:47:13PM +0100, Mark Brown wrote: > > On Sat, Aug 31, 2013 at 08:34:31PM +0100, Russell King - ARM Linux wrote: > > > And here's the oops: > > > > > Aug 10 22:06:17 cubox kernel: [] (snd_pcm_info+0xc8/0xd8) from [] (snd_pcm_info_user+0x34/0x9c) > > > Aug 10 22:06:17 cubox kernel: [] (snd_pcm_info_user+0x34/0x9c) from [] (snd_pcm_control_ioctl+0x274/0x280) > > > > > This is caused because substream->ops is NULL. Why that's the case, > > > I don't know, but I believe the PCM which is trying to be operated on > > > is the one registered against the backend (by snd_pcm_new_internal). > > > > Liam did provide you with a workaround for this one along with a > > suggested proper fix. Have you had any success in using this > > workaround, or with implementing the proper fix for that matter? I > > don't recall seeing any feedback on the results but perhaps I missed it. > > I am not aware of any such patch. That was a little hasty - I should say: I have not received any such patch and I have nothing which suggests that a solution to this problem was even outlined. (I have checked my mailbox for anything from Liam, of which there are a very small number of such mails.)