Linux-2.6.12-rc2v2.6.12-rc2

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!

1 files changed, 89 insertions, 0 deletions

diff --git a/include/linux/mtd/flashchip.h b/include/linux/mtd/flashchip.h
new file mode 100644
index 000000000000..c66ba812bf90
--- /dev/null
+++ b/include/linux/mtd/flashchip.h
@@ -0,0 +1,89 @@
+
+/* 
+ * struct flchip definition
+ * 
+ * Contains information about the location and state of a given flash device 
+ *
+ * (C) 2000 Red Hat. GPLd.
+ *
+ * $Id: flashchip.h,v 1.15 2004/11/05 22:41:06 nico Exp $
+ *
+ */
+
+#ifndef __MTD_FLASHCHIP_H__
+#define __MTD_FLASHCHIP_H__
+
+/* For spinlocks. sched.h includes spinlock.h from whichever directory it
+ * happens to be in - so we don't have to care whether we're on 2.2, which
+ * has asm/spinlock.h, or 2.4, which has linux/spinlock.h 
+ */
+#include <linux/sched.h>
+
+typedef enum { 
+        FL_READY,
+        FL_STATUS,
+        FL_CFI_QUERY,
+        FL_JEDEC_QUERY,
+        FL_ERASING,
+        FL_ERASE_SUSPENDING,
+        FL_ERASE_SUSPENDED,
+        FL_WRITING,
+        FL_WRITING_TO_BUFFER,
+        FL_WRITE_SUSPENDING,
+        FL_WRITE_SUSPENDED,
+        FL_PM_SUSPENDED,
+        FL_SYNCING,
+        FL_UNLOADING,
+        FL_LOCKING,
+        FL_UNLOCKING,
+        FL_POINT,
+        FL_XIP_WHILE_ERASING,
+        FL_XIP_WHILE_WRITING,
+        FL_UNKNOWN
+} flstate_t;
+
+
+
+/* NOTE: confusingly, this can be used to refer to more than one chip at a time, 
+   if they're interleaved.  This can even refer to individual partitions on
+   the same physical chip when present. */
+
+struct flchip {
+        unsigned long start; /* Offset within the map */
+        //      unsigned long len;
+        /* We omit len for now, because when we group them together
+           we insist that they're all of the same size, and the chip size
+           is held in the next level up. If we get more versatile later,
+           it'll make it a damn sight harder to find which chip we want from
+           a given offset, and we'll want to add the per-chip length field
+           back in.
+        */
+        int ref_point_counter;
+        flstate_t state;
+        flstate_t oldstate;
+
+        int write_suspended:1;
+        int erase_suspended:1;
+        unsigned long in_progress_block_addr;
+
+        spinlock_t *mutex;
+        spinlock_t _spinlock; /* We do it like this because sometimes they'll be shared. */
+        wait_queue_head_t wq; /* Wait on here when we're waiting for the chip
+                             to be ready */
+        int word_write_time;
+        int buffer_write_time;
+        int erase_time;
+
+        void *priv;
+};
+
+/* This is used to handle contention on write/erase operations
+   between partitions of the same physical chip. */
+struct flchip_shared {
+        spinlock_t lock;
+        struct flchip *writing;
+        struct flchip *erasing;
+};
+
+
+#endif /* __MTD_FLASHCHIP_H__ */