From: Vikram Narayanan <vikram186@gmail.com>
To: Stefan Roese <sr@denx.de>
Cc: Huang Shijie <b32955@freescale.com>, linux-mtd@lists.infradead.org
Subject: Re: mtd_oobtest fails with GPMI-NAND
Date: Mon, 13 May 2013 22:13:10 +0530 [thread overview]
Message-ID: <5191181E.5060209@gmail.com> (raw)
In-Reply-To: <51909DF1.4060201@denx.de>
On 5/13/2013 1:31 PM, Stefan Roese wrote:
> On 05/13/2013 04:51 AM, Huang Shijie wrote:
>>>> Also, I don't have enough spare boards to sacrifice it for mtd_torture test.
>>> Yes, I can understand this.
>>>
>>> Huang, do you have any idea on how to proceed here? What else
>>> could/should we test? Any ideas/hints?
>>
>> Currently, the kernel supports three imx6 boards for the gpmi-nand:
>> imx6q-arm2, imx6q-sabreauto, imx6dl-sabareauto.
>>
>> I am afraid your board is none of them. I doubt your board is not
>> correctly configrated with
>> some timing or signals.
>
> Correct, our board is a custom imx6 board. Basically NAND is working
> just fine (UBI/UBIFS works basically). This board even boots from NAND.
> So at least the pin muxing has to be correct.
If you are missing something very fundamental like the pinmux, I really
wonder how the board would boot. So I'd say, you got your basic settings
right.
> Please correct me if I'm wrong, but from my understanding the Linux GPMI
> NAND driver configures the timings. So this is not board platform code
> related but NAND driver related.
>
> Do you have any hints where to "tune/change" some values (timing or
> signal related) to fix this error?
Not sure if this will fix your errors. There is a struct timing in the
driver (Just give a grep). Update that structure with the timings given
in your NAND datasheet.
HTH,
Vikram
prev parent reply other threads:[~2013-05-13 16:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 16:52 mtd_oobtest fails with GPMI-NAND Vikram Narayanan
2013-01-21 2:12 ` Huang Shijie
2013-01-28 2:39 ` Vikram Narayanan
2013-01-28 3:20 ` Huang Shijie
2013-01-28 17:04 ` Vikram Narayanan
2013-01-29 2:06 ` Huang Shijie
2013-01-29 2:26 ` Vikram Narayanan
2013-01-29 2:36 ` Huang Shijie
2013-01-29 16:28 ` Vikram Narayanan
2013-01-30 2:27 ` Huang Shijie
2013-02-02 6:41 ` Vikram Narayanan
2013-02-02 7:42 ` Huang Shijie
2013-02-02 7:46 ` Huang Shijie
2013-05-08 14:33 ` Stefan Roese
2013-05-09 12:30 ` Vikram Narayanan
2013-05-10 6:20 ` Stefan Roese
2013-05-12 12:10 ` Vikram Narayanan
2013-05-12 15:09 ` Stefan Roese
2013-05-13 16:38 ` Vikram Narayanan
2013-05-13 2:51 ` Huang Shijie
2013-05-13 8:01 ` Stefan Roese
2013-05-13 9:01 ` Huang Shijie
2013-05-13 9:22 ` Stefan Roese
2013-05-13 9:34 ` Huang Shijie
2013-05-13 10:02 ` Stefan Roese
2013-05-14 2:09 ` Huang Shijie
2013-05-14 2:11 ` Huang Shijie
2013-05-13 16:51 ` Vikram Narayanan
2013-05-14 2:23 ` Huang Shijie
2013-05-14 2:33 ` Vikram Narayanan
2013-05-14 2:47 ` Huang Shijie
2013-05-13 16:43 ` Vikram Narayanan [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=5191181E.5060209@gmail.com \
--to=vikram186@gmail.com \
--cc=b32955@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=sr@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.