1 files changed, 46 insertions, 0 deletions
diff --git a/apps/examples/mtdpart/Kconfig b/apps/examples/mtdpart/Kconfig
new file mode 100644
index 000000000..363b6091f
--- /dev/null
+++ b/apps/examples/mtdpart/Kconfig
@@ -0,0 +1,46 @@
+#
+# For a description of the syntax of this configuration file,
+# see misc/tools/kconfig-language.txt.
+#
+
+config EXAMPLES_MTDPART
+	bool "MTD partition test"
+	default n
+	---help---
+		Enable the MTD partition test example
+
+if EXAMPLES_MTDPART
+
+config EXAMPLES_MTDPART_ARCHINIT
+	bool "Architecture-specific initialization"
+	default n
+	---help---
+		The default is to use the RAM MTD device at drivers/mtd/rammtd.c.
+		But an architecture-specific MTD driver can be used instead by
+		defining EXAMPLES_MTDPART_ARCHINIT.  In this case, the
+		initialization logic will call mtdpart_archinitialize() to obtain
+		the MTD driver instance.
+
+config EXAMPLES_MTDPART_NEBLOCKS
+	int "Number of erase blocks (simulated)"
+	default 32
+	depends on !EXAMPLES_MTDPART_ARCHINIT
+	---help---
+		When EXAMPLES_MTDPART_ARCHINIT is not defined, this test will use
+		the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH.  In
+		this case, this value must be provided to give the nubmer of erase
+		blocks in MTD RAM device.
+
+		The size of the allocated RAM drive will be:
+
+			EXAMPLES_MTDPART_ERASESIZE * EXAMPLES_MTDPART_NEBLOCKS
+
+config EXAMPLES_MTDPART_NPARTITIONS
+	int "Number of partitions"
+	default 3
+	---help---
+		This setting provides the number of partitions to test.  The
+		test will divide the reported size of the MTD device into equal-
+		sized sub-regions for each test partition.
+
+endif