Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp316901pxv; Wed, 14 Jul 2021 04:50:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxl1+f8IQqE3WAhzue/SiX3eLDwQf1NxlL52pd1tOA3oOunTg7HSQSvsAMAYcMpFdfrpmUL X-Received: by 2002:a05:6602:24d8:: with SMTP id h24mr6954966ioe.27.1626263445511; Wed, 14 Jul 2021 04:50:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626263445; cv=none; d=google.com; s=arc-20160816; b=qvzMM0NcxWAgP7/qK46SwLRmp4JjPTB6z2HqTvXIethbakfpOiw+ZT4W6q+LE+qWIw ezvm9tjHTCoQ15TTdgqHg5b8lyaaJDj7j1MznIFwa4haQCkHgyqxCOWrEO/IdNhUMGyg +QTDDUh9bkdBZ79YrUFZ0UwXPjknvZI+XrMKRDbGFjiPJ3pkD5vn7DmwjGDFn+8h5QlQ LoEsGrIkSC9dHBl3sRbz7iVLPNI8OJDEwEBGhQ4b6nfSiqlqKlE+HVxtWZ6X7vCEnrKA V/LHuNosHgbOaTJWdolpJjC/ecElMY5kaMpNQsRn1ACa/aEiAl/N4ZNpcKq8OuyxjGBs wmoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=132bNXd2CFbUt9KYv8y9sYjf5aFnD3ITjQqBDf11vlA=; b=lNrQUbsP0zTlmScX4PC2xtJWBYDlOvAmKseiakjoHoXYlT3yfOi3X9yOa6NNrD3LGL gFdverYmEWUVzwtUIYZNcYi78Zi9vFGmEXZqTeeba4Wm+hm87ZTX4LOrc/R/uCMPdCHL c3jIa8zxVUHY4BlJOqJXMc8S/y5MKQnl1QlOIWYe2aF5UoMFhA3KwNC7VVHXgF767uYZ aoTcym3RWHG/wG+Vw5VNC+rGy1hknD6UFlqKtG8REtQOYowXxZguHJF7/p5Nfoy3iK9r 8FT3jYd+p32oOFTb30n4WfgjPGuRcChHflTnhkuVqW42J5840jp3AJDf1K7rPRYgSNUT mp2w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@axis.com header.s=axis-central1 header.b="XWDKI9O/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=axis.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r9si2457462jad.24.2021.07.14.04.50.32; Wed, 14 Jul 2021 04:50:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@axis.com header.s=axis-central1 header.b="XWDKI9O/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=axis.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231173AbhGNLwP (ORCPT + 99 others); Wed, 14 Jul 2021 07:52:15 -0400 Received: from smtp2.axis.com ([195.60.68.18]:44014 "EHLO smtp2.axis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230405AbhGNLwP (ORCPT ); Wed, 14 Jul 2021 07:52:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axis.com; q=dns/txt; s=axis-central1; t=1626263363; x=1657799363; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=132bNXd2CFbUt9KYv8y9sYjf5aFnD3ITjQqBDf11vlA=; b=XWDKI9O/Ehj5blDEF4UqcXmEB6dJ8yPRduCLblra7Jx5NFO3i88B6Jiv cLR35YC5ZKCe+E+qtWIwFKdVDaUQCrk5noswD7cm5i8QJEHFVHqeNap3C NmiN7SXuyBjU/XTXicxIqbr5FHL31PpI+dZjfuZ0tjYNM8ZnfXh6zvKZA USEWRWWD97OmmZritIVFqnn6883w0/ZgfeR0zMimbhXq2e7ILtfYeI5fw XSCG6EwF4dRxEzls0wvLw+9Y7KnMSDXMIdnsMTras+0AW0T6BelKdx1gW BUyFCtQM70njROSVkioLP1vE9FrtWtquMbLmZBfY09pR97gP+vnDeNgkt Q==; Date: Wed, 14 Jul 2021 13:49:21 +0200 From: Vincent Whitchurch To: Jaehoon Chung CC: Ulf Hansson , kernel , "linux-mmc@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] mmc: dw_mmc: Fix hang on data CRC error Message-ID: <20210714114921.GA22706@axis.com> References: <20210630102232.16011-1-vincent.whitchurch@axis.com> <81c1b56d-e1be-b3fb-6b44-fc8054f1dd8b@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <81c1b56d-e1be-b3fb-6b44-fc8054f1dd8b@samsung.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 01, 2021 at 12:06:31AM +0200, Jaehoon Chung wrote: > On 6/30/21 7:22 PM, Vincent Whitchurch wrote: > > When a Data CRC interrupt is received, the driver disables the DMA, then > > sends the stop/abort command and then waits for Data Transfer Over. > > > > However, sometimes, when a data CRC error is received in the middle of a > > multi-block write transfer, the Data Transfer Over interrupt is never > > received, and the driver hangs and never completes the request. > > > > The driver sets the BMOD.SWR bit (SDMMC_IDMAC_SWRESET) when stopping the > > DMA, but according to the manual CMD.STOP_ABORT_CMD should be programmed > > "before assertion of SWR". Do these operations in the recommended > > order. With this change the Data Transfer Over is always received > > correctly in my tests. > > I will check with your patch. I didn't see any CRC error on my targets before. Have you had a chance to check it? You can use the fault-injection patch if you want to trigger aborted transfers without getting real CRC errors: https://lore.kernel.org/linux-mmc/20210701080534.23138-1-vincent.whitchurch@axis.com/