Kyungmin Park wrote:
To use the mmc_test, it should be build before mmc_block.
Reported-by: Adrian Hunter <adrian.hunter@xxxxxxxxx>
I did not report this. I just pointed out that mmc_test
will not work if mmc_block has already been given all the
MMC devices.
You can always switch between mmc_test and mmc_block by
unbinding / binding e.g.
# ls -al /sys/bus/mmc/drivers/mmcblk
drwxr-xr-x 2 root 0 0 Jan 1 00:00 .
drwxr-xr-x 4 root 0 0 Jan 1 00:00 ..
--w------- 1 root 0 4096 Jan 1 00:01 bind
lrwxrwxrwx 1 root 0 0 Jan 1 00:01 mmc0:0001 -> ../../../../devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001
--w------- 1 root 0 4096 Jan 1 00:01 uevent
--w------- 1 root 0 4096 Jan 1 00:01 unbind
# echo mmc0:0001 > /sys/bus/mmc/drivers/mmcblk/unbind
# echo mmc0:0001 > /sys/bus/mmc/drivers/mmc_test/bind
[ 128.221313] mmc_test mmc0:0001: Card claimed for testing.
I suggest adding explanation to the Kconfig help text for
MMC_TEST and also the module decription in drivers/mmc/card/mmc_test.c
Signed-off-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
---
diff --git a/drivers/mmc/card/Makefile b/drivers/mmc/card/Makefile
index 0d40751..9d50437 100644
--- a/drivers/mmc/card/Makefile
+++ b/drivers/mmc/card/Makefile
@@ -6,9 +6,9 @@ ifeq ($(CONFIG_MMC_DEBUG),y)
EXTRA_CFLAGS += -DDEBUG
endif
+obj-$(CONFIG_MMC_TEST) += mmc_test.o
obj-$(CONFIG_MMC_BLOCK) += mmc_block.o
mmc_block-objs := block.o queue.o
-obj-$(CONFIG_MMC_TEST) += mmc_test.o
obj-$(CONFIG_SDIO_UART) += sdio_uart.o
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
