2012-04-17 14:26:31 +08:00
|
|
|
/*
|
|
|
|
* SoC specific setup code for the AT91SAM9N12
|
|
|
|
*
|
|
|
|
* Copyright (C) 2012 Atmel Corporation.
|
|
|
|
*
|
|
|
|
* Licensed under GPLv2 or later.
|
|
|
|
*/
|
|
|
|
|
2014-11-27 00:25:24 +08:00
|
|
|
#include <asm/system_misc.h>
|
|
|
|
#include <mach/hardware.h>
|
2012-04-17 14:26:31 +08:00
|
|
|
|
|
|
|
#include "soc.h"
|
|
|
|
#include "generic.h"
|
|
|
|
|
|
|
|
/* --------------------------------------------------------------------
|
|
|
|
* AT91SAM9N12 processor initialization
|
|
|
|
* -------------------------------------------------------------------- */
|
|
|
|
|
|
|
|
static void __init at91sam9n12_map_io(void)
|
|
|
|
{
|
|
|
|
at91_init_sram(0, AT91SAM9N12_SRAM_BASE, AT91SAM9N12_SRAM_SIZE);
|
|
|
|
}
|
|
|
|
|
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
|
|
|
static void __init at91sam9n12_initialize(void)
|
|
|
|
{
|
|
|
|
at91_sysirq_mask_rtc(AT91SAM9N12_BASE_RTC);
|
|
|
|
}
|
|
|
|
|
2013-03-22 21:24:09 +08:00
|
|
|
AT91_SOC_START(at91sam9n12)
|
2012-04-17 14:26:31 +08:00
|
|
|
.map_io = at91sam9n12_map_io,
|
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
|
|
|
.init = at91sam9n12_initialize,
|
2012-08-16 17:36:55 +08:00
|
|
|
AT91_SOC_END
|