From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] MTD NAND: Fix ECC errors in au1550nd.c
Date: Tue, 04 Oct 2005 15:53:51 +0400 [thread overview]
Message-ID: <43426D4F.2000400@ru.mvista.com> (raw)
In-Reply-To: <1128381010.13057.16.camel@tglx.tec.linutronix.de>
Thomas, thanks for reviewing this.
I asked the intern who did this work to clarify some points more preciously.
My comments and understanding of the situation is below.
Thomas Gleixner wrote:
> On Mon, 2005-10-03 at 17:22 +0400, Vitaly Bordug wrote:
>
>>David,
>>This patch fixes ECC errors by automatic CS assertion in the driver.
>>We still use manual drive of CS only during READ CYCLE and READ OOB
>>CYCLE, while overriding CS right after third address byte latch and
>>finishing override after first data byte read.
>>
>> From the Nand read page cycle timings (Toshiba Datasheet)
>
>
> Come on. I know those data sheets quite well and there is more than one.
> Which chip type (Manufacturer part Nr) are you using ?
>
TC58DVM92A1FT00
>
>>- we have to
>>keep CS active from third address byte latch to the end of the cycle
>
>
> Thats a known issue and the controller has worked with those chips
> before.
>
Actually, yes, a sort of. The issue was in some bytes lost during read
cycles (ECC errors reported) when PCMCIA (board AMD Alchemy 1550) is
active. This does not take place when 4 CS drives happen - as shown on
the timing diagram - e.g.
cs: \__/\__/\__/\__/\_<CS low>______ [works fine]
^
asserted by SoC controller
unchanged code:
cs:\______________/\_[PCMCIA driver steals bytes ]...
^
asserted by SoC controller
>
>>It seems that static controller drives CS to low after fourth address
>>byte latch - this interrupts the read cycle.
>
>
> It seems ?
>
> "drives CS to low ?" CS is active low.
>
>
>>We must manually keep CS in active state
>
>
> So whats active state: low or high or high-Z ?
>
The developer of this code will provide detailed description of the
situation.
>
>>from third address byte latch
>>to second data byte read, not during all read page cycles. And when we
>>drive CS manualy - we have to disable interrupts to prevent simultaneous
>>CS-s activation (NAND, PCMCIA,NOR CS).
>
>
> Oh well. Disable interrupts with cli().
>
> Have your Makefiles a builtin -Wignore ?
>
Heh, how could I miss this crap... Really funny
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2005-10-04 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 13:22 [PATCH] MTD NAND: Fix ECC errors in au1550nd.c Vitaly Bordug
2005-10-03 23:10 ` Thomas Gleixner
2005-10-04 11:53 ` Vitaly Bordug [this message]
2005-10-04 16:41 ` Thomas Gleixner
2005-10-05 16:18 ` Vitaly Bordug
2005-10-05 19:22 ` Vitaly Wool
2005-10-04 13:19 ` Vitaly Wool
2005-10-04 13:33 ` Vitaly Bordug
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=43426D4F.2000400@ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.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