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.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, UNPARSEABLE_RELAY,URIBL_BLOCKED,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 0F767C43331 for ; Sat, 7 Sep 2019 09:15:02 +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 F02372186A for ; Sat, 7 Sep 2019 09:15:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="ZYMUUwY5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F02372186A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-mips.org 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 8EB6B843; Sat, 7 Sep 2019 11:14:08 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 8EB6B843 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1567847698; bh=8xdtzloPC5i8MrI40szelS7L65pjGBXtrxjjP5r2Row=; h=Date:From:To:References:In-Reply-To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=ZYMUUwY5zZQceSUusuE7vjkbJCl8hmt8Q4f3zW++oshmgoeMzmaqzoZP3WDYBzOH0 qpAudx36F0Yi0iieLoc/7CAESNmqwN/hF4aGOEPgXjniqYTX1NVi14my357lni4enw E2vx4H8m4W3pUrgjk3RuRIRiSosSvFfFnt6yfckg= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 03A4FF800C6; Sat, 7 Sep 2019 11:14:08 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 443A6F80448; Sat, 7 Sep 2019 11:14:06 +0200 (CEST) Received: from cvs.linux-mips.org (eddie.linux-mips.org [148.251.95.138]) by alsa1.perex.cz (Postfix) with ESMTP id C8A61F800C6 for ; Sat, 7 Sep 2019 11:14:02 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz C8A61F800C6 Received: (from localhost user: 'ladis' uid#1021 fake: STDIN (ladis@eddie.linux-mips.org)) by eddie.linux-mips.org id S23994248AbfIGJOAdZwOx (ORCPT ); Sat, 7 Sep 2019 11:14:00 +0200 Date: Sat, 7 Sep 2019 11:13:58 +0200 From: Ladislav Michl To: Tomas Novotny Message-ID: <20190907091358.GA7166@lenoch> References: <20190906165109.53c5a306@tomas.local.tbs-biometrics.cz> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190906165109.53c5a306@tomas.local.tbs-biometrics.cz> User-Agent: Mutt/1.10.1 (2018-07-13) Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org 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" 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). 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. l. > There are two workarounds to get rid of the message: > 1) Change 'dma_op_mode' sysfs attribute from 'element' to 'threshold'. I > found that just by coincidence when checking sysfs attributes. > 2) Compile kernel with CONFIG_VIDEO_OMAP3=y. Found on Logic PD forum [1]. > > Does anybody have any idea what's going wrong? Or why these (somehow) > unrelated workarounds help? > > Thanks, > > Tomas > > [1] https://support.logicpd.com/TDGForum/tabid/124/aft/2277/Default.aspx _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ladislav Michl Subject: Re: omap-mcbsp: TX Buffer Overflow Date: Sat, 7 Sep 2019 11:13:58 +0200 Message-ID: <20190907091358.GA7166@lenoch> References: <20190906165109.53c5a306@tomas.local.tbs-biometrics.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20190906165109.53c5a306@tomas.local.tbs-biometrics.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" To: Tomas Novotny Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org List-Id: linux-omap@vger.kernel.org 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). 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. l. > There are two workarounds to get rid of the message: > 1) Change 'dma_op_mode' sysfs attribute from 'element' to 'threshold'. I > found that just by coincidence when checking sysfs attributes. > 2) Compile kernel with CONFIG_VIDEO_OMAP3=y. Found on Logic PD forum [1]. > > Does anybody have any idea what's going wrong? Or why these (somehow) > unrelated workarounds help? > > Thanks, > > Tomas > > [1] https://support.logicpd.com/TDGForum/tabid/124/aft/2277/Default.aspx