From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: pxa3xx-nand failing to find device on linux-next
Date: Wed, 24 May 2017 13:23:01 +0200 [thread overview]
Message-ID: <20170524132301.12ad33d8@bbrezillon> (raw)
In-Reply-To: <2a79405e219b4c37ba00defbe4a0dfe4@svr-chch-ex1.atlnz.lc>
Hi Chris,
On Wed, 24 May 2017 09:36:56 +0000
Chris Packham <Chris.Packham@alliedtelesis.co.nz> 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]?
Thanks,
Boris
[1]http://code.bulix.org/eic5n9-135873
next prev parent reply other threads:[~2017-05-24 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 5:27 pxa3xx-nand failing to find device on linux-next Chris Packham
2017-05-24 9:36 ` Chris Packham
2017-05-24 11:23 ` Boris Brezillon [this message]
2017-05-24 11:25 ` Boris Brezillon
2017-05-24 22:03 ` Chris Packham
2017-05-24 22:36 ` Boris Brezillon
2017-05-24 22:58 ` Chris Packham
2017-05-25 6:17 ` Boris Brezillon
2017-05-25 22:12 ` Chris Packham
2017-05-26 12:12 ` Boris Brezillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170524132301.12ad33d8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).