litmus-rt.git - The LITMUS^RT kernel.

diff options

author	Olof Johansson <olof@lixom.net>	2012-11-30 02:05:32 -0500
committer	Olof Johansson <olof@lixom.net>	2012-11-30 02:16:12 -0500
commit	73f14f6d007df1596da7cea9113084acfe846b8f (patch)
tree	91f65f082a0491df206400b208d5e888fe055479 /arch/arm/mach-imx/iram_alloc.c
parent	c8a1ceccf394b2f99feed2b702732140e9f0f92d (diff)

ARM: omap: fix typo on timer cleanup

Fix 32 vs 32k typo: arch/arm/mach-omap2/timer.c: In function 'omap4_local_timer_init': arch/arm/mach-omap2/timer.c:633:2: error: implicit declaration of function 'omap4_sync32_timer_init' [-Werror=implicit-function-declaration] arch/arm/mach-omap2/timer.c: At top level: arch/arm/mach-omap2/timer.c:610:2: warning: 'omap4_sync32k_timer_init' defined but not used [-Wunused-function] Also, mark the omap4_local_timer_init() stub as __init (and take off the explicit inline and let the compiler do the work instead). Signed-off-by: Olof Johansson <olof@lixom.net> Cc: Tony Lindgren <tony@atomide.com> Cc: Igor Grinberg <grinberg@compulab.co.il>

Diffstat (limited to 'arch/arm/mach-imx/iram_alloc.c')

0 files changed, 0 insertions, 0 deletions

# drivers/mtd/maps/Kconfig # $Id: Kconfig,v 1.42 2005/01/05 16:59:50 dwmw2 Exp $ menu "Mapping drivers for chip access" depends on MTD!=n config MTD_COMPLEX_MAPPINGS bool "Support non-linear mappings of flash chips" depends on MTD help This causes the chip drivers to allow for complicated paged mappings of flash chips. config MTD_PHYSMAP tristate "CFI Flash device in physical memory map" depends on MTD_CFI help This provides a 'mapping' driver which allows the CFI probe and command set driver code to communicate with flash chips which are mapped physically into the CPU's memory. You will need to configure the physical address and size of the flash chips on your particular board as well as the bus width, either statically with config options or at run-time. config MTD_PHYSMAP_START hex "Physical start address of flash mapping" depends on MTD_PHYSMAP default "0x8000000" help This is the physical memory location at which the flash chips are mapped on your particular target board. Refer to the memory map which should hopefully be in the documentation for your board. Ignore this option if you use run-time physmap configuration (i.e., run-time calling physmap_configure()). config MTD_PHYSMAP_LEN hex "Physical length of flash mapping" depends on MTD_PHYSMAP default "0x4000000" help This is the total length of the mapping of the flash chips on your particular board. If there is space, or aliases, in the physical memory map between the chips, this could be larger than the total amount of flash present. Refer to the memory map which should hopefully be in the documentation for your board. Ignore this option if you use run-time physmap configuration (i.e., run-time calling physmap_configure()). config MTD_PHYSMAP_BANKWIDTH int "Bank width in octets" depends on MTD_PHYSMAP default "2" help This is the total width of the data bus of the flash devices in octets. For example, if you have a data bus width of 32 bits, you would set the bus width octect value to 4. This is used internally by the CFI drivers. Ignore this option if you use run-time physmap configuration (i.e., run-time calling physmap_configure()). config MTD_SUN_UFLASH tristate "Sun Microsystems userflash support" depends on (SPARC32 || SPARC64) && MTD_CFI help This provides a 'mapping' driver which supports the way in which user-programmable flash chips are connected on various Sun Microsystems boardsets. This driver will require CFI support in the kernel, so if you did not enable CFI previously, do that now. config MTD_PNC2000 tristate "CFI Flash device mapped on Photron PNC-2000" depends on X86 && MTD_CFI && MTD_PARTITIONS help PNC-2000 is the name of Network Camera product from PHOTRON Ltd. in Japan. It uses CFI-compliant flash. config MTD_SC520CDP tristate "CFI Flash device mapped on AMD SC520 CDP" depends on X86 && MTD_CFI help The SC520 CDP board has two banks of CFI-compliant chips and one Dual-in-line JEDEC chip. This 'mapping' driver supports that arrangement, implementing three MTD devices. config MTD_NETSC520 tristate "CFI Flash device mapped on AMD NetSc520" depends on X86 && MTD_CFI && MTD_PARTITIONS help This enables access routines for the flash chips on the AMD NetSc520 demonstration board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. config MTD_TS5500 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" depends on X86 && MTD_JEDECPROBE && MTD_PARTITIONS help This provides a driver for the on-board flash of the Technologic System's TS-5500 board. The flash is split into 3 partitions which are accessed as separate MTD devices. mtd0 and mtd2 are the two BIOS drives. Unfortunately the BIOS uses a proprietary flash translation layer from General Software, which is not supported (the drives cannot be mounted). You can create your own file system (jffs for example), but the BIOS won't be able to boot from it. mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. Note that jumper 3 ("Write Enable Drive A") must be set otherwise detection won't succeeed. config MTD_SBC_GXX tristate "CFI Flash device mapped on Arcom SBC-GXx boards" depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS help This provides a driver for the on-board flash of Arcom Control Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. By default the flash is split into 3 partitions which are accessed as separate MTD devices. This board utilizes Intel StrataFlash. More info at <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. config MTD_ELAN_104NC tristate "CFI Flash device mapped on Arcom ELAN-104NC" depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS help This provides a driver for the on-board flash of the Arcom Control System's ELAN-104NC development board. By default the flash is split into 3 partitions which are accessed as separate MTD devices. This board utilizes Intel StrataFlash. More info at <http://www.arcomcontrols.com/products/icp/pc104/processors/ELAN104NC.htm>. config MTD_LUBBOCK tristate "CFI Flash device mapped on Intel Lubbock XScale eval board" depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS help This provides a driver for the on-board flash of the Intel 'Lubbock' XScale evaluation board. config MTD_OCTAGON tristate "JEDEC Flash device mapped on Octagon 5066 SBC" depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS help This provides a 'mapping' driver which supports the way in which the flash chips are connected in the Octagon-5066 Single Board Computer. More information on the board is available at <http://www.octagonsystems.com/CPUpages/5066.html>. config MTD_VMAX tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301" depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS help This provides a 'mapping' driver which supports the way in which the flash chips are connected in the Tempustech VMAX SBC301 Single Board Computer. More information on the board is available at <http://www.tempustech.com/>. config MTD_SCx200_DOCFLASH tristate "Flash device mapped with DOCCS on NatSemi SCx200" depends on SCx200 && MTD_CFI && MTD_PARTITIONS help Enable support for a flash chip mapped using the DOCCS signal on a National Semiconductor SCx200 processor. If you don't know what to do here, say N. If compiled as a module, it will be called scx200_docflash. config MTD_AMD76XROM tristate "BIOS flash chip on AMD76x southbridge" depends on X86 && MTD_JEDECPROBE help Support for treating the BIOS flash chip on AMD76x motherboards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. config MTD_ICHXROM tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" depends on X86 && MTD_JEDECPROBE help Support for treating the BIOS flash chip on ICHX motherboards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. config MTD_SCB2_FLASH tristate "BIOS flash chip on Intel SCB2 boards" depends on X86 && MTD_JEDECPROBE help Support for treating the BIOS flash chip on Intel SCB2 boards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. config MTD_TSUNAMI tristate "Flash chips on Tsunami TIG bus" depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS help Support for the flash chip on Tsunami TIG bus. config MTD_LASAT tristate "Flash chips on LASAT board" depends on LASAT help Support for the flash chips on the Lasat 100 and 200 boards. config MTD_NETtel tristate "CFI flash device on SnapGear/SecureEdge" depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE help Support for flash chips on NETtel/SecureEdge/SnapGear boards. config MTD_PB1XXX tristate "Flash devices on Alchemy PB1xxx boards" depends on MIPS && ( MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 ) help Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards config MTD_PB1XXX_BOOT bool "PB1x00 boot flash device" depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 ) help Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board. You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use both banks. config MTD_PB1XXX_USER bool "PB1x00 user flash device" depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 ) default y if MTD_PB1XX_BOOT = n help Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board. You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use both banks. config MTD_PB1550 tristate "Flash devices on Alchemy PB1550 board" depends on MIPS && MIPS_PB1550 help Flash memory access on Alchemy Pb1550 board config MTD_PB1550_BOOT bool "PB1550 boot flash device" depends on MTD_PB1550 help Use the first of the two 64MiB flash banks on Pb1550 board. You can say 'Y' to both this and 'MTD_PB1550_USER' below, to use both banks. config MTD_PB1550_USER bool "PB1550 user flash device" depends on MTD_PB1550 default y if MTD_PB1550_BOOT = n help Use the second of the two 64MiB flash banks on Pb1550 board. You can say 'Y' to both this and 'MTD_PB1550_BOOT' above, to use both banks. config MTD_DB1550 tristate "Flash devices on Alchemy DB1550 board" depends on MIPS && MIPS_DB1550 help Flash memory access on Alchemy Db1550 board config MTD_DB1550_BOOT bool "DB1550 boot flash device" depends on MTD_DB1550 help Use the first of the two 64MiB flash banks on Db1550 board. You can say 'Y' to both this and 'MTD_DB1550_USER' below, to use both banks. config MTD_DB1550_USER bool "DB1550 user flash device" depends on MTD_DB1550 default y if MTD_DB1550_BOOT = n help Use the second of the two 64MiB flash banks on Db1550 board. You can say 'Y' to both this and 'MTD_DB1550_BOOT' above, to use both banks. config MTD_DILNETPC tristate "CFI Flash device mapped on DIL/Net PC" depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT help MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm> and <http://www.ssv-embedded.de/ssv/pc104/p170.htm> config MTD_DILNETPC_BOOTSIZE hex "Size of DIL/Net PC flash boot partition" depends on MTD_DILNETPC default "0x80000" help The amount of space taken up by the kernel or Etherboot on the DIL/Net PC flash chips. config MTD_L440GX tristate "BIOS flash chip on Intel L440GX boards" depends on X86 && MTD_JEDECPROBE help Support for treating the BIOS flash chip on Intel L440GX motherboards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. config MTD_SBC8240 tristate "Flash device on SBC8240" depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260 help Flash access on the SBC8240 board from Wind River. See


context:
space:
mode: