Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4110144ybi; Mon, 27 May 2019 11:19:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqyQvbU+ef3PXrp817w4+WxWmGYeXDU6R0GElolN/yi5GvKF03pmUSpRohlJjX7wyFHmvXlf X-Received: by 2002:a17:90a:cd04:: with SMTP id d4mr355871pju.128.1558981150130; Mon, 27 May 2019 11:19:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558981150; cv=none; d=google.com; s=arc-20160816; b=YWNcAP2jyYFYNST/PNNpHfLqoDuWPR6BYmjUMHg3n0ocBe64hiMzkUy+l6F1eWBbnV McYDv+eNJ7osq+3cJVWRbRcPOKTuwXAPjB3A0IpoiqPKFMsnHyBjR7fnahbGmSUlEKBV fMndfn7LCBUqLWEVipK55cIF9KYJLiEzAE/nYGweK2DwV/gEr+7DbPjmAjdN/pXeLTE+ ov7S8eIC+DnSME1DxazBFR+oyNeJZvkXthEEtI+arEcauYgIctLlbwGQdLoE2qvtv06h 7cYiDr1CVg/jL1ncBmQuxl0rPuA+69uwssqVkCyN1mKgeBV9+oTygzRByrycZTH94+Q5 irzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=Wk2hdUXANFYl1/k0tGnBJuWme842kQgEugYRrAdMJgU=; b=Wvt05M3z923KQbh64GcAe3DBN+M8kTshaPhfRiAiYmz2l8nVbLw+OvV7EbGgwQfYic 7zeZYONg3tV133XGvO9d99n2AsEsaNeCPzAfy6yM7rTupqH+Ye+e9Bwydfd7M4itRBXJ jrQxhmjqEW4KORTNo6mFrzOXxABsGNJDB0wbXpbIM5r1M+Q3pdJufqUGcu7LrzP4KN9c al1zc2434mK+O3ejS6azc3qSnjJTCrQwgK0cYWjO/0k+gxCNo2XbDp2IfrS6gxllDrPY sRZQFmag2akkbboPqVVmYkT8kNx/u7iJypLWup8CYxDYOXUNhw1pJdK/atQAnm5O9ktu plBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=dS4IbOdh; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c94si147047pje.24.2019.05.27.11.18.54; Mon, 27 May 2019 11:19:10 -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; dkim=pass header.i=@linaro.org header.s=google header.b=dS4IbOdh; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727128AbfE0SRn (ORCPT + 99 others); Mon, 27 May 2019 14:17:43 -0400 Received: from mail-vs1-f65.google.com ([209.85.217.65]:34626 "EHLO mail-vs1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726817AbfE0SRn (ORCPT ); Mon, 27 May 2019 14:17:43 -0400 Received: by mail-vs1-f65.google.com with SMTP id q64so11120345vsd.1 for ; Mon, 27 May 2019 11:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wk2hdUXANFYl1/k0tGnBJuWme842kQgEugYRrAdMJgU=; b=dS4IbOdhgZVSQqWE7W9HLkrZGQvhZ5abk5sQyiNlaHVjv85/1nWeAywC/QDyez/NL5 z5AsU7MavE++ZEHOw8BPtuFl6Sl4UofmOw2JMe8ShMocnqtby87XNUKx/Ynr/IiV5k4S orzYRSZzC7PdIRMNlk5aBCIXPnUpTfvSyJn5JPRMiFhwEko33ECMK7cuh70/+y6un1gJ rrPyBdC2KSR4FFZ/fXnMog2IOWRqmbwXXzgLgWBhbyphDpZn+xro+tYx+/W4yNXgHXah 3/mzTz1Ffet/YgR4K1+Noi+2C8Qr5Gf16oP/oHeUde/Cw3BPJYfSTbmqpKYSPiHHrZ9H ELeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wk2hdUXANFYl1/k0tGnBJuWme842kQgEugYRrAdMJgU=; b=pDrjWzgTPc/5hK8MubZ1CwTCymsKsMRZ0qoQWuykVRwEXJPBjVFn/3HtODwXI0lrx3 dhuRQxFQGGcY21k1UZ6GLmIRwQJjwJSutsnY4Uf73C7hqIfL3BaPUSFWyKZUo2Wo4mBT rkf9New5+FOODCNblrNMg6K8DB415XOt7fB5z0iz9fcSOUgkd3yC8ceUOL0NH1UGHmnu T3tvWaSTZG34Tm5n4HcNhkHd9yZZT66meGYBkF0Tv2/gmc1WaHTJkP7vadYGEMkeaAsU 3oc8IJlC77IV9JrJ/ipkYJEaNT9btcLrNNe/95Wx5vZMDUrlMUmHoXWpoqCOOriVwPQH ewYg== X-Gm-Message-State: APjAAAViuXrdMx/oYnwj6tuGvweriI3d474MuVMRyiQfnQg6p51fdjmD sgcvw/muf2tZFEGdk8h3jaeMehq1tLUTspHM0bAFmg== X-Received: by 2002:a67:3046:: with SMTP id w67mr51182171vsw.165.1558981062356; Mon, 27 May 2019 11:17:42 -0700 (PDT) MIME-Version: 1.0 References: <1556264798-18540-1-git-send-email-ludovic.Barre@st.com> <1556264798-18540-4-git-send-email-ludovic.Barre@st.com> In-Reply-To: <1556264798-18540-4-git-send-email-ludovic.Barre@st.com> From: Ulf Hansson Date: Mon, 27 May 2019 20:17:05 +0200 Message-ID: Subject: Re: [PATCH V2 3/5] mmc: mmci: fix clear of busy detect status To: Ludovic Barre Cc: Rob Herring , Srinivas Kandagatla , Maxime Coquelin , Alexandre Torgue , Linux ARM , Linux Kernel Mailing List , DTML , "linux-mmc@vger.kernel.org" , linux-stm32@st-md-mailman.stormreply.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 26 Apr 2019 at 09:46, Ludovic Barre wrote: > > From: Ludovic Barre > > The "busy_detect_flag" is used to read/clear busy value of > mmci status. The "busy_detect_mask" is used to manage busy irq of > mmci mask. > For sdmmc variant, the 2 properties have not the same offset. > To clear the busyd0 status bit, we must add busy detect flag, > the mmci mask is not enough. > > Signed-off-by: Ludovic Barre Ludovic, again, apologies for the delay. > --- > drivers/mmc/host/mmci.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c > index a040f54..3cd52e8 100644 > --- a/drivers/mmc/host/mmci.c > +++ b/drivers/mmc/host/mmci.c > @@ -1517,7 +1517,8 @@ static irqreturn_t mmci_irq(int irq, void *dev_id) > * to make sure that both start and end interrupts are always > * cleared one after the other. > */ > - status &= readl(host->base + MMCIMASK0); > + status &= readl(host->base + MMCIMASK0) | > + host->variant->busy_detect_flag; I think this is not entirely correct, because it would mean we check for busy even if we haven't unmasked the busy IRQ via the variant->busy_detect_mask. I suggest to store a new bool in the host (call it "busy_detect_unmasked" or whatever makes sense to you), to track whether we have unmasked the busy IRQ or not. Then take this flag into account, before ORing the value of host->variant->busy_detect_flag, according to above. > if (host->variant->busy_detect) > writel(status & ~host->variant->busy_detect_mask, > host->base + MMCICLEAR); > -- > 2.7.4 > Kind regards Uffe