diff -r 4816d766a08a -r f345bda72bc4 Symbian3/PDK/Source/GUID-423537D5-2C8A-5C26-8D7B-60446E95F681.dita --- a/Symbian3/PDK/Source/GUID-423537D5-2C8A-5C26-8D7B-60446E95F681.dita Tue Mar 30 11:42:04 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-423537D5-2C8A-5C26-8D7B-60446E95F681.dita Tue Mar 30 11:56:28 2010 +0100 @@ -10,10 +10,11 @@ Interrupt -Layer InitialisationThis topic describes how to implement the Asic::Init1() and Asic::Init3() functions +Layer InitialisationThis topic describes how to implement the Asic::Init1() and Asic::Init3() functions to initialise interrupts. -
In first phase initialisation

During first phase -initialisation of start-up, the kernel calls the ASSP's implementation of Asic::Init1(). +

In first phase +initialisation

During first phase initialisation of start-up, the +kernel calls the ASSP's implementation of Asic::Init1(). For the template reference board, where the ASSP is split into a common, ASSP layer and a device-specific (variant) layer, interrupt handling is initialised in the ASSP layer, specifically in TemplateAssp::Init1(), @@ -60,8 +61,9 @@

  • Bind any ISRs that handle chained or pseudo interrupts

    • -
    In third phase initialisation

    During third phase -initialisation of start-up, the kernel calls the ASSP's implementation of Asic::Init3().

    Note +

    In third phase +initialisation

    During third phase initialisation of start-up, the +kernel calls the ASSP's implementation of Asic::Init3().

    Note that interrupts are enabled during third phase initialisation.

    Within your implementation of Init3(), if you need to, call Interrupt::Enable() on any of the interrupt sources that are bound to a chained or pseudo ISR dispatcher.