Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp5167168ima; Tue, 5 Feb 2019 07:23:22 -0800 (PST) X-Google-Smtp-Source: AHgI3Ib9bTSVOShLBnDQdYGZGFN6jIg/Ec4VJmKvVx4/BLaAB22lHaSa/C1VGd2vyF++RfQZROvT X-Received: by 2002:a17:902:e087:: with SMTP id cb7mr648151plb.313.1549380202884; Tue, 05 Feb 2019 07:23:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549380202; cv=none; d=google.com; s=arc-20160816; b=me4C8fyi5Xud6Y87nTP6rUzDZuRAgHbnpqf1xTyUbM735IR/3NU0QOf+5AuSy8PnmW YaGAfXmN1PgirPVsZkwFCSOzxBBbxgvGa6XzykwZJyIjDJV4EntAqi1ORmhx1WmOpvg0 ErctmKJ9iSE3ekBUXrjS45v2O+OnhQjlBCQs2a7pijjXdtEenKtZBWX2X02BkYbj40Sw uLppcJsPCiMkVmBnVLGYWbOosikAip+9P7m7RdHhqqVQS+4cK4770uHsmjR/Lt205A3K ScMko/uHVpw0J/M6cwT/wPZuZO9SfSQlgXbhdgZinTMeU8ryvSyWxnNuh5cpQi7BYQ0K 7Zww== 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:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=MozAZbg/lc3xRWjn6YkeFHkBJ7fte+FJbAP94vyT2DE=; b=XQiEiPy8IhoWmi7u6rfIbT1n7WTc6MCJbdZtEF/FP5Ll0TjjASam0mvAi91vTRjTAo 1sRjP/cp4s2XVJqifoBazUyqrIfIkcH3nhDbFR0UyOpm6FztUyX9Y3wAqlOnxazoG65w NDrGoRAtl6M7x/DOX/2vNz6GCsbalQ6Io6BSrnSpEUzykdWQ0v0KlUUwe3ucKvmSrG4Y gYKKVVKeiWjazgIE4oP/jpGPZyjqOyXETlJRlzsLNCxwl0aSKGwOQ3coC2/hRmWTvNOg Wi92eNkBxHGWh6cNhTUGaDdzHc6nipowlTHZ5Pk0LNDGXvM9ORaTC7JvXnjEvCiF6+6H 5y6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=vC1gCk8Y; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u6si3209159pgn.181.2019.02.05.07.23.06; Tue, 05 Feb 2019 07:23:22 -0800 (PST) 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=@gmail.com header.s=20161025 header.b=vC1gCk8Y; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729644AbfBEPWu (ORCPT + 99 others); Tue, 5 Feb 2019 10:22:50 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:45858 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729464AbfBEPWt (ORCPT ); Tue, 5 Feb 2019 10:22:49 -0500 Received: by mail-ot1-f68.google.com with SMTP id 32so6190315ota.12 for ; Tue, 05 Feb 2019 07:22:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=MozAZbg/lc3xRWjn6YkeFHkBJ7fte+FJbAP94vyT2DE=; b=vC1gCk8Y6BgYigpxi6FqH3CqGfZ7qty0mSF+MqpXRSReqO/VEffTyluiTt29AFWM/V qF+lY+iMsFTYy/bDOSHVKoWHfLa2gWzez4fMPxYmeUa+cv9v5kTiodlx/Bn8aHOAoHEL ABG6etRJucV+w/8M0nHQAC1mVJ4zyTiN82wn9wlkhxesYjTKPO3Lvr6SbwCTWIG/eR4p Y6CBzOIQwoorFrZgv5STBHaC62tVa/KzAx5U3TlMIlg/4NapxH23lwDktH6F71tlolAF 4XN3iEa2KFAIwAyuocT9d9dJnkJyTPO5CN5gU6rXl7a8p4pZcVsI9P4AKJ+sfpZL4DBx HN2w== 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:content-transfer-encoding; bh=MozAZbg/lc3xRWjn6YkeFHkBJ7fte+FJbAP94vyT2DE=; b=IsPiyIqXvx7kHhIefl73xcAYLGP3b5jSeoxDBeFxpfLbj8Dg33jbz4UPuDAWS9nUwI Y1jJkIOwxc7VxFEfWDgaFnHc/5YNnjAXoJFMNdITcdWQcUvB1+wsO76pR6bZN70hRLee vOJXD9tA4g8/kp6Zt4rM2oP+L59VzueR5Bp58RtvEDLnrH4JiT28b1yANXR7GRtVEsLv rLJceSdYlxTcZxGf+OyKYgg146cVIlF7ICewi35xh4ZYEdWgD9lm2bp9wVXH0OmM4OSF qAoODfbI1zBKui4vfIGBoKYlxTfe30n1/rJg27rjRjruL3AXmL0ry9ocExy+vQnuQUH1 Kszg== X-Gm-Message-State: AHQUAuaZlTnjbJCSUqPH5HIslWTTOeydF8oE7Z1MMpjpLh2ElPdBHxy5 /Cbn9zevuI6r5rQXwaFrlqYLFxzL8OiBz2oGhBA= X-Received: by 2002:aca:ab57:: with SMTP id u84mr2717592oie.87.1549380168611; Tue, 05 Feb 2019 07:22:48 -0800 (PST) MIME-Version: 1.0 References: <20190129153700.18717-1-martink@posteo.de> <20190205135946.64eda55c@xps13> In-Reply-To: <20190205135946.64eda55c@xps13> From: Fabio Estevam Date: Tue, 5 Feb 2019 13:22:45 -0200 Message-ID: Subject: Re: [PATCH] mtd: rawnand: gpmi: fix MX28 bus master lockup problem To: Miquel Raynal Cc: Martin Kepplinger , bbrezillon@kernel.org, Manfred Schlaegl , Richard Weinberger , Martin Kepplinger , linux-kernel , Marek Vasut , linux-mtd@lists.infradead.org, Han Xu , Brian Norris , David Woodhouse Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 5, 2019 at 11:00 AM Miquel Raynal w= rote: > > Hi Martin, > > Martin Kepplinger wrote on Tue, 29 Jan 2019 > 16:37:00 +0100: > > > From: Martin Kepplinger > > > > Disable BCH soft reset according to MX23 erratum #2847 ("BCH soft > > reset may cause bus master lock up") for MX28 too. It has the same > > problem. > > > > Observed problem: once per 100,000+ MX28 reboots NAND read failed on > > DMA timeout errors: > > [ 1.770823] UBI: attaching mtd3 to ubi0 > > [ 2.768088] gpmi_nand: DMA timeout, last DMA :1 > > [ 3.958087] gpmi_nand: BCH timeout, last DMA :1 > > [ 4.156033] gpmi_nand: Error in ECC-based read: -110 > > [ 4.161136] UBI warning: ubi_io_read: error -110 while reading 64 > > bytes from PEB 0:0, read only 0 bytes, retry > > [ 4.171283] step 1 error > > [ 4.173846] gpmi_nand: Chip: 0, Error -1 > > > > Without BCH soft reset we successfully executed 1,000,000 MX28 reboots. > > > > I have a quote from NXP regarding this problem, from July 18th 2016: > > > > "As the i.MX23 and i.MX28 are of the same generation, they share many > > characteristics. Unfortunately, also the erratas may be shared. > > In case of the documented erratas and the workarounds, you can also > > apply the workaround solution of one device on the other one. This have > > been reported, but I=E2=80=99m afraid that there are not an estimated d= ate for > > updating the Errata documents. > > Please accept our apologies for any inconveniences this may cause." > > > > Signed-off-by: Manfred Schlaegl > > Signed-off-by: Martin Kepplinger Does this also need a Fixes tag so that it can be backported to stable? Thanks