From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1163234AbdEXJhg (ORCPT ); Wed, 24 May 2017 05:37:36 -0400 Received: from gate2.alliedtelesis.co.nz ([202.36.163.20]:50612 "EHLO gate2.alliedtelesis.co.nz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1163202AbdEXJhD (ORCPT ); Wed, 24 May 2017 05:37:03 -0400 From: Chris Packham To: "linux-mtd@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Thomas Petazzoni CC: "ezequiel.garcia@free-electrons.com" , Boris Brezillon , Gregory Clement Subject: Re: pxa3xx-nand failing to find device on linux-next Thread-Topic: pxa3xx-nand failing to find device on linux-next Thread-Index: AQHS04VCDrK5tOKlGkCrPkXEtQfG7A== Date: Wed, 24 May 2017 09:36:56 +0000 Message-ID: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc> References: Accept-Language: en-NZ, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.32.1.10] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v4O9cDeE003519 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gate2.alliedtelesis.co.nz ([202.36.163.20]) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1dDSjO-00022F-4R for linux-mtd@lists.infradead.org; Wed, 24 May 2017 09:37:28 +0000 From: Chris Packham To: "linux-mtd@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Thomas Petazzoni CC: "ezequiel.garcia@free-electrons.com" , Boris Brezillon , Gregory Clement Subject: Re: pxa3xx-nand failing to find device on linux-next Date: Wed, 24 May 2017 09:36:56 +0000 Message-ID: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc> References: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 23/05/17 17:27, Chris Packham wrote:=0A= > Hi,=0A= >=0A= > I'm doing some testing on linux-next and I'm finding that my nand flash= =0A= > has disappeared.=0A= >=0A= > pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device=0A= > pxa3xx-nand f10d0000.flash: non-supported command ef=0A= > pxa3xx-nand f10d0000.flash: non-supported command ee=0A= > pxa3xx-nand f10d0000.flash: non-supported command ef=0A= > pxa3xx-nand f10d0000.flash: non-supported command ee=0A= > On-die ECC forcefully enabled, not supported=0A= > nand: No NAND device found=0A= > pxa3xx-nand f10d0000.flash: failed to scan nand at cs 0=0A= >=0A= > This was working around 4.11. I'll try to do some more digging tomorrow= =0A= > to narrow down a failure point but I thought I'd send this out now just= =0A= > in case it rings any bells.=0A= >=0A= > The board I'm using (DB-88F6820-AMC) is unfortunately out-of tree but it= =0A= > should be pretty close to the armada-388-db. I can make my dts available= =0A= > if it's helpful.=0A= =0A= Still works on 4.12-rc2. Fails on next-20170524.=0A= =0A= This appears to be due to commit b566d9c055de ("mtd: nand: add support =0A= for Micron on-die ECC"). Which based on the description seems intentional.= =0A= =0A= Since I have access to a hardware platform that has a micron flash with=0A= ECC forcefully enabled how can I help to get this implemented.=0A= From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris.Packham@alliedtelesis.co.nz (Chris Packham) Date: Wed, 24 May 2017 09:36:56 +0000 Subject: pxa3xx-nand failing to find device on linux-next References: Message-ID: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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.