2007-04-12 23:26:57 +08:00
|
|
|
/*
|
|
|
|
* Board-specific setup code for the ATNGW100 Network Gateway
|
|
|
|
*
|
|
|
|
* Copyright (C) 2005-2006 Atmel Corporation
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
*/
|
|
|
|
#include <linux/clk.h>
|
|
|
|
#include <linux/etherdevice.h>
|
2008-09-07 11:19:02 +08:00
|
|
|
#include <linux/gpio.h>
|
2008-06-13 03:18:05 +08:00
|
|
|
#include <linux/irq.h>
|
|
|
|
#include <linux/i2c.h>
|
2007-07-12 22:36:34 +08:00
|
|
|
#include <linux/i2c-gpio.h>
|
2007-04-12 23:26:57 +08:00
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/linkage.h>
|
|
|
|
#include <linux/platform_device.h>
|
|
|
|
#include <linux/types.h>
|
2007-07-08 18:49:53 +08:00
|
|
|
#include <linux/leds.h>
|
2007-04-12 23:26:57 +08:00
|
|
|
#include <linux/spi/spi.h>
|
2008-11-20 22:59:12 +08:00
|
|
|
#include <linux/atmel-mci.h>
|
2009-12-03 21:58:20 +08:00
|
|
|
#include <linux/usb/atmel_usba_udc.h>
|
2007-04-12 23:26:57 +08:00
|
|
|
|
|
|
|
#include <asm/io.h>
|
|
|
|
#include <asm/setup.h>
|
|
|
|
|
2008-08-05 19:57:38 +08:00
|
|
|
#include <mach/at32ap700x.h>
|
|
|
|
#include <mach/board.h>
|
|
|
|
#include <mach/init.h>
|
|
|
|
#include <mach/portmux.h>
|
2007-04-12 23:26:57 +08:00
|
|
|
|
2008-03-17 21:55:06 +08:00
|
|
|
/* Oscillator frequencies. These are board-specific */
|
|
|
|
unsigned long at32_board_osc_rates[3] = {
|
|
|
|
[0] = 32768, /* 32.768 kHz on RTC osc */
|
|
|
|
[1] = 20000000, /* 20 MHz on osc0 */
|
|
|
|
[2] = 12000000, /* 12 MHz on osc1 */
|
|
|
|
};
|
|
|
|
|
2009-12-03 21:58:20 +08:00
|
|
|
/*
|
|
|
|
* The ATNGW100 mkII is very similar to the ATNGW100. Both have the AT32AP7000
|
|
|
|
* chip on board; the difference is that the ATNGW100 mkII has 128 MB 32-bit
|
|
|
|
* SDRAM (the ATNGW100 has 32 MB 16-bit SDRAM) and 256 MB 16-bit NAND flash
|
|
|
|
* (the ATNGW100 has none.)
|
|
|
|
*
|
|
|
|
* The RAM difference is handled by the boot loader, so the only difference we
|
|
|
|
* end up handling here is the NAND flash, EBI pin reservation and if LCDC or
|
|
|
|
* MACB1 should be enabled.
|
|
|
|
*/
|
|
|
|
#ifdef CONFIG_BOARD_ATNGW100_MKII
|
|
|
|
#include <linux/mtd/partitions.h>
|
|
|
|
#include <mach/smc.h>
|
|
|
|
|
|
|
|
static struct smc_timing nand_timing __initdata = {
|
|
|
|
.ncs_read_setup = 0,
|
|
|
|
.nrd_setup = 10,
|
|
|
|
.ncs_write_setup = 0,
|
|
|
|
.nwe_setup = 10,
|
|
|
|
|
|
|
|
.ncs_read_pulse = 30,
|
|
|
|
.nrd_pulse = 15,
|
|
|
|
.ncs_write_pulse = 30,
|
|
|
|
.nwe_pulse = 15,
|
|
|
|
|
|
|
|
.read_cycle = 30,
|
|
|
|
.write_cycle = 30,
|
|
|
|
|
|
|
|
.ncs_read_recover = 0,
|
|
|
|
.nrd_recover = 15,
|
|
|
|
.ncs_write_recover = 0,
|
|
|
|
/* WE# high -> RE# low min 60 ns */
|
|
|
|
.nwe_recover = 50,
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct smc_config nand_config __initdata = {
|
|
|
|
.bus_width = 2,
|
|
|
|
.nrd_controlled = 1,
|
|
|
|
.nwe_controlled = 1,
|
|
|
|
.nwait_mode = 0,
|
|
|
|
.byte_write = 0,
|
|
|
|
.tdf_cycles = 2,
|
|
|
|
.tdf_mode = 0,
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct mtd_partition nand_partitions[] = {
|
|
|
|
{
|
|
|
|
.name = "main",
|
|
|
|
.offset = 0x00000000,
|
|
|
|
.size = MTDPART_SIZ_FULL,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static struct atmel_nand_data atngw100mkii_nand_data __initdata = {
|
|
|
|
.cle = 21,
|
|
|
|
.ale = 22,
|
|
|
|
.rdy_pin = GPIO_PIN_PB(28),
|
|
|
|
.enable_pin = GPIO_PIN_PE(23),
|
|
|
|
.bus_width_16 = true,
|
2011-12-29 14:43:24 +08:00
|
|
|
.ecc_mode = NAND_ECC_SOFT,
|
2011-05-29 21:49:22 +08:00
|
|
|
.parts = nand_partitions,
|
|
|
|
.num_parts = ARRAY_SIZE(nand_partitions),
|
2009-12-03 21:58:20 +08:00
|
|
|
};
|
|
|
|
#endif
|
|
|
|
|
2007-04-12 23:26:57 +08:00
|
|
|
/* Initialized by bootloader-specific startup code. */
|
|
|
|
struct tag *bootloader_tags __initdata;
|
|
|
|
|
|
|
|
struct eth_addr {
|
|
|
|
u8 addr[6];
|
|
|
|
};
|
|
|
|
static struct eth_addr __initdata hw_addr[2];
|
2011-03-09 04:17:06 +08:00
|
|
|
static struct macb_platform_data __initdata eth_data[2];
|
2007-04-12 23:26:57 +08:00
|
|
|
|
|
|
|
static struct spi_board_info spi0_board_info[] __initdata = {
|
|
|
|
{
|
|
|
|
.modalias = "mtd_dataflash",
|
2008-08-01 23:06:01 +08:00
|
|
|
.max_speed_hz = 8000000,
|
2007-04-12 23:26:57 +08:00
|
|
|
.chip_select = 0,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
atmel-mci: Driver for Atmel on-chip MMC controllers
This is a driver for the MMC controller on the AP7000 chips from
Atmel. It should in theory work on AT91 systems too with some
tweaking, but since the DMA interface is quite different, it's not
entirely clear if it's worth merging this with the at91_mci driver.
This driver has been around for a while in BSPs and kernel sources
provided by Atmel, but this particular version uses the generic DMA
Engine framework (with the slave extensions) instead of an
avr32-only DMA controller framework.
This driver can also use PIO transfers when no DMA channels are
available, and for transfers where using DMA may be difficult or
impractical for some reason (e.g. the DMA setup overhead is usually
not worth it for very short transfers, and badly aligned buffers or
lengths are difficult to handle.)
Currently, the driver only support PIO transfers. DMA support has been
split out to a separate patch to hopefully make it easier to review.
The driver has been tested using mmc-block and ext3fs on several SD,
SDHC and MMC+ cards. Reads and writes work fine, with read transfer
rates up to 3.5 MiB/s on fast cards with debugging disabled.
The driver has also been tested using the mmc_test module on the same
cards. All tests except 7, 9, 15 and 17 succeed. The first two are
unsupported by all the cards I have, so I don't know if the driver
handles this correctly. The last two fail because the hardware flags a
Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
with that.
Documentation for this controller can be found in many data sheets from
Atmel, including the AT32AP7000 data sheet which can be found here:
http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2008-07-01 00:35:03 +08:00
|
|
|
static struct mci_platform_data __initdata mci0_data = {
|
2008-08-07 20:08:49 +08:00
|
|
|
.slot[0] = {
|
|
|
|
.bus_width = 4,
|
2009-12-03 21:58:20 +08:00
|
|
|
#if defined(CONFIG_BOARD_ATNGW100_MKII)
|
|
|
|
.detect_pin = GPIO_PIN_PC(25),
|
|
|
|
.wp_pin = GPIO_PIN_PE(22),
|
|
|
|
#else
|
2008-08-07 20:08:49 +08:00
|
|
|
.detect_pin = GPIO_PIN_PC(25),
|
|
|
|
.wp_pin = GPIO_PIN_PE(0),
|
2009-12-03 21:58:20 +08:00
|
|
|
#endif
|
2008-08-07 20:08:49 +08:00
|
|
|
},
|
atmel-mci: Driver for Atmel on-chip MMC controllers
This is a driver for the MMC controller on the AP7000 chips from
Atmel. It should in theory work on AT91 systems too with some
tweaking, but since the DMA interface is quite different, it's not
entirely clear if it's worth merging this with the at91_mci driver.
This driver has been around for a while in BSPs and kernel sources
provided by Atmel, but this particular version uses the generic DMA
Engine framework (with the slave extensions) instead of an
avr32-only DMA controller framework.
This driver can also use PIO transfers when no DMA channels are
available, and for transfers where using DMA may be difficult or
impractical for some reason (e.g. the DMA setup overhead is usually
not worth it for very short transfers, and badly aligned buffers or
lengths are difficult to handle.)
Currently, the driver only support PIO transfers. DMA support has been
split out to a separate patch to hopefully make it easier to review.
The driver has been tested using mmc-block and ext3fs on several SD,
SDHC and MMC+ cards. Reads and writes work fine, with read transfer
rates up to 3.5 MiB/s on fast cards with debugging disabled.
The driver has also been tested using the mmc_test module on the same
cards. All tests except 7, 9, 15 and 17 succeed. The first two are
unsupported by all the cards I have, so I don't know if the driver
handles this correctly. The last two fail because the hardware flags a
Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
with that.
Documentation for this controller can be found in many data sheets from
Atmel, including the AT32AP7000 data sheet which can be found here:
http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2008-07-01 00:35:03 +08:00
|
|
|
};
|
|
|
|
|
2009-12-03 21:58:20 +08:00
|
|
|
static struct usba_platform_data atngw100_usba_data __initdata = {
|
|
|
|
#if defined(CONFIG_BOARD_ATNGW100_MKII)
|
|
|
|
.vbus_pin = GPIO_PIN_PE(26),
|
|
|
|
#else
|
|
|
|
.vbus_pin = -ENODEV,
|
|
|
|
#endif
|
|
|
|
};
|
|
|
|
|
2007-04-12 23:26:57 +08:00
|
|
|
/*
|
|
|
|
* The next two functions should go away as the boot loader is
|
|
|
|
* supposed to initialize the macb address registers with a valid
|
|
|
|
* ethernet address. But we need to keep it around for a while until
|
|
|
|
* we can be reasonably sure the boot loader does this.
|
|
|
|
*
|
|
|
|
* The phy_id is ignored as the driver will probe for it.
|
|
|
|
*/
|
|
|
|
static int __init parse_tag_ethernet(struct tag *tag)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
i = tag->u.ethernet.mac_index;
|
|
|
|
if (i < ARRAY_SIZE(hw_addr))
|
|
|
|
memcpy(hw_addr[i].addr, tag->u.ethernet.hw_address,
|
|
|
|
sizeof(hw_addr[i].addr));
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
__tagtable(ATAG_ETHERNET, parse_tag_ethernet);
|
|
|
|
|
|
|
|
static void __init set_hw_addr(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct resource *res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
|
|
|
|
const u8 *addr;
|
|
|
|
void __iomem *regs;
|
|
|
|
struct clk *pclk;
|
|
|
|
|
|
|
|
if (!res)
|
|
|
|
return;
|
|
|
|
if (pdev->id >= ARRAY_SIZE(hw_addr))
|
|
|
|
return;
|
|
|
|
|
|
|
|
addr = hw_addr[pdev->id].addr;
|
|
|
|
if (!is_valid_ether_addr(addr))
|
|
|
|
return;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Since this is board-specific code, we'll cheat and use the
|
|
|
|
* physical address directly as we happen to know that it's
|
|
|
|
* the same as the virtual address.
|
|
|
|
*/
|
|
|
|
regs = (void __iomem __force *)res->start;
|
|
|
|
pclk = clk_get(&pdev->dev, "pclk");
|
2010-11-27 01:06:12 +08:00
|
|
|
if (IS_ERR(pclk))
|
2007-04-12 23:26:57 +08:00
|
|
|
return;
|
|
|
|
|
|
|
|
clk_enable(pclk);
|
|
|
|
__raw_writel((addr[3] << 24) | (addr[2] << 16)
|
|
|
|
| (addr[1] << 8) | addr[0], regs + 0x98);
|
|
|
|
__raw_writel((addr[5] << 8) | addr[4], regs + 0x9c);
|
|
|
|
clk_disable(pclk);
|
|
|
|
clk_put(pclk);
|
|
|
|
}
|
|
|
|
|
|
|
|
void __init setup_board(void)
|
|
|
|
{
|
2009-04-01 01:31:02 +08:00
|
|
|
at32_map_usart(1, 0, 0); /* USART 1: /dev/ttyS0, DB9 */
|
2007-04-12 23:26:57 +08:00
|
|
|
at32_setup_serial_console(0);
|
|
|
|
}
|
|
|
|
|
2007-07-08 18:49:53 +08:00
|
|
|
static const struct gpio_led ngw_leds[] = {
|
|
|
|
{ .name = "sys", .gpio = GPIO_PIN_PA(16), .active_low = 1,
|
|
|
|
.default_trigger = "heartbeat",
|
|
|
|
},
|
|
|
|
{ .name = "a", .gpio = GPIO_PIN_PA(19), .active_low = 1, },
|
|
|
|
{ .name = "b", .gpio = GPIO_PIN_PE(19), .active_low = 1, },
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct gpio_led_platform_data ngw_led_data = {
|
|
|
|
.num_leds = ARRAY_SIZE(ngw_leds),
|
|
|
|
.leds = (void *) ngw_leds,
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct platform_device ngw_gpio_leds = {
|
|
|
|
.name = "leds-gpio",
|
|
|
|
.id = -1,
|
|
|
|
.dev = {
|
|
|
|
.platform_data = (void *) &ngw_led_data,
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2007-07-12 22:36:34 +08:00
|
|
|
static struct i2c_gpio_platform_data i2c_gpio_data = {
|
2007-09-25 22:17:48 +08:00
|
|
|
.sda_pin = GPIO_PIN_PA(6),
|
|
|
|
.scl_pin = GPIO_PIN_PA(7),
|
|
|
|
.sda_is_open_drain = 1,
|
|
|
|
.scl_is_open_drain = 1,
|
|
|
|
.udelay = 2, /* close to 100 kHz */
|
2007-07-12 22:36:34 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
static struct platform_device i2c_gpio_device = {
|
|
|
|
.name = "i2c-gpio",
|
|
|
|
.id = 0,
|
|
|
|
.dev = {
|
|
|
|
.platform_data = &i2c_gpio_data,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
2008-06-13 03:18:05 +08:00
|
|
|
static struct i2c_board_info __initdata i2c_info[] = {
|
|
|
|
/* NOTE: original ATtiny24 firmware is at address 0x0b */
|
|
|
|
};
|
|
|
|
|
2007-04-12 23:26:57 +08:00
|
|
|
static int __init atngw100_init(void)
|
|
|
|
{
|
2007-07-08 18:49:53 +08:00
|
|
|
unsigned i;
|
|
|
|
|
2007-04-12 23:26:57 +08:00
|
|
|
/*
|
2009-12-03 21:58:20 +08:00
|
|
|
* ATNGW100 mkII uses 32-bit SDRAM interface. Reserve the
|
|
|
|
* SDRAM-specific pins so that nobody messes with them.
|
2007-04-12 23:26:57 +08:00
|
|
|
*/
|
2009-12-03 21:58:20 +08:00
|
|
|
#ifdef CONFIG_BOARD_ATNGW100_MKII
|
|
|
|
at32_reserve_pin(GPIO_PIOE_BASE, ATMEL_EBI_PE_DATA_ALL);
|
|
|
|
|
|
|
|
smc_set_timing(&nand_config, &nand_timing);
|
|
|
|
smc_set_configuration(3, &nand_config);
|
|
|
|
at32_add_device_nand(0, &atngw100mkii_nand_data);
|
|
|
|
#endif
|
2007-04-12 23:26:57 +08:00
|
|
|
|
|
|
|
at32_add_device_usart(0);
|
|
|
|
|
|
|
|
set_hw_addr(at32_add_device_eth(0, ð_data[0]));
|
2009-12-03 21:58:20 +08:00
|
|
|
#ifndef CONFIG_BOARD_ATNGW100_MKII_LCD
|
2007-04-12 23:26:57 +08:00
|
|
|
set_hw_addr(at32_add_device_eth(1, ð_data[1]));
|
2009-12-03 21:58:20 +08:00
|
|
|
#endif
|
2007-04-12 23:26:57 +08:00
|
|
|
|
|
|
|
at32_add_device_spi(0, spi0_board_info, ARRAY_SIZE(spi0_board_info));
|
atmel-mci: Driver for Atmel on-chip MMC controllers
This is a driver for the MMC controller on the AP7000 chips from
Atmel. It should in theory work on AT91 systems too with some
tweaking, but since the DMA interface is quite different, it's not
entirely clear if it's worth merging this with the at91_mci driver.
This driver has been around for a while in BSPs and kernel sources
provided by Atmel, but this particular version uses the generic DMA
Engine framework (with the slave extensions) instead of an
avr32-only DMA controller framework.
This driver can also use PIO transfers when no DMA channels are
available, and for transfers where using DMA may be difficult or
impractical for some reason (e.g. the DMA setup overhead is usually
not worth it for very short transfers, and badly aligned buffers or
lengths are difficult to handle.)
Currently, the driver only support PIO transfers. DMA support has been
split out to a separate patch to hopefully make it easier to review.
The driver has been tested using mmc-block and ext3fs on several SD,
SDHC and MMC+ cards. Reads and writes work fine, with read transfer
rates up to 3.5 MiB/s on fast cards with debugging disabled.
The driver has also been tested using the mmc_test module on the same
cards. All tests except 7, 9, 15 and 17 succeed. The first two are
unsupported by all the cards I have, so I don't know if the driver
handles this correctly. The last two fail because the hardware flags a
Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
with that.
Documentation for this controller can be found in many data sheets from
Atmel, including the AT32AP7000 data sheet which can be found here:
http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2008-07-01 00:35:03 +08:00
|
|
|
at32_add_device_mci(0, &mci0_data);
|
2009-12-03 21:58:20 +08:00
|
|
|
at32_add_device_usba(0, &atngw100_usba_data);
|
2007-04-12 23:26:57 +08:00
|
|
|
|
2007-07-08 18:49:53 +08:00
|
|
|
for (i = 0; i < ARRAY_SIZE(ngw_leds); i++) {
|
|
|
|
at32_select_gpio(ngw_leds[i].gpio,
|
|
|
|
AT32_GPIOF_OUTPUT | AT32_GPIOF_HIGH);
|
|
|
|
}
|
|
|
|
platform_device_register(&ngw_gpio_leds);
|
|
|
|
|
2008-06-13 03:18:05 +08:00
|
|
|
/* all these i2c/smbus pins should have external pullups for
|
|
|
|
* open-drain sharing among all I2C devices. SDA and SCL do;
|
2009-12-03 21:58:20 +08:00
|
|
|
* PB28/EXTINT3 (ATNGW100) and PE21 (ATNGW100 mkII) doesn't; it should
|
|
|
|
* be SMBALERT# (for PMBus), but it's not available off-board.
|
2008-06-13 03:18:05 +08:00
|
|
|
*/
|
2009-12-03 21:58:20 +08:00
|
|
|
#ifdef CONFIG_BOARD_ATNGW100_MKII
|
|
|
|
at32_select_periph(GPIO_PIOE_BASE, 1 << 21, 0, AT32_GPIOF_PULLUP);
|
|
|
|
#else
|
2008-09-24 16:30:47 +08:00
|
|
|
at32_select_periph(GPIO_PIOB_BASE, 1 << 28, 0, AT32_GPIOF_PULLUP);
|
2009-12-03 21:58:20 +08:00
|
|
|
#endif
|
2007-09-25 22:17:48 +08:00
|
|
|
at32_select_gpio(i2c_gpio_data.sda_pin,
|
|
|
|
AT32_GPIOF_MULTIDRV | AT32_GPIOF_OUTPUT | AT32_GPIOF_HIGH);
|
|
|
|
at32_select_gpio(i2c_gpio_data.scl_pin,
|
|
|
|
AT32_GPIOF_MULTIDRV | AT32_GPIOF_OUTPUT | AT32_GPIOF_HIGH);
|
2007-07-12 22:36:34 +08:00
|
|
|
platform_device_register(&i2c_gpio_device);
|
2008-06-13 03:18:05 +08:00
|
|
|
i2c_register_board_info(0, i2c_info, ARRAY_SIZE(i2c_info));
|
2007-07-12 22:36:34 +08:00
|
|
|
|
2007-04-12 23:26:57 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
postcore_initcall(atngw100_init);
|
2008-06-13 03:18:05 +08:00
|
|
|
|
|
|
|
static int __init atngw100_arch_init(void)
|
|
|
|
{
|
2009-12-03 21:58:20 +08:00
|
|
|
/* PB30 (ATNGW100) and PE30 (ATNGW100 mkII) is the otherwise unused
|
|
|
|
* jumper on the mainboard, with an external pullup; the jumper grounds
|
|
|
|
* it. Use it however you like, including letting U-Boot or Linux tweak
|
|
|
|
* boot sequences.
|
2008-09-07 11:19:02 +08:00
|
|
|
*/
|
2009-12-03 21:58:20 +08:00
|
|
|
#ifdef CONFIG_BOARD_ATNGW100_MKII
|
|
|
|
at32_select_gpio(GPIO_PIN_PE(30), 0);
|
|
|
|
gpio_request(GPIO_PIN_PE(30), "j15");
|
|
|
|
gpio_direction_input(GPIO_PIN_PE(30));
|
|
|
|
gpio_export(GPIO_PIN_PE(30), false);
|
|
|
|
#else
|
2008-09-07 11:19:02 +08:00
|
|
|
at32_select_gpio(GPIO_PIN_PB(30), 0);
|
|
|
|
gpio_request(GPIO_PIN_PB(30), "j15");
|
|
|
|
gpio_direction_input(GPIO_PIN_PB(30));
|
|
|
|
gpio_export(GPIO_PIN_PB(30), false);
|
2009-12-03 21:58:20 +08:00
|
|
|
#endif
|
2008-09-07 11:19:02 +08:00
|
|
|
|
2008-06-13 03:18:05 +08:00
|
|
|
/* set_irq_type() after the arch_initcall for EIC has run, and
|
|
|
|
* before the I2C subsystem could try using this IRQ.
|
|
|
|
*/
|
2011-03-24 23:39:32 +08:00
|
|
|
return irq_set_irq_type(AT32_EXTINT(3), IRQ_TYPE_EDGE_FALLING);
|
2008-06-13 03:18:05 +08:00
|
|
|
}
|
|
|
|
arch_initcall(atngw100_arch_init);
|