summaryrefslogtreecommitdiffstats
path: root/include/linux/mtd/nand.h
Commit message (Collapse)AuthorAgeFilesLines
* [MTD] NAND: Reorganize chip lockingThomas Gleixner2005-06-291-1/+4
| | | | | | | | | | | | | | | | | The code was wrong in several aspects. The locking order was inconsistent, the device aquire code did not reset a variable after a wakeup and the wakeup handling was not working for applications where multiple chips are sharing a single hardware controller. When a hardware controller is available the locking is now reduced to the hardware controller lock and the waitqueue is moved to the hardware controller structure in order to avoid a wake_up_all(). The problem was pointed out by Ben Dooks, who also found the missing variable reset as main cause for his deadlock problem. Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
* [MTD] NAND: Add Hynix to manufacturer listNicolas S. Dade2005-05-271-0/+1
| | | | | Signed-off-by: Nicolas S. Dade <daden@symbol.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
* [MTD] NAND: Skip bad block table scan on requestThomas Gleixner2005-05-231-2/+3
| | | | Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
* [MTD] NAND Add optional ECC status check callbackDavid A. Marlin2005-05-231-2/+14
| | | | | | | | Add optional hardware specific callback routine to perform extra error status checks on erase and write failures for devices with hardware ECC. Signed-off-by: David A. Marlin <dmarlin@redhat.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
* [MTD] NAND extended commands, badb block table autorefresh David A. Marlin2005-05-231-1/+26
| | | | | | | | Added extended commands for AG-AND device and added option for BBT_AUTO_REFRESH. Signed-off-by: David A. Marlin <dmarlin@redhat.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
* Linux-2.6.12-rc2v2.6.12-rc2Linus Torvalds2005-04-161-0/+469
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!