Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp4466456rwb; Tue, 16 Aug 2022 23:46:03 -0700 (PDT) X-Google-Smtp-Source: AA6agR5mNqfiqAK+LMjg0UAL3uIVV2HeohM93+rWx4w/9Ad1M93p5DUCbXgjxISUycAFTzdf15mn X-Received: by 2002:a17:907:7fac:b0:732:989b:6bd6 with SMTP id qk44-20020a1709077fac00b00732989b6bd6mr15978879ejc.39.1660718762770; Tue, 16 Aug 2022 23:46:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660718762; cv=none; d=google.com; s=arc-20160816; b=AHfIy76EtEnriqVNbZsp2RBhv3ZjIphJHcuHCJN2IfaT0EQeg4CKlUR3RXYrK/Kzr8 F1iVODtv632eO4/1NzxFYnf6KdYuWPAEnakn9EtRzoWlmItbpJFvLQmJz981cIFk3UXb cgmXevYvc9rz+Iz965BfFQk6EVt3pa3UUiByR1x4MDJZ5wZ029f9VuiL3EVtYBu1/zzD ucDDg6WMvRb4wsq4TGJKWXB72Yl211yNxARZa2OsY9Df3t5BiTRe3gQ5f+tTeegCZom3 pxJmiGrRS8C4HSi3l0Bxu1LLPvj2NazgawSfVlnkRqiOH/q4+KxYdi6JFyEe6hjkTK/k twNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=Pl8j8nMikEGLv3auuJamJeuxCXOj7rX7d17W0lTlskY=; b=VXp7mFthoI6rpJwrfUcJjLvgVJc+BO8/d72nDKfFQUniehTAVxCDBBX6q028HdkzXf CjFCwCvdAoeiWQ0KPBJA2Diu43rtzB+du9bT9BYhOeb7WC1UBFO7X8SbQdM7EvbZYi9/ WGj6zEHbW8DYgXOiAR3iCJg80a/ypHsMncER6M0ueW315qHAUSaE9G1QtCTqO1irzJOb HrW8oGc0Urc3iqOUhIEATMlJ2y/80XE1XQv5gfKM8mnZyJJAKzIytqHgfMLPCENWum5F wJURSqdDojbeGGVSmfeg4xC89G27rj0HerdebDx3UZl02lFTGISBVWQSoufL9vjYi3uS +IHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=IOxuVGEu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y13-20020a056402440d00b0043d48f26cfbsi12587732eda.236.2022.08.16.23.45.37; Tue, 16 Aug 2022 23:46:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=IOxuVGEu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238926AbiHQGfh (ORCPT + 99 others); Wed, 17 Aug 2022 02:35:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47084 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229689AbiHQGff (ORCPT ); Wed, 17 Aug 2022 02:35:35 -0400 Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 16C367695A for ; Tue, 16 Aug 2022 23:35:35 -0700 (PDT) Received: by mail-wm1-x329.google.com with SMTP id d5so3950539wms.5 for ; Tue, 16 Aug 2022 23:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=Pl8j8nMikEGLv3auuJamJeuxCXOj7rX7d17W0lTlskY=; b=IOxuVGEuuWrhB890xfIpMhVaObL/QznrYMLo0MDJU8skANXcLIpC5rM9IZj9P1k1S9 RTPEAdpwwl4G0dBwPFBLTa8u7oyRnV9YiY1/D/muF5gBw8zwSV/R+RccjDUHj6/ThBOT OV4PiVZqQvt1vUIAoHq/jUZDO3oIqeXHxJK/d2FGT6CLpVYrMaQyZqRk17hxWFlq9Ci/ LO2AmqpVa4X9M7v/2LShjYzdQUVjSQM0NRDLDUGEG8M1tq3ELCylC683JyE9NYHh4sgL sHHHwPUJeHmp17fhNCvWy4DcEu9PEPM5zQCcwH05fw+IjbjE3IShAewKoqv8ZRiSdGL9 0frQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=Pl8j8nMikEGLv3auuJamJeuxCXOj7rX7d17W0lTlskY=; b=Fs8uTRCwJ7qK6hv5B0wljQNOv1K6jsVfyKa01LvKQLFo5v7E8T/TLhoojl6lunk/bA Cms32IKdziOMN520xA9f8ZT8F6ij2sEJrB6h5VlTCTwKoX1xiuJ6wHYgLEpN5ysJ4S6k OsuQIFZlySHrShrLP4Tu/oirsEsyny3ni2FJLWGTxV8dyXWvUVKWqFlg8xp0EFq23jhE 2sm+tY9Ktq3VQHEGuR4LUAMWEIiQIl5LijCAEF3DPcm4SNKQHNhY76EOhxA6xZVv96je vgOtY0G5VbsQDW/mbExbT3a360xdupTWGLbKj7y03ST0NVzS1WjI3fG3vlvOj3MIJh6t kd/w== X-Gm-Message-State: ACgBeo3TY+yM6SYIbWbZLnymf6a5alrZA29OdP+LsT/4a18eUPZO+IFJ Wln6rsCeA00TRfX4+LSiKhTMpSqdqdhbkyI4Ids= X-Received: by 2002:a1c:f718:0:b0:3a3:2416:634d with SMTP id v24-20020a1cf718000000b003a32416634dmr1114507wmh.83.1660718133588; Tue, 16 Aug 2022 23:35:33 -0700 (PDT) MIME-Version: 1.0 References: <1660713867-26921-1-git-send-email-shengjiu.wang@nxp.com> In-Reply-To: From: Nicolin Chen Date: Tue, 16 Aug 2022 23:35:22 -0700 Message-ID: Subject: Re: [PATCH] ASoC: fsl_sai: Remove unnecessary FIFO reset in ISR To: Shengjiu Wang Cc: Shengjiu Wang , Xiubo Li , Fabio Estevam , Liam Girdwood , Mark Brown , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linuxppc-dev , linux-kernel Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 16, 2022 at 11:29 PM Shengjiu Wang wrote: >> > The FIFO reset drops the words in the FIFO, which may cause >> > channel swap when SAI module is running, especially when the >> > DMA speed is low. So it is not good to do FIFO reset in ISR, >> > then remove the operation. >> >> I don't recall the details of adding this many years ago, but >> leaving underrun/overrun errors unhandled does not sound right >> to me either. Would it result in a channel swap also? Perhaps >> there needs to be a reset routine that stops and restarts the >> DMA as well? > > > Remove the reset, the channel swap is gone. I have no doubt about that :) > IMO, no need to handle the underrun/overrun in driver, the SAI > hardware can handle the read/write pointer itself when xrun happen, > and we don't need reset routine. That'd be okay then.