From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752941AbcHOLm3 (ORCPT ); Mon, 15 Aug 2016 07:42:29 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:60134 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752563AbcHOLm1 (ORCPT ); Mon, 15 Aug 2016 07:42:27 -0400 Date: Mon, 15 Aug 2016 12:42:11 +0100 From: Mark Brown To: wens Tsai Cc: Maxime Ripard , Liam Girdwood , Code Kipper , Linux-ALSA , linux-arm-kernel , linux-kernel Message-ID: <20160815114211.GI9347@sirena.org.uk> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SR0DFWOzPg+ymaCV" Content-Disposition: inline In-Reply-To: X-Cookie: I can't drive 55. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: ASoC: sun4i-codec: playback stall and I/O error with DAPM paths all disabled X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --SR0DFWOzPg+ymaCV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Aug 15, 2016 at 05:43:55PM +0800, wens Tsai wrote: > What is unexpected is any attempt to play anything under this state makes > the playback software (in my case mpg321) stall, and later report an I/O > error. My guess is that the DAC is still disabled by DAPM, so it doesn't > send any DRQs, and thus the DMA engine is not consuming any data from > userspace. This is normal for ASoC - like you say it'll be becasue the hardware isn't powered up. > I think we should just enable the digital bits of the DAC/ADC all the > time. Or maybe transfer and then discard data if the DAC is off. Not > sure if this is doable though. I expect playback software to work, and > not block, regardless of the hardware status. Powering things up all the time will have a major effect on battery life for systems that care about that. The expectation is that systems with this sort of hardware won't normally be offering end users direct control of the routing, it'll be something that's handled during system integration. --SR0DFWOzPg+ymaCV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXsaqSAAoJECTWi3JdVIfQi4AH/jWqPscNLFZz2nkGMDKaDym+ DRk35pXedAC5apLlT7Ep08sSk7taPecq0tzwmsyJTDNauYPDc73E9ED6gewAzgew JA3xw8/cQYqI3Hz9G0l1MzO/mp4ygq1Xw6HHTktNK5y5d4KiXye5UmnBukho4Q5Z kcKesiUeP0gsLxE27oALz+RIDYemoHGpGKViBadq4pBMTF6Ue0ADw/TDtipQSwNB spGtl+3EL8r3mPjeehxDVcL3Ys35Iy/FSO4WHTNlRRZxUdo/EjKBFwNRoLuowhc1 /Z4sR8OYO27y1yJH+F6SODpLUuy8fP3QXeiRQATk1jPFHCcNc98+HL62H5MJgkU= =clzO -----END PGP SIGNATURE----- --SR0DFWOzPg+ymaCV--