From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1942C433DB for ; Mon, 1 Mar 2021 13:39:36 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D674164DAF for ; Mon, 1 Mar 2021 13:39:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D674164DAF Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 619551676; Mon, 1 Mar 2021 14:38:44 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 619551676 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1614605974; bh=RzxGfNUho/pRixRVXXF9kDanXJH3qDbV0/Ouz9m+A20=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=Gs2DqD/6Pwvyg6696F3nQRZH2vK++/Zo7tNTc1g4rUBoZ61u0zCw0bL3rcAQvoTjB h9ZAvZScF8lNcqBg6jNG+qOIE/Fb97eZNoMInAgLH9y2RSI2P4gpoim2fyjMhoswUL JxdutzvdZbIwmzmdgRKHsW6u4NrA+OvahLo8xvhU= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id D6DADF804DA; Mon, 1 Mar 2021 14:38:43 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id C9E69F804E3; Mon, 1 Mar 2021 14:38:42 +0100 (CET) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id AE6F8F80475 for ; Mon, 1 Mar 2021 14:38:36 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz AE6F8F80475 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 260CEAB8C; Mon, 1 Mar 2021 13:38:36 +0000 (UTC) Date: Mon, 01 Mar 2021 14:38:36 +0100 Message-ID: From: Takashi Iwai To: Anton Yakovlev Subject: Re: [PATCH v6 9/9] ALSA: virtio: introduce device suspend/resume support In-Reply-To: <54854cb9-99c3-4c05-3b43-f41d89a29aec@opensynergy.com> References: <20210227085956.1700687-1-anton.yakovlev@opensynergy.com> <20210227085956.1700687-10-anton.yakovlev@opensynergy.com> <54854cb9-99c3-4c05-3b43-f41d89a29aec@opensynergy.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: virtio-dev@lists.oasis-open.org, alsa-devel@alsa-project.org, "Michael S. Tsirkin" , linux-kernel@vger.kernel.org, Takashi Iwai , virtualization@lists.linux-foundation.org X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, 01 Mar 2021 11:03:04 +0100, Anton Yakovlev wrote: > > On 28.02.2021 13:05, Takashi Iwai wrote: > > On Sat, 27 Feb 2021 09:59:56 +0100, > > Anton Yakovlev wrote: > >> > >> All running PCM substreams are stopped on device suspend and restarted > >> on device resume. > >> > >> Signed-off-by: Anton Yakovlev > >> --- > >> sound/virtio/virtio_card.c | 56 +++++++++++++++++++++++++++++++++++ > >> sound/virtio/virtio_pcm.c | 1 + > >> sound/virtio/virtio_pcm_ops.c | 41 ++++++++++++++++++++----- > >> 3 files changed, 90 insertions(+), 8 deletions(-) > >> > >> diff --git a/sound/virtio/virtio_card.c b/sound/virtio/virtio_card.c > >> index 59455a562018..c7ae8801991d 100644 > >> --- a/sound/virtio/virtio_card.c > >> +++ b/sound/virtio/virtio_card.c > >> @@ -323,6 +323,58 @@ static void virtsnd_remove(struct virtio_device *vdev) > >> kfree(snd->event_msgs); > >> } > >> > >> +#ifdef CONFIG_PM_SLEEP > >> +/** > >> + * virtsnd_freeze() - Suspend device. > >> + * @vdev: VirtIO parent device. > >> + * > >> + * Context: Any context. > >> + * Return: 0 on success, -errno on failure. > >> + */ > >> +static int virtsnd_freeze(struct virtio_device *vdev) > >> +{ > >> + struct virtio_snd *snd = vdev->priv; > >> + > >> + virtsnd_ctl_msg_cancel_all(snd); > >> + > >> + vdev->config->del_vqs(vdev); > >> + vdev->config->reset(vdev); > >> + > >> + kfree(snd->event_msgs); > >> + > >> + /* > >> + * If the virtsnd_restore() fails before re-allocating events, then we > >> + * get a dangling pointer here. > >> + */ > >> + snd->event_msgs = NULL; > >> + > >> + return 0; > > > > I suppose some cancel of inflight works is needed? > > Ditto for the device removal, too. > > It's not necessary here, since the device is reset and all of this are > happened automatically. Hrm, but the reset call itself might conflict with the inflight reset work? I haven't see any work canceling or flushing, so... > But in the device remove it makes sense also to > disable events before calling snd_card_free(), since the device is still > able to send notifications at that moment. Thanks! > > > >> --- a/sound/virtio/virtio_pcm.c > >> +++ b/sound/virtio/virtio_pcm.c > >> @@ -109,6 +109,7 @@ static int virtsnd_pcm_build_hw(struct virtio_pcm_substream *vss, > >> SNDRV_PCM_INFO_BATCH | > >> SNDRV_PCM_INFO_BLOCK_TRANSFER | > >> SNDRV_PCM_INFO_INTERLEAVED | > >> + SNDRV_PCM_INFO_RESUME | > >> SNDRV_PCM_INFO_PAUSE; > > > > Actually you don't need to set SNDRV_PCM_INFO_RESUME. > > This flag means that the driver supports the full resume procedure, > > which isn't often the case; with this, the driver is supposed to > > resume the stream exactly from the suspended position. > > If I understood you right, that's exactly how resume is implemented now > in the driver. Although we fully restart substream on the device side, > from an application point of view it is resumed exactly at the same > position. > > > > Most drivers don't set this but implement only the suspend-stop > > action. Then the application (or the sound backend) will re-setup the > > stream and restart accordingly. > > And an application must be aware of such possible situation? Since I > have no doubt in alsa-lib, but I don't think that for example tinyalsa > can handle this right. Tiny ALSA should work, too. Actually there are only few drivers that have the full PCM resume. The majority of drivers are without the resume support (including a large one like HD-audio). And, with the resume implementation, I'm worried by the style like: > >> @@ -309,6 +318,21 @@ static int virtsnd_pcm_trigger(struct snd_pcm_substream *substream, int command) > >> int rc; > >> > >> switch (command) { > >> + case SNDRV_PCM_TRIGGER_RESUME: { > >> + /* > >> + * We restart the substream by executing the standard command > >> + * sequence. > >> + */ > >> + rc = virtsnd_pcm_hw_params(substream, NULL); > >> + if (rc) > >> + return rc; > >> + > >> + rc = virtsnd_pcm_prepare(substream); > >> + if (rc) > >> + return rc; ... and this is rather what the core code should do, and it's exactly the same procedure that would be done without RESUME flag. Takashi