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=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 2C289C4740C for ; Mon, 9 Sep 2019 16:25:22 +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 2C9812171F for ; Mon, 9 Sep 2019 16:25:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="B/5Fhd5f" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2C9812171F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=atomide.com 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 0E1EE15F9; Mon, 9 Sep 2019 18:24:29 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 0E1EE15F9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1568046319; bh=xO0LGCcXYTRzyor6iLOoWqsUNzbU00ayv2BNv8cKfwQ=; h=Date:From:To:References:In-Reply-To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=B/5Fhd5fWbmMcNmRlFWIXI7orLQlrjX3eyjmXCZbC2gXHrOvCLSp19vsAQkRZMSiw ktvsflPoW8ClHveEhHLxsaR99EPkkM0VRUF3WI4dtst2qmEX2LtMg1XOtMPd1dXZkr z7EIMqdSHSQyt4kz4ovCbihFFQbiJLaW5lTjkmS4= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 655A8F800C9; Mon, 9 Sep 2019 18:24:28 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 8F8E3F80323; Mon, 9 Sep 2019 18:24:27 +0200 (CEST) Received: from muru.com (muru.com [72.249.23.125]) by alsa1.perex.cz (Postfix) with ESMTP id 73EC3F800C9 for ; Mon, 9 Sep 2019 18:24:12 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 73EC3F800C9 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 69DBC80BF; Mon, 9 Sep 2019 16:24:41 +0000 (UTC) Date: Mon, 9 Sep 2019 09:24:07 -0700 From: Tony Lindgren To: Ladislav Michl Message-ID: <20190909162407.GO52127@atomide.com> References: <20190906165109.53c5a306@tomas.local.tbs-biometrics.cz> <20190907091358.GA7166@lenoch> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190907091358.GA7166@lenoch> User-Agent: Mutt/1.11.4 (2019-03-13) Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, Tomas Novotny Subject: Re: [alsa-devel] omap-mcbsp: TX Buffer Overflow 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" * Ladislav Michl [190907 09:14]: > On Fri, Sep 06, 2019 at 04:51:09PM +0200, Tomas Novotny wrote: > > Hi, > > > > we have AM3703 based board similar to BeagleBoard. I'm hitting this error > > after upgrade to latest LTS 4.19.71 (upgraded from 4.1): > > > > omap-mcbsp 49022000.mcbsp: TX Buffer Overflow! > > > > This appears during or after playing of short (~2s) ding-dong wav. That error > > exists for longer time, because handling of tx buffer overflow irq was > > introduced in 2016: 4e85e7776eba ("ASoC: omap-mcbsp: Enable TX/RX under and > > overflow interrupts"). I've cherry-picked it to 4.1 and I see the error there also. > > The sound seems clear and ok to me, but we are using low quality speaker. > > Just FYI, for stream capture there's > omap-mcbsp 49022000.mcbsp: RX Buffer Underflow! > > As far as I remember all stable kernels we have in production - 4.9.x, 4.14.x and > 4.19.x - are affected. IGEPv2 with both DM3730 and OMAP3530 are affected > (headless machines, CONFIG_VIDEO_OMAP3=n). Hmm I wonder if this is still related to the SoC idling? See commit 9834ffd1ecc3 ("ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches"), maybe something still needs to be fixed in that area. > And DT is probably worth updating: > omap_hwmod: mcbsp2_sidetone using broken dt data from mcbsp > omap_hwmod: mcbsp3_sidetone using broken dt data from mcbsp > > I never motivated myself to dig deeper as catured stream looks pretty normal. These mean the devices should really have separate nodes in the dts rather than combining multiple devices into a single node with multiple reg entries. The issue with combining multiple devices into a single device is that flushing posted write with a read back to one register range will not flush it for the other which can cause mysterious bugs. Regards, Tony _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel