5ff391d8ac
Now that omap2420 is using hwmod for MMC, this code is omap1 only used on omap1. Signed-off-by: Tony Lindgren <tony@atomide.com>
92 lines
2.7 KiB
C
92 lines
2.7 KiB
C
/*
|
|
* linux/arch/arm/plat-omap/devices.c
|
|
*
|
|
* Common platform device setup/initialization for OMAP1 and OMAP2
|
|
*
|
|
* This program is free software; you can redistribute it and/or modify
|
|
* it under the terms of the GNU General Public License as published by
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
* (at your option) any later version.
|
|
*/
|
|
#include <linux/gpio.h>
|
|
#include <linux/module.h>
|
|
#include <linux/kernel.h>
|
|
#include <linux/init.h>
|
|
#include <linux/platform_device.h>
|
|
#include <linux/io.h>
|
|
#include <linux/slab.h>
|
|
#include <linux/memblock.h>
|
|
|
|
#include <mach/hardware.h>
|
|
#include <asm/mach-types.h>
|
|
#include <asm/mach/map.h>
|
|
#include <asm/memblock.h>
|
|
|
|
#include <plat/tc.h>
|
|
#include <plat/board.h>
|
|
#include <plat/mmc.h>
|
|
#include <plat/menelaus.h>
|
|
#include <plat/omap44xx.h>
|
|
|
|
/*-------------------------------------------------------------------------*/
|
|
|
|
#if defined(CONFIG_HW_RANDOM_OMAP) || defined(CONFIG_HW_RANDOM_OMAP_MODULE)
|
|
|
|
#ifdef CONFIG_ARCH_OMAP2
|
|
#define OMAP_RNG_BASE 0x480A0000
|
|
#else
|
|
#define OMAP_RNG_BASE 0xfffe5000
|
|
#endif
|
|
|
|
static struct resource rng_resources[] = {
|
|
{
|
|
.start = OMAP_RNG_BASE,
|
|
.end = OMAP_RNG_BASE + 0x4f,
|
|
.flags = IORESOURCE_MEM,
|
|
},
|
|
};
|
|
|
|
static struct platform_device omap_rng_device = {
|
|
.name = "omap_rng",
|
|
.id = -1,
|
|
.num_resources = ARRAY_SIZE(rng_resources),
|
|
.resource = rng_resources,
|
|
};
|
|
|
|
static void omap_init_rng(void)
|
|
{
|
|
(void) platform_device_register(&omap_rng_device);
|
|
}
|
|
#else
|
|
static inline void omap_init_rng(void) {}
|
|
#endif
|
|
|
|
/*
|
|
* This gets called after board-specific INIT_MACHINE, and initializes most
|
|
* on-chip peripherals accessible on this board (except for few like USB):
|
|
*
|
|
* (a) Does any "standard config" pin muxing needed. Board-specific
|
|
* code will have muxed GPIO pins and done "nonstandard" setup;
|
|
* that code could live in the boot loader.
|
|
* (b) Populating board-specific platform_data with the data drivers
|
|
* rely on to handle wiring variations.
|
|
* (c) Creating platform devices as meaningful on this board and
|
|
* with this kernel configuration.
|
|
*
|
|
* Claiming GPIOs, and setting their direction and initial values, is the
|
|
* responsibility of the device drivers. So is responding to probe().
|
|
*
|
|
* Board-specific knowledge like creating devices or pin setup is to be
|
|
* kept out of drivers as much as possible. In particular, pin setup
|
|
* may be handled by the boot loader, and drivers should expect it will
|
|
* normally have been done by the time they're probed.
|
|
*/
|
|
static int __init omap_init_devices(void)
|
|
{
|
|
/* please keep these calls, and their implementations above,
|
|
* in alphabetical order so they're easier to sort through.
|
|
*/
|
|
omap_init_rng();
|
|
return 0;
|
|
}
|
|
arch_initcall(omap_init_devices);
|