Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1859606yba; Sun, 14 Apr 2019 23:06:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqwMUoXt3/UsxEYQ6j1ggQE5IYvJprQnH/4433vpjQ0/EOueinIzJbSOKSllHBNko8z6Ahwu X-Received: by 2002:a17:902:7044:: with SMTP id h4mr29616115plt.274.1555308365074; Sun, 14 Apr 2019 23:06:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555308365; cv=none; d=google.com; s=arc-20160816; b=Yu08K9FuWjCHvc6UT1xHod9bRixaU8Ih4K1wZzb/hlC1OyKaEw7FMZrLiFx+LyDN0P 1wDWptHDu4yQTXocaBYe6rf4RptC4XV+QPAs+CLUODcNDaZG7YE4YtRQ9fL6hdoxs5Ap 8UacMPxYwhMN/GO/FUhDTAQY5DWEFoZm39gQ/pbB46OC5GLVFH7OcNlPUQR0N6X2ZpRF rPFE0+olpC5odLHz49bq4usQ+9b7MwPXcgzG6+/OtLyl286fZBU/BTuDLOO/LPBI5MJJ +bTE61uGY8ZWd31De6QYZ501nIV/htJ52uOBIaxFSsvLU9t7+apa/soLFG5UzBmf8YLf UjHQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=bf7N1T49K0dI6TDOW6lCp0H/CK7puDrL5/l1rrtK6Ek=; b=cgTu3QPdZ+ZErTVQuuxkxKAQiGI0G1ZiWfzsOV0TxRmdmnocKCffWHG2LzwvgT/ZWb FFtXZ07UaxOu7cbKOQ77kann0Jfjhj7YTntIf9WjuJCXl6O4TM3YHlBFjrnnFMCte7M6 hdlF4sq5Ds3buW1Bx8/XqI6qPfleG0eKerp6o+FwXLd+Gg+NX/SdbCVP8IkOBtIC3VfX pIXiuTXzr8QKOF/G0MhrGkSdYt/t4QrFjramZwKDN1Jvf9mhNwezBqhqJQnIxLHlQxSc YPw1Dxii3T1/Sb+AncMGuyxl38y8CU+h+NBRDf0BYd+gHtMMRQO4oqS34/MLiO8yA0r1 HF7Q== 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 a22si44537680plm.263.2019.04.14.23.05.48; Sun, 14 Apr 2019 23:06:05 -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 S1726211AbfDOGEc (ORCPT + 99 others); Mon, 15 Apr 2019 02:04:32 -0400 Received: from mail-sz.amlogic.com ([211.162.65.117]:30410 "EHLO mail-sz.amlogic.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725796AbfDOGEb (ORCPT ); Mon, 15 Apr 2019 02:04:31 -0400 Received: from [10.28.18.125] (10.28.18.125) by mail-sz.amlogic.com (10.28.11.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1591.10; Mon, 15 Apr 2019 14:04:30 +0800 Subject: Re: [PATCH 4/4] mtd: rawnand: meson: only initialize the RB completion once To: Martin Blumenstingl , , , , CC: , , , , , , References: <20190411220056.19109-1-martin.blumenstingl@googlemail.com> <20190411220056.19109-5-martin.blumenstingl@googlemail.com> From: Liang Yang Message-ID: Date: Mon, 15 Apr 2019 14:04:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190411220056.19109-5-martin.blumenstingl@googlemail.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.28.18.125] X-ClientProxiedBy: mail-sz.amlogic.com (10.28.11.5) To mail-sz.amlogic.com (10.28.11.5) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/4/12 6:00, Martin Blumenstingl wrote: > Documentation/scheduler/completion.txt states: > Calling init_completion() on the same completion object twice is > most likely a bug as it re-initializes the queue to an empty queue and > enqueued tasks could get "lost" - use reinit_completion() in that case, > but be aware of other races. > > Initialize nfc->completion in meson_nfc_probe using init_completion and > change the call in meson_nfc_queue_rb to reinit_completion so the logic > matches what the documentation suggests. > > Signed-off-by: Martin Blumenstingl > --- > drivers/mtd/nand/raw/meson_nand.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/mtd/nand/raw/meson_nand.c b/drivers/mtd/nand/raw/meson_nand.c > index 57cc4bd3f665..ea57ddcec41e 100644 > --- a/drivers/mtd/nand/raw/meson_nand.c > +++ b/drivers/mtd/nand/raw/meson_nand.c > @@ -400,7 +400,7 @@ static int meson_nfc_queue_rb(struct meson_nfc *nfc, int timeout_ms) > cfg |= NFC_RB_IRQ_EN; > writel(cfg, nfc->reg_base + NFC_REG_CFG); > > - init_completion(&nfc->completion); > + reinit_completion(&nfc->completion); Tested-by:Liang Yang Acked-by: Liang Yang > > /* use the max erase time as the maximum clock for waiting R/B */ > cmd = NFC_CMD_RB | NFC_CMD_RB_INT > @@ -1380,6 +1380,7 @@ static int meson_nfc_probe(struct platform_device *pdev) > > nand_controller_init(&nfc->controller); > INIT_LIST_HEAD(&nfc->chips); > + init_completion(&nfc->completion); Tested-by:Liang Yang Acked-by: Liang Yang > > nfc->dev = dev; > >