xref: /linux/drivers/memstick/core/Kconfig (revision baf8532a147d5b76681ce040e2c8f25a3f0e718d)
1*baf8532aSAlex Dubov#
2*baf8532aSAlex Dubov# MemoryStick core configuration
3*baf8532aSAlex Dubov#
4*baf8532aSAlex Dubov
5*baf8532aSAlex Dubovcomment "MemoryStick drivers"
6*baf8532aSAlex Dubov
7*baf8532aSAlex Dubovconfig MEMSTICK_UNSAFE_RESUME
8*baf8532aSAlex Dubov        bool "Allow unsafe resume (DANGEROUS)"
9*baf8532aSAlex Dubov        help
10*baf8532aSAlex Dubov          If you say Y here, the MemoryStick layer will assume that all
11*baf8532aSAlex Dubov          cards stayed in their respective slots during the suspend. The
12*baf8532aSAlex Dubov          normal behaviour is to remove them at suspend and
13*baf8532aSAlex Dubov          redetecting them at resume. Breaking this assumption will
14*baf8532aSAlex Dubov          in most cases result in data corruption.
15*baf8532aSAlex Dubov
16*baf8532aSAlex Dubov          This option is usually just for embedded systems which use
17*baf8532aSAlex Dubov          a MemoryStick card for rootfs. Most people should say N here.
18*baf8532aSAlex Dubov
19*baf8532aSAlex Dubovconfig MSPRO_BLOCK
20*baf8532aSAlex Dubov	tristate "MemoryStick Pro block device driver"
21*baf8532aSAlex Dubov	depends on BLOCK
22*baf8532aSAlex Dubov	help
23*baf8532aSAlex Dubov	  Say Y here to enable the MemoryStick Pro block device driver
24*baf8532aSAlex Dubov	  support. This provides a block device driver, which you can use
25*baf8532aSAlex Dubov	  to mount the filesystem. Almost everyone wishing MemoryStick
26*baf8532aSAlex Dubov	  support should say Y or M here.
27