From: Takashi Iwai Subject: Re: question on alsa's kernel API concerning snd_power_change_state() Date: Thu, 24 Nov 2011 09:55:38 +0100 Message-ID: References: <201111240928.02679.oneukum@suse.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id B1959244A4 for ; Thu, 24 Nov 2011 09:55:38 +0100 (CET) In-Reply-To: <201111240928.02679.oneukum@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Oliver Neukum Cc: alsa-devel@alsa-project.org, Amit Nagal List-Id: alsa-devel@alsa-project.org At Thu, 24 Nov 2011 09:28:02 +0100, Oliver Neukum wrote: > > Hi, > > if this function has been used to tell the sound core that a device > is in a powersave mode, will the soundcore allow user space to open it? Yes. Some operations (typically ioctl, read, write) are blocked when the mode is set to D3 until snd_power_change_state(D0) is called. But the open itself isn't blocked. Takashi