summaryrefslogtreecommitdiffstats
path: root/include/linux/mtd
diff options
context:
space:
mode:
authorBarry Song <21cnbao@gmail.com>2010-01-15 15:50:14 +0800
committerDavid Woodhouse <David.Woodhouse@intel.com>2010-08-08 12:28:15 +0100
commit78ef7fab0eb0a5b159842bac89aed74bb0aa7bfe (patch)
tree98aff2083703762b75e8ecb7e0e8a27ec9c8df9a /include/linux/mtd
parent73ee5760253dc8893502e19a9cb118d25dab21ec (diff)
downloadtalos-op-linux-78ef7fab0eb0a5b159842bac89aed74bb0aa7bfe.tar.gz
talos-op-linux-78ef7fab0eb0a5b159842bac89aed74bb0aa7bfe.zip
mtd-physmap: add support users can assign the probe type in board files
There are three reasons to add this support: 1. users probably know the interface type of their flashs, then probe can be faster if they give the right type in platform data since wrong types will not be detected. 2. sometimes, detecting can cause destory to system. For example, for kernel XIP, detecting can cause NOR enter a mode instructions can not be fetched right, which will make kernel crash. 3. For a new probe which is not listed in the rom_probe_types, if users assign it in board files, physmap can still probe it. Signed-off-by: Barry Song <21cnbao@gmail.com> Signed-off-by: Mike Frysinger <vapier.adi@gmail.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'include/linux/mtd')
-rw-r--r--include/linux/mtd/physmap.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/mtd/physmap.h b/include/linux/mtd/physmap.h
index 76f7cabf07d3..bcfd9f777454 100644
--- a/include/linux/mtd/physmap.h
+++ b/include/linux/mtd/physmap.h
@@ -25,6 +25,7 @@ struct physmap_flash_data {
void (*set_vpp)(struct map_info *, int);
unsigned int nr_parts;
unsigned int pfow_base;
+ char *probe_type;
struct mtd_partition *parts;
};
OpenPOWER on IntegriCloud