From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [i.MX28 GPMI] problem overwriting all-0xff data in NAND
Date: Tue, 19 Jul 2011 15:36:02 +0200 [thread overview]
Message-ID: <20110719133602.GJ1951@pengutronix.de> (raw)
In-Reply-To: <20005.21635.427202.49313@ipc1.ka-ro>
> > >> 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?
> Maybe you are missing this patch:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2011-April/049105.html
> I sent it in April, but apparently it has not been integrated in
> mainline or the pengutronix git.
Well, just resend them; might be worth trying Shawn's comment, too (if
that reset is really needed). BTW they didn't help for my case :(
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110719/ed63c556/attachment.sig>
next prev parent reply other threads:[~2011-07-19 13:36 UTC|newest]
Thread overview: 21+ 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 [this message]
2011-07-20 2:18 ` Huang Shijie
2011-07-20 8:51 ` Wolfram Sang
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=20110719133602.GJ1951@pengutronix.de \
--to=w.sang@pengutronix.de \
--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