From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1035113AbdEXL0T (ORCPT ); Wed, 24 May 2017 07:26:19 -0400 Received: from mail.free-electrons.com ([62.4.15.54]:37520 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1035099AbdEXLZK (ORCPT ); Wed, 24 May 2017 07:25:10 -0400 Date: Wed, 24 May 2017 13:25:08 +0200 From: Boris Brezillon To: Chris Packham Cc: "linux-mtd@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Thomas Petazzoni , "ezequiel.garcia@free-electrons.com" , Gregory Clement Subject: Re: pxa3xx-nand failing to find device on linux-next Message-ID: <20170524132508.420614c7@bbrezillon> In-Reply-To: <20170524132301.12ad33d8@bbrezillon> References: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc> <20170524132301.12ad33d8@bbrezillon> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 24 May 2017 13:23:01 +0200 Boris Brezillon wrote: > Hi Chris, > > On Wed, 24 May 2017 09:36:56 +0000 > Chris Packham wrote: > > > On 23/05/17 17:27, Chris Packham wrote: > > > Hi, > > > > > > I'm doing some testing on linux-next and I'm finding that my nand flash > > > has disappeared. > > > > > > pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device > > > pxa3xx-nand f10d0000.flash: non-supported command ef > > > pxa3xx-nand f10d0000.flash: non-supported command ee > > > pxa3xx-nand f10d0000.flash: non-supported command ef > > > pxa3xx-nand f10d0000.flash: non-supported command ee > > > On-die ECC forcefully enabled, not supported > > > nand: No NAND device found > > > pxa3xx-nand f10d0000.flash: failed to scan nand at cs 0 > > > > > > This was working around 4.11. I'll try to do some more digging tomorrow > > > to narrow down a failure point but I thought I'd send this out now just > > > in case it rings any bells. > > > > > > The board I'm using (DB-88F6820-AMC) is unfortunately out-of tree but it > > > should be pretty close to the armada-388-db. I can make my dts available > > > if it's helpful. > > > > Still works on 4.12-rc2. Fails on next-20170524. > > > > This appears to be due to commit b566d9c055de ("mtd: nand: add support > > for Micron on-die ECC"). Which based on the description seems intentional. > > > > Since I have access to a hardware platform that has a micron flash with > > ECC forcefully enabled how can I help to get this implemented. > > Can you try with this patch applied [1]? Sorry, wrong patch. Can you try this one [1] instead? [1]http://code.bulix.org/pkfhmi-135875 From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 24 May 2017 13:25:08 +0200 From: Boris Brezillon To: Chris Packham Cc: "linux-mtd@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Thomas Petazzoni , "ezequiel.garcia@free-electrons.com" , Gregory Clement Subject: Re: pxa3xx-nand failing to find device on linux-next Message-ID: <20170524132508.420614c7@bbrezillon> In-Reply-To: <20170524132301.12ad33d8@bbrezillon> References: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc> <20170524132301.12ad33d8@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 24 May 2017 13:23:01 +0200 Boris Brezillon wrote: > Hi Chris, > > On Wed, 24 May 2017 09:36:56 +0000 > Chris Packham wrote: > > > On 23/05/17 17:27, Chris Packham wrote: > > > Hi, > > > > > > I'm doing some testing on linux-next and I'm finding that my nand flash > > > has disappeared. > > > > > > pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device > > > pxa3xx-nand f10d0000.flash: non-supported command ef > > > pxa3xx-nand f10d0000.flash: non-supported command ee > > > pxa3xx-nand f10d0000.flash: non-supported command ef > > > pxa3xx-nand f10d0000.flash: non-supported command ee > > > On-die ECC forcefully enabled, not supported > > > nand: No NAND device found > > > pxa3xx-nand f10d0000.flash: failed to scan nand at cs 0 > > > > > > This was working around 4.11. I'll try to do some more digging tomorrow > > > to narrow down a failure point but I thought I'd send this out now just > > > in case it rings any bells. > > > > > > The board I'm using (DB-88F6820-AMC) is unfortunately out-of tree but it > > > should be pretty close to the armada-388-db. I can make my dts available > > > if it's helpful. > > > > Still works on 4.12-rc2. Fails on next-20170524. > > > > This appears to be due to commit b566d9c055de ("mtd: nand: add support > > for Micron on-die ECC"). Which based on the description seems intentional. > > > > Since I have access to a hardware platform that has a micron flash with > > ECC forcefully enabled how can I help to get this implemented. > > Can you try with this patch applied [1]? Sorry, wrong patch. Can you try this one [1] instead? [1]http://code.bulix.org/pkfhmi-135875 From mboxrd@z Thu Jan 1 00:00:00 1970 From: boris.brezillon@free-electrons.com (Boris Brezillon) Date: Wed, 24 May 2017 13:25:08 +0200 Subject: pxa3xx-nand failing to find device on linux-next In-Reply-To: <20170524132301.12ad33d8@bbrezillon> References: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc> <20170524132301.12ad33d8@bbrezillon> Message-ID: <20170524132508.420614c7@bbrezillon> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, 24 May 2017 13:23:01 +0200 Boris Brezillon wrote: > Hi Chris, > > On Wed, 24 May 2017 09:36:56 +0000 > Chris Packham wrote: > > > On 23/05/17 17:27, Chris Packham wrote: > > > Hi, > > > > > > I'm doing some testing on linux-next and I'm finding that my nand flash > > > has disappeared. > > > > > > pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device > > > pxa3xx-nand f10d0000.flash: non-supported command ef > > > pxa3xx-nand f10d0000.flash: non-supported command ee > > > pxa3xx-nand f10d0000.flash: non-supported command ef > > > pxa3xx-nand f10d0000.flash: non-supported command ee > > > On-die ECC forcefully enabled, not supported > > > nand: No NAND device found > > > pxa3xx-nand f10d0000.flash: failed to scan nand at cs 0 > > > > > > This was working around 4.11. I'll try to do some more digging tomorrow > > > to narrow down a failure point but I thought I'd send this out now just > > > in case it rings any bells. > > > > > > The board I'm using (DB-88F6820-AMC) is unfortunately out-of tree but it > > > should be pretty close to the armada-388-db. I can make my dts available > > > if it's helpful. > > > > Still works on 4.12-rc2. Fails on next-20170524. > > > > This appears to be due to commit b566d9c055de ("mtd: nand: add support > > for Micron on-die ECC"). Which based on the description seems intentional. > > > > Since I have access to a hardware platform that has a micron flash with > > ECC forcefully enabled how can I help to get this implemented. > > Can you try with this patch applied [1]? Sorry, wrong patch. Can you try this one [1] instead? [1]http://code.bulix.org/pkfhmi-135875