From: Huang Shijie <b32955@freescale.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
"Shawn Guo" <shawn.guo@freescale.com>,
"Lothar Waßmann" <LW@KARO-electronics.de>
Subject: Re: [i.MX28 GPMI] problem overwriting all-0xff data in NAND
Date: Wed, 20 Jul 2011 10:34:26 -0000 [thread overview]
Message-ID: <4E26AFF4.9000208@freescale.com> (raw)
In-Reply-To: <20110720085142.GA2377@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Hi,
>>>>>>> I am debugging the DMA bug now. and I will send it out when i fix it.
>>>>>>>
>>>>>> What sort of DMA bug?
>>>>>>
>>>>> The DMA may time-out. :(
>>>>>
>>>>> The DMA time-out may occur in two situations:
>>>>> [1] send a command DMA descriptor, see the nfc->send_command() function.
>>>>> [2] read the non-ecc data from nand, see the nfc->read_data() function.
>>>>>
>>>>> I don't know why. Maybe caused by the timing, or something else.
>>> I am confused. The send-command DMA timeout prevents any write for me.
>>> You guys surely would have noticed if you have been bitten as well. Does
>>> it depend on the NAND chip?
>> I think It does not depend on the NAND chip.
>> My test chip is Samsung K9G8G08U0M.
>> Sometimes, I can run a long time while there is no DMA timeout occurring;
>> Sometimes, the bug appears right away.
> For me, the bug always happens right away. So, if you need logs or debug
> output or can give me a pointer into some direction, I am glad to
> assist.
>
Thanks a lot. :)
I am trying to merge the two DMA descriptors into one in the send_command().
The original bsp code used only one DMA descriptor.
Huang Shijie
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
[-- Attachment #2: Type: text/html, Size: 2635 bytes --]
next prev parent reply other threads:[~2011-07-20 10:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 13:13 [i.MX28 GPMI] problem overwriting all-0xff data in NAND Lothar Waßmann
2011-07-18 14:56 ` Ivan Djelic
2011-07-19 5:59 ` Lothar Waßmann
2011-07-19 6:48 ` Ivan Djelic
2011-07-18 16:43 ` Shawn Guo
2011-07-19 2:12 ` Huang Shijie
2011-07-19 6:02 ` Lothar Waßmann
2011-07-19 7:03 ` Huang Shijie
2011-07-19 9:55 ` Lothar Waßmann
2011-07-19 13:36 ` Wolfram Sang
2011-07-20 2:18 ` Huang Shijie
2011-07-20 8:51 ` Wolfram Sang
2011-07-20 10:34 ` Huang Shijie [this message]
2011-07-20 4:55 ` Huang Shijie
2011-07-20 6:22 ` Lothar Waßmann
2011-07-20 5:16 ` Artem Bityutskiy
2011-07-20 5:19 ` Artem Bityutskiy
2011-07-19 6:00 ` Lothar Waßmann
2011-07-20 6:44 ` Huang Shijie
2011-07-20 8:10 ` Lothar Waßmann
2011-07-20 8:35 ` Artem Bityutskiy
2011-07-20 5:12 ` Artem Bityutskiy
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=4E26AFF4.9000208@freescale.com \
--to=b32955@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@freescale.com \
--cc=w.sang@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox