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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no 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 5C39BC432C0 for ; Tue, 19 Nov 2019 06:45:34 +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 4ECBD222D3 for ; Tue, 19 Nov 2019 06:45:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="j+YxzDTY" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4ECBD222D3 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 DD44D1684; Tue, 19 Nov 2019 07:44:40 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz DD44D1684 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1574145931; bh=axzvfxhUBzMok+Lyzqvb9gp6UmRyty85t2PymZ9zh4E=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=j+YxzDTY6gVAMUz6c2/1QQ8fDTsBWrf1rwczOtX60YvPXjvWZMhy/CBKSWXcFAnkf AnwigyKdf6765ZPrss29BeT9KBaBxZvYv9kFWl7u8BWIqxCZpRY768YGkPE9nEX2aW EXGLxoTV0lTibCP6zjbvMpxZlbktRMgy+9+sHzB0= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 601D8F800F4; Tue, 19 Nov 2019 07:44:40 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id ED0F0F80137; Tue, 19 Nov 2019 07:44:37 +0100 (CET) Received: from mx1.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 121EFF800F4 for ; Tue, 19 Nov 2019 07:44:33 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 121EFF800F4 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 46F4AAC91; Tue, 19 Nov 2019 06:44:32 +0000 (UTC) Date: Tue, 19 Nov 2019 07:44:31 +0100 Message-ID: From: Takashi Iwai To: Ranjani Sridharan In-Reply-To: <3fc820272992362a56881abf7230f1500fdfdd2a.camel@linux.intel.com> References: <20191117085308.23915-1-tiwai@suse.de> <20191117085308.23915-8-tiwai@suse.de> <3b407a02-b791-52a4-2335-e21d8ab732dd@linux.intel.com> <3fc820272992362a56881abf7230f1500fdfdd2a.camel@linux.intel.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") Cc: Linux-ALSA , "Sridharan, Ranjani" , Pierre-Louis Bossart Subject: Re: [alsa-devel] [PATCH 7/8] ALSA: pcm: Add card sync_irq field 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Tue, 19 Nov 2019 00:47:53 +0100, Ranjani Sridharan wrote: > > On Mon, 2019-11-18 at 21:40 +0100, Takashi Iwai wrote: > > On Mon, 18 Nov 2019 20:55:19 +0100, > > Sridharan, Ranjani wrote: > > > > > > > Thanks for the clarification, Takashi. But just wondering how > > > would one > > > pass > > > > on the sync_irq when the snd_card is created? Typically in > > > the case of > > > the > > > > Intel platforms, the card->dev points to the platform device > > > for the > > > machine > > > > driver that registers the card and the PCI device is the > > > parent of the > > > machine > > > > drv platform device. > > > > > > It's completely up to the driver implementation :) > > > You can implement the own sync_stop ops if that's easier, too. > > > > > > I think this would make sense in the case of the SOF driver and > > > we'd probably > > > need to just call synchronize_irq() in the sync_stop() operation. > > > With this > > > change, we can probably remove the workaround we have to address > > > the issue we > > > were facing during snd_pcm_period_elapsed(). > > > > > > I can give this a try. We might need to run some stress tests to > > > make sure it > > > doesn't break anything. > > > > If this helps for SOF, it'd be great. I have converted only non-ASoC > > drivers regarding the sync-stop stuff, so it won't conflict my > > upcoming changes :) > > > Hi Takashi, > > I just realized that In the SOF driver, we only set the component > driver ops. The pcm ops are set when creating the new pcm. So, should I > also add the sync_stop op in the component driver and set the pcm > sync_stop op to point to the component sync_stop op? Just wanted to > confirm if I am on the right track. Yes, I didn't touch this yet, but that's the way to go I suppose. One caveat is that this ops is optional and needs NULL as default, hence you'd need to set only when defined, like copy_user, page or mmap ops, at least. thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel