public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Tobi Wulff <Tobi.Wulff@alliedtelesis.co.nz>,
	"boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>
Subject: Re: NAND timeout issues with blank chip and Marvell NFC
Date: Wed, 25 Apr 2018 15:32:52 +0200	[thread overview]
Message-ID: <20180425153252.210a0b1e@xps13> (raw)
In-Reply-To: <cf834bbf9ac14cfc8ad07e4921245f6f@svr-chch-ex1.atlnz.lc>

Hi Chris,

On Tue, 24 Apr 2018 05:31:39 +0000, Chris Packham
<Chris.Packham@alliedtelesis.co.nz> wrote:

> Hi,
> 
> We're in the process of qualifying new NAND chips (Macronix 
> MX30LF2G18AC) for one of our Armada-385 based devices and we're 
> experiencing some long startup times on units with factory fresh NAND 
> chips. Anecdotally I think I've also seen this behaviour on the old 
> chips as well (Micron MT29F2G08ABAEAWP-ITX:E).
> 
> On 4.17.0-rc2 with the newly re-written NAND infrastructure we see
> 
> nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
> nand: Macronix MX30LF2G18AC
> nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> marvell-nfc f10d0000.flash: Timeout on CMDD (NDSR: 0x00000080)
> marvell-nfc f10d0000.flash: Timeout on CMDD (NDSR: 0x00000280)

I just sent a patch (and forgot to add you in copy) [1]. This should
remove these two timeouts. I don't think it will improve your (first)
boot time though.

The patch is within a short series fixing various portion of the same
chunk of code, I suggest you to take them all.

[1] http://lists.infradead.org/pipermail/linux-mtd/2018-April/080537.html

Regards,
Miquèl

-- 
Miquel Raynal, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-04-25 13:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24  5:31 NAND timeout issues with blank chip and Marvell NFC Chris Packham
2018-04-24 15:49 ` Steve deRosier
2018-04-24 16:08   ` Miquel Raynal
2018-04-25 21:22     ` Chris Packham
2018-04-26  1:40       ` Chris Packham
2018-04-26  5:16         ` Chris Packham
2018-04-26  6:06           ` Boris Brezillon
2018-04-26  6:21             ` Boris Brezillon
2018-04-26  7:03           ` Miquel Raynal
2018-04-26 22:43             ` Chris Packham
2018-04-27  4:30               ` Chris Packham
2018-04-27  6:16                 ` Boris Brezillon
2018-05-02 15:28               ` Miquel Raynal
2018-05-02 22:12                 ` Chris Packham
2018-04-25 21:16   ` Chris Packham
2018-04-25 13:32 ` Miquel Raynal [this message]

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=20180425153252.210a0b1e@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=Tobi.Wulff@alliedtelesis.co.nz \
    --cc=boris.brezillon@bootlin.com \
    --cc=linux-mtd@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