Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp874590ybe; Thu, 19 Sep 2019 05:19:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqzpEqCyB054M8Oov5KJPEIYrQcLrq/hyzX+dFC76VIekYMLVNBLdVajFWfOLodU/4H7dTFV X-Received: by 2002:a50:d5c5:: with SMTP id g5mr15832407edj.57.1568895576470; Thu, 19 Sep 2019 05:19:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568895576; cv=none; d=google.com; s=arc-20160816; b=Dc2beHSpwWhgWIQ307QFeL4qmw7yaYJNED0Si33FR5VwjnajUEYG8BIS7gHCwFOAZH f3w4VAEfrFoELocak+ysrJa/+YvY+eA0/u3aorjsNTMbWTmoxnAG13JjWPp1jh/bXjS5 uYkbbdmNQ9zDAFrDVxwW6MKUO4sbBw9gJ/QSiYFP5+MYmS2fGwjUxP1any2mO+/qUL0o K1u/5remKVmyuFqDLvh3MLgU1sgFsRd/fSGgvypCooP82o8H+xFYdDEBcLFUAg8S+NMh DMK6jFEwPP1cqq9jA84PfKbqTXWd8ocQEBVW/9Zf9sYEYBb5TRaD9ENTx/j+++/jaTPB NPqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=rbx0MXJE7VaA5Q1hCD/qNZeTOrIn1nmn8xz8X3VD5Xw=; b=HCbJL1zc9E1NUiPEHP1xClmhIeie0Wa+SGCkqegqTGI8SwjP7+bWQsdwIjX/TW7ls5 Zgt6iZ6TggA3N4pR9rFdDT6GKn+wQwYh4OLMfy5+wY+X/7IvBYmUVnYOcrbHh09YE0fe 0WhviK9S+J2rVMlQ3oXj+1p9Gkh4DJatB3jwlqCJ8h6fc2rw3qoWv2znVR26uv8JchhM Xtkgkjm6T7Cipy+aQ2AJrBSQR5/QZF/Vg1mO6kIapFsrkpan33y5DMq/ij1SCXrBXMCN //T9lmN1FlmHBjtKHbUHg1PCUAZ+kqztwvIbMH98zQ7fM43Z64hh+1cCXng8nbKc9ttj /05Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v26si4092114eja.230.2019.09.19.05.19.12; Thu, 19 Sep 2019 05:19:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389164AbfISKXq (ORCPT + 99 others); Thu, 19 Sep 2019 06:23:46 -0400 Received: from mx1.emlix.com ([188.40.240.192]:57578 "EHLO mx1.emlix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389098AbfISKXp (ORCPT ); Thu, 19 Sep 2019 06:23:45 -0400 Received: from mailer.emlix.com (unknown [81.20.119.6]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.emlix.com (Postfix) with ESMTPS id 27A4F6038C; Thu, 19 Sep 2019 12:23:44 +0200 (CEST) From: Philipp Puschmann To: linux-kernel@vger.kernel.org Cc: yibin.gong@nxp.com, fugang.duan@nxp.com, l.stach@pengutronix.de, dan.j.williams@intel.com, vkoul@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, dmaengine@vger.kernel.or, linux-arm-kernel@lists.infradead.org, Philipp Puschmann Subject: [PATCH v2 2/3] dmaengine: imx-sdma: fix dma freezes Date: Thu, 19 Sep 2019 12:23:18 +0200 Message-Id: <20190919102319.23368-3-philipp.puschmann@emlix.com> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20190919102319.23368-1-philipp.puschmann@emlix.com> References: <20190911144943.21554-1-philipp.puschmann@emlix.com> <20190919102319.23368-1-philipp.puschmann@emlix.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org For some years and since many kernel versions there are reports that the RX UART SDMA channel stops working at some point. The workaround was to disable DMA for RX. This commit tries to fix the problem itself. Due to its license i wasn't able to debug the sdma script itself but it somehow leads to blocking the scheduling of the channel script when a running sdma script does not find any free descriptor in the ring to put its data into. If we detect such a potential case we manually restart the channel. As sdmac->desc is constant we can move desc out of the loop. Signed-off-by: Philipp Puschmann Reviewed-by: Lucas Stach --- Changelog v2: - clarify comment and commit description drivers/dma/imx-sdma.c | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c index e029a2443cfc..a32b5962630e 100644 --- a/drivers/dma/imx-sdma.c +++ b/drivers/dma/imx-sdma.c @@ -775,21 +775,23 @@ static void sdma_start_desc(struct sdma_channel *sdmac) static void sdma_update_channel_loop(struct sdma_channel *sdmac) { struct sdma_buffer_descriptor *bd; - int error = 0; - enum dma_status old_status = sdmac->status; + struct sdma_desc *desc = sdmac->desc; + int error = 0, cnt = 0; + enum dma_status old_status = sdmac->status; /* * loop mode. Iterate over descriptors, re-setup them and * call callback function. */ - while (sdmac->desc) { - struct sdma_desc *desc = sdmac->desc; + while (desc) { bd = &desc->bd[desc->buf_tail]; if (bd->mode.status & BD_DONE) break; + cnt++; + if (bd->mode.status & BD_RROR) { bd->mode.status &= ~BD_RROR; sdmac->status = DMA_ERROR; @@ -822,6 +824,17 @@ static void sdma_update_channel_loop(struct sdma_channel *sdmac) if (error) sdmac->status = old_status; } + + /* In some situations it may happen that the sdma does not found any + * usable descriptor in the ring to put data into. The channel is + * stopped then. While there is no specific error condition we can + * check for, a necessary condition is that all available buffers for + * the current channel have been written to by the sdma script. In + * this case and after we have made the buffers available again, + * we restart the channel. + */ + if (cnt >= desc->num_bd) + sdma_enable_channel(sdmac->sdma, sdmac->channel); } static void mxc_sdma_handle_channel_normal(struct sdma_channel *data) -- 2.23.0