Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp5761618pxu; Thu, 22 Oct 2020 10:20:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzBQBFEXpHeyBN1nlU6aokMvGHVmRScd7xU7xt9XqAPU1diAF6sIFTg/pIknSl7JoOSlMIQ X-Received: by 2002:a17:907:a8d:: with SMTP id by13mr3117930ejc.295.1603387202337; Thu, 22 Oct 2020 10:20:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603387202; cv=none; d=google.com; s=arc-20160816; b=ozB8JT31miv2aSigo8UB08W2K5BDiMr61l4WlM4XjRg2XxsiSpu9x73V+8QubVW7AZ DapxOsWsp0/tyY/JpKcB8gaiEp2ub3fcX7nhsAj56WeB79tJloMZSN81ridwTKkSDd+4 n+fmcucZKbfw+49nCUiOx/mUyw31R5MFfUxkgNf+hJ7xoPU2o/OTzjFz5Lzk9z3vJ0CM 5LgkEFb30ePw5dBZpxtKKw9V09ODtrdQFRddjtbCoDRhRWW2Lrif8MfJ3SHFNqLtZoaX sUs1EUEoX0JrtcDAHsEgXRbjYKjGKh3Aux1WKIPvhHJX2vML3r7MDiutuAvmSk+79ZRz rKPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=mialpmlTByUN/FdHQ+yBGSqMoG4U9kbwv71N40YEZEo=; b=mxSBQzP0rA2kcF33pj7yTeIHX5NvEz1APwop0ao5B0tzpKdXQtKEZkPxN9i2RuIEkE BJ9+pwYLLq7MAWJsBWRJvIB7X0ZrGlhbcmgE+ZY0iH2LlOVlBKvLq5TfyPcP8cjgOJ+X 6ii1W+abkXhMHM9U8VPx4d7G+p4yusIWIhevfYbjwjQG+Lwv1giISFojjZHvjGu/k+Qe GdHgsdXF4R9LxNh0DGhC6C4ho7QkK3uahC7s6D84bNSAXKG206J6wzvdYbq5SVIzitBF abxwYc+iRiCUGfS+k95glOgTtYu0yBNto8xo4Q/3VHqxHwypEqHK1LGeqw9hHCv+Xp4/ 8Zkg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bu8si1651152edb.95.2020.10.22.10.19.40; Thu, 22 Oct 2020 10:20:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2899786AbgJVNVH (ORCPT + 99 others); Thu, 22 Oct 2020 09:21:07 -0400 Received: from mx2.suse.de ([195.135.220.15]:50340 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2899739AbgJVNUv (ORCPT ); Thu, 22 Oct 2020 09:20:51 -0400 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 EC29CB904; Thu, 22 Oct 2020 13:20:49 +0000 (UTC) Date: Thu, 22 Oct 2020 15:20:49 +0200 Message-ID: From: Takashi Iwai To: Maxime Ripard Cc: Jaroslav Kysela , Takashi Iwai , Liam Girdwood , Mark Brown , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, Dom Cobley , Dave Stevenson , Nicolas Saenz Julienne Subject: Re: Context expectations in ALSA In-Reply-To: <20201022125741.xxibhwgcr2mhxehe@gilmour.lan> References: <20201022095041.44jytaelnlako54w@gilmour.lan> <30226f94-72e9-34d2-17d0-11d2501053f0@perex.cz> <20201022125741.xxibhwgcr2mhxehe@gilmour.lan> 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 22 Oct 2020 14:57:41 +0200, Maxime Ripard wrote: > > On Thu, Oct 22, 2020 at 12:03:19PM +0200, Jaroslav Kysela wrote: > > Dne 22. 10. 20 v 11:50 Maxime Ripard napsal(a): > > > > > So, I'm not really sure what I'm supposed to do here. The drivers > > > involved don't appear to be doing anything extraordinary, but the issues > > > lockdep report are definitely valid too. What are the expectations in > > > terms of context from ALSA when running the callbacks, and how can we > > > fix it? > > > > I think that you should set the non-atomic flag and wake up the workqueue or > > so from interrupt handler in this case. Call snd_pcm_period_elapsed() from the > > workqueue not the interrupt handler context. > > Yeah, that was my first guess too. However, the DMA driver uses some > kind of generic helpers using a tasklet, so getting rid of it would take > some work and would very likely not be eligible for stable. Who sets the nonatomic flag for vc4? I couldn't find the relevant code in the latest upstream. Ideally dmaengine PCM helper should support the nonatomic mode, but until then, the other side needs to drop the nonatomic flag, I suppose. thanks, Takashi