From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: sebastian.hesselbarth@gmail.com,
ezequiel.garcia@free-electrons.com, dwmw2@infradead.org,
computersforpeace@gmail.com, robert.jarzmik@free.fr,
zmxu@marvell.com, jszhang@marvell.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>
Subject: Re: [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup
Date: Thu, 22 Oct 2015 17:12:59 +0200 [thread overview]
Message-ID: <20151022171259.57581575@free-electrons.com> (raw)
In-Reply-To: <1445416144-9194-1-git-send-email-antoine.tenart@free-electrons.com>
Hello Antoine,
On Wed, 21 Oct 2015 10:28:59 +0200, Antoine Tenart wrote:
> Antoine Tenart (5):
> mtd: pxa3xx: prepare allowing compile test
> mtd: nand: allow compile test of MTD_NAND_PXA3xx
> mtd: pxa3xx_nand: add helpers to setup the timings
> mtd: pxa3xx_nand: rework flash detection and timing setup
> mtd: pxa3xx_nand: clean up the pxa3xx timings
I tested your series on Armada 375 DB, which uses the same pxa3xx
driver, but with the Armada 370 variant.
With the current Device Tree which has nand,keep-config to keep the
timing configuration from the bootloader, I don't see any problem, so
there is no regression introduced by your series, at least on this
platform.
However, when I remove nand,keep-config to use the ONFI timings from
the NAND, then things work fine (I can mount a UBIFS root filesystem),
but there is a weird:
pxa3xx-nand f10d0000.nand: Wait time out!!!
After investigating a bit, the following steps occur:
* The timings are configured as ONFI mode 0
* Reset command is sent to the NAND (0xff), two times in a row.
* READID command is sent to the NAND (0x90), three times in a row.
* PARAM command is sent to the NAND (0xec) and it times out
* The NAND is properly identified, and the timings are reconfigured as
ONFI mode 5
* Everything seems to work fine
In the current implementation of the driver, the nand_cmdfunc()
function is used for all the identification phase, and only switched
later to nand_cmdfunc_extended() if we are on an Armada 370/XP variant
(which Armada 375 is) and the page size is higher than PAGE_CHUNK_SIZE.
So the timeout occurs when nand_cmdfunc() is in-use. I've tried forcing
to use nand_cmdfunc_extended() from the beginning, but it times out
similarly in this function.
Since the driver works fine, maybe the PARAM command has worked
properly, but just times out for some reason. It would be good to
understand why.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-22 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:28 Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 1/5] mtd: pxa3xx: prepare allowing compile test Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 2/5] mtd: nand: allow compile test of MTD_NAND_PXA3xx Antoine Tenart
2015-10-26 18:34 ` Brian Norris
2015-10-21 8:29 ` [PATCH v4 3/5] mtd: pxa3xx_nand: add helpers to setup the timings Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 4/5] mtd: pxa3xx_nand: rework flash detection and timing setup Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 5/5] mtd: pxa3xx_nand: clean up the pxa3xx timings Antoine Tenart
2015-10-22 15:12 ` Thomas Petazzoni [this message]
2015-10-22 15:22 ` [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup Ezequiel Garcia
2015-10-22 15:42 ` Thomas Petazzoni
2015-11-02 15:49 ` Ezequiel Garcia
2015-10-25 20:53 ` Robert Jarzmik
2015-10-26 13:50 ` Ezequiel Garcia
2015-10-26 18:38 ` Brian Norris
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=20151022171259.57581575@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zmxu@marvell.com \
/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
all inboxes | Powered by JetHome®