9361401eb7
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
112 lines
3.1 KiB
Text
112 lines
3.1 KiB
Text
#
|
|
# MMC subsystem configuration
|
|
#
|
|
|
|
menu "MMC/SD Card support"
|
|
|
|
config MMC
|
|
tristate "MMC support"
|
|
help
|
|
MMC is the "multi-media card" bus protocol.
|
|
|
|
If you want MMC support, you should say Y here and also
|
|
to the specific driver for your MMC interface.
|
|
|
|
config MMC_DEBUG
|
|
bool "MMC debugging"
|
|
depends on MMC != n
|
|
help
|
|
This is an option for use by developers; most people should
|
|
say N here. This enables MMC core and driver debugging.
|
|
|
|
config MMC_BLOCK
|
|
tristate "MMC block device driver"
|
|
depends on MMC && BLOCK
|
|
default y
|
|
help
|
|
Say Y here to enable the MMC block device driver support.
|
|
This provides a block device driver, which you can use to
|
|
mount the filesystem. Almost everyone wishing MMC support
|
|
should say Y or M here.
|
|
|
|
config MMC_ARMMMCI
|
|
tristate "ARM AMBA Multimedia Card Interface support"
|
|
depends on ARM_AMBA && MMC
|
|
help
|
|
This selects the ARM(R) AMBA(R) PrimeCell Multimedia Card
|
|
Interface (PL180 and PL181) support. If you have an ARM(R)
|
|
platform with a Multimedia Card slot, say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_PXA
|
|
tristate "Intel PXA255 Multimedia Card Interface support"
|
|
depends on ARCH_PXA && MMC
|
|
help
|
|
This selects the Intel(R) PXA(R) Multimedia card Interface.
|
|
If you have a PXA(R) platform with a Multimedia Card slot,
|
|
say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_SDHCI
|
|
tristate "Secure Digital Host Controller Interface support (EXPERIMENTAL)"
|
|
depends on PCI && MMC && EXPERIMENTAL
|
|
help
|
|
This select the generic Secure Digital Host Controller Interface.
|
|
It is used by manufacturers such as Texas Instruments(R), Ricoh(R)
|
|
and Toshiba(R). Most controllers found in laptops are of this type.
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_OMAP
|
|
tristate "TI OMAP Multimedia Card Interface support"
|
|
depends on ARCH_OMAP && MMC
|
|
select TPS65010 if MACH_OMAP_H2
|
|
help
|
|
This selects the TI OMAP Multimedia card Interface.
|
|
If you have an OMAP board with a Multimedia Card slot,
|
|
say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_WBSD
|
|
tristate "Winbond W83L51xD SD/MMC Card Interface support"
|
|
depends on MMC && ISA_DMA_API
|
|
help
|
|
This selects the Winbond(R) W83L51xD Secure digital and
|
|
Multimedia card Interface.
|
|
If you have a machine with a integrated W83L518D or W83L519D
|
|
SD/MMC card reader, say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_AU1X
|
|
tristate "Alchemy AU1XX0 MMC Card Interface support"
|
|
depends on MMC && SOC_AU1200
|
|
help
|
|
This selects the AMD Alchemy(R) Multimedia card interface.
|
|
If you have a Alchemy platform with a MMC slot, say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_AT91RM9200
|
|
tristate "AT91RM9200 SD/MMC Card Interface support"
|
|
depends on ARCH_AT91RM9200 && MMC
|
|
help
|
|
This selects the AT91RM9200 MCI controller.
|
|
|
|
If unsure, say N.
|
|
|
|
config MMC_IMX
|
|
tristate "Motorola i.MX Multimedia Card Interface support"
|
|
depends on ARCH_IMX && MMC
|
|
help
|
|
This selects the Motorola i.MX Multimedia card Interface.
|
|
If you have a i.MX platform with a Multimedia Card slot,
|
|
say Y or M here.
|
|
|
|
If unsure, say N.
|
|
|
|
endmenu
|