xref: /linux/drivers/memstick/core/Kconfig (revision c532de5a67a70f8533d495f8f2aaa9a0491c3ad0)
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# MemoryStick core configuration
4#
5
6comment "MemoryStick drivers"
7
8config MEMSTICK_UNSAFE_RESUME
9	bool "Allow unsafe resume (DANGEROUS)"
10	help
11	  If you say Y here, the MemoryStick layer will assume that all
12	  cards stayed in their respective slots during the suspend. The
13	  normal behaviour is to remove them at suspend and
14	  redetecting them at resume. Breaking this assumption will
15	  in most cases result in data corruption.
16
17	  This option is usually just for embedded systems which use
18	  a MemoryStick card for rootfs. Most people should say N here.
19
20config MSPRO_BLOCK
21	tristate "MemoryStick Pro block device driver"
22	depends on BLOCK
23	imply IOSCHED_BFQ
24	help
25	  Say Y here to enable the MemoryStick Pro block device driver
26	  support. This provides a block device driver, which you can use
27	  to mount the filesystem. Almost everyone wishing MemoryStick
28	  support should say Y or M here.
29
30config MS_BLOCK
31	tristate "MemoryStick Standard device driver"
32	depends on BLOCK
33	imply IOSCHED_BFQ
34	help
35	  Say Y here to enable the MemoryStick Standard device driver
36	  support. This provides a block device driver, which you can use
37	  to mount the filesystem.
38	  This driver works with old (bulky) MemoryStick and MemoryStick Duo
39	  but not PRO. Say Y if you have such card.
40	  Driver is new and not yet well tested, thus it can damage your card
41	  (even permanently)
42