2007-05-12 03:49:56 +08:00
|
|
|
/*
|
|
|
|
|
* arch/arm/mach-at91/at91sam9rl.c
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2005 SAN People
|
|
|
|
|
* Copyright (C) 2007 Atmel Corporation
|
|
|
|
|
*
|
|
|
|
|
* This file is subject to the terms and conditions of the GNU General Public
|
|
|
|
|
* License. See the file COPYING in the main directory of this archive for
|
|
|
|
|
* more details.
|
|
|
|
|
*/
|
|
|
|
|
|
2012-03-29 01:30:01 +08:00
|
|
|
#include <asm/system_misc.h>
|
2014-11-09 14:39:51 +08:00
|
|
|
#include <asm/irq.h>
|
2008-08-05 23:14:15 +08:00
|
|
|
#include <mach/cpu.h>
|
2011-04-23 22:12:57 +08:00
|
|
|
#include <mach/at91_dbgu.h>
|
2013-11-14 17:49:19 +08:00
|
|
|
#include <mach/hardware.h>
|
2007-05-12 03:49:56 +08:00
|
|
|
|
2011-04-23 15:28:34 +08:00
|
|
|
#include "soc.h"
|
2007-05-12 03:49:56 +08:00
|
|
|
#include "generic.h"
|
|
|
|
|
|
|
|
|
|
/* --------------------------------------------------------------------
|
|
|
|
|
* AT91SAM9RL processor initialization
|
|
|
|
|
* -------------------------------------------------------------------- */
|
|
|
|
|
|
2011-04-23 15:28:34 +08:00
|
|
|
static void __init at91sam9rl_map_io(void)
|
2007-05-12 03:49:56 +08:00
|
|
|
{
|
2011-04-23 22:12:57 +08:00
|
|
|
unsigned long sram_size;
|
2007-05-12 03:49:56 +08:00
|
|
|
|
2011-04-23 22:12:57 +08:00
|
|
|
switch (at91_soc_initdata.cidr & AT91_CIDR_SRAMSIZ) {
|
2007-05-12 03:49:56 +08:00
|
|
|
case AT91_CIDR_SRAMSIZ_32K:
|
|
|
|
|
sram_size = 2 * SZ_16K;
|
|
|
|
|
break;
|
|
|
|
|
case AT91_CIDR_SRAMSIZ_16K:
|
|
|
|
|
default:
|
|
|
|
|
sram_size = SZ_16K;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Map SRAM */
|
2011-05-10 03:20:09 +08:00
|
|
|
at91_init_sram(0, AT91SAM9RL_SRAM_BASE, sram_size);
|
2011-04-28 20:19:32 +08:00
|
|
|
}
|
2007-05-12 03:49:56 +08:00
|
|
|
|
2011-04-24 18:20:28 +08:00
|
|
|
static void __init at91sam9rl_initialize(void)
|
2011-04-28 20:19:32 +08:00
|
|
|
{
|
2012-02-05 20:25:32 +08:00
|
|
|
arm_pm_idle = at91sam9_idle;
|
2007-05-12 03:49:56 +08:00
|
|
|
|
ARM: at91: fix hanged boot due to early rtc-interrupt
Make sure the RTC-interrupts are masked at boot by adding a new helper
function to be used at SOC-init.
This fixes hanged boot on all AT91 SOCs with an RTC (but RM9200), for
example, after a reset during an RTC-update or if an RTC-alarm goes off
after shutdown (e.g. when using RTC wakeup).
The RTC and RTT-peripherals are powered by backup power (VDDBU) (on all
AT91 SOCs but RM9200) and are not reset on wake-up, user, watchdog or
software reset. This means that their interrupts may be enabled during
early boot if, for example, they where not disabled during a previous
shutdown (e.g. due to a buggy driver or a non-clean shutdown such as a
user reset). Furthermore, an RTC or RTT-alarm may also be active.
The RTC and RTT-interrupts use the shared system-interrupt line, which
is also used by the PIT, and if an interrupt occurs before a handler
(e.g. RTC-driver) has been installed this leads to the system interrupt
being disabled and prevents the system from booting.
Note that when boot hangs due to an early RTC or RTT-interrupt, the only
way to get the system to start again is to remove the backup power (e.g.
battery) or to disable the interrupt manually from the bootloader. In
particular, a user reset is not sufficient.
Signed-off-by: Johan Hovold <jhovold@gmail.com>
Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: stable@vger.kernel.org # 3.11.x
2013-10-16 17:56:14 +08:00
|
|
|
at91_sysirq_mask_rtc(AT91SAM9RL_BASE_RTC);
|
ARM: at91: fix hanged boot due to early rtt-interrupt
Make sure the RTT-interrupts are masked at boot by adding a new helper
function to be used at SOC-init.
This fixes hanged boot on all AT91 SOCs with an RTT, for example, if an
RTT-alarm goes off after a non-clean shutdown (e.g. when using RTC
wakeup).
The RTC and RTT-peripherals are powered by backup power (VDDBU) (on all
AT91 SOCs but RM9200) and are not reset on wake-up, user, watchdog or
software reset. This means that their interrupts may be enabled during
early boot if, for example, they where not disabled during a previous
shutdown (e.g. due to a buggy driver or a non-clean shutdown such as a
user reset). Furthermore, an RTC or RTT-alarm may also be active.
The RTC and RTT-interrupts use the shared system-interrupt line, which
is also used by the PIT, and if an interrupt occurs before a handler
(e.g. RTC-driver) has been installed this leads to the system interrupt
being disabled and prevents the system from booting.
Note that when boot hangs due to an early RTC or RTT-interrupt, the only
way to get the system to start again is to remove the backup power (e.g.
battery) or to disable the interrupt manually from the bootloader. In
particular, a user reset is not sufficient.
Signed-off-by: Johan Hovold <jhovold@gmail.com>
Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: stable@vger.kernel.org # 3.11.x
2013-10-16 17:56:15 +08:00
|
|
|
at91_sysirq_mask_rtt(AT91SAM9RL_BASE_RTT);
|
2014-07-03 17:10:10 +08:00
|
|
|
}
|
|
|
|
|
|
2013-03-22 21:24:09 +08:00
|
|
|
AT91_SOC_START(at91sam9rl)
|
2011-04-23 15:28:34 +08:00
|
|
|
.map_io = at91sam9rl_map_io,
|
|
|
|
|
.init = at91sam9rl_initialize,
|
2012-08-16 17:36:55 +08:00
|
|
|
AT91_SOC_END
|