CONFIG_MMC_UNSAFE_RESUME: Assume MMC/SD cards are non-removable (DANGEROUS)

General informations

The Linux kernel configuration item CONFIG_MMC_UNSAFE_RESUME has multiple definitions:

Assume MMC/SD cards are non-removable (DANGEROUS) found in drivers/mmc/core/Kconfig

The configuration item CONFIG_MMC_UNSAFE_RESUME:

• prompt: Assume MMC/SD cards are non-removable (DANGEROUS)
• type: bool
• depends on: (none)
• defined in drivers/mmc/core/Kconfig
• found in Linux kernels: 2.6.33–2.6.39, 3.0–3.14

Help text

If you say Y here, the MMC layer will assume that all cards stayed in their respective slots during the suspend. The normal behaviour is to remove them at suspend and redetecting them at resume. Breaking this assumption will in most cases result in data corruption.

This option is usually just for embedded systems which use a MMC/SD card for rootfs. Most people should say N here.

This option sets a default which can be overridden by the module parameter "removable=0" or "removable=1".

Allow unsafe resume (DANGEROUS) found in drivers/mmc/core/Kconfig

The configuration item CONFIG_MMC_UNSAFE_RESUME:

• prompt: Allow unsafe resume (DANGEROUS)
• type: bool
• depends on: (none)
• defined in drivers/mmc/core/Kconfig
• found in Linux kernels: 2.6.22–2.6.32

Help text

If you say Y here, the MMC layer will assume that all cards stayed in their respective slots during the suspend. The normal behaviour is to remove them at suspend and redetecting them at resume. Breaking this assumption will in most cases result in data corruption.

This option is usually just for embedded systems which use a MMC/SD card for rootfs. Most people should say N here.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: