diff options
author | Fabrizio Castro <fabrizio.castro@bp.renesas.com> | 2018-02-28 20:40:22 +0300 |
---|---|---|
committer | Simon Horman <horms+renesas@verge.net.au> | 2018-03-13 22:52:19 +0300 |
commit | 58adf1ba0d227754d9bc763c667f10efe0053ce5 (patch) | |
tree | 2d0aacba5b68bbd309ec45fa34754d7448141b5c /Documentation/pcmcia | |
parent | 60fc75bdf5b1b8ed3e0a372b7b35f27726ff542b (diff) | |
download | linux-58adf1ba0d227754d9bc763c667f10efe0053ce5.tar.xz |
ARM: shmobile: Add watchdog support
On R-Car Gen2 and RZ/G1 platforms, we use the SBAR registers to make non
boot CPUs run a routine designed to bring up SMP and deal with hot plug.
The value contained in the SBAR registers is not initialized by a WDT
triggered reset, which means that after a WDT triggered reset we jump
to the SMP bring up routine, preventing the system from executing the
bootrom code.
The purpose of this patch is to jump to the bootrom code in case of a
WDT triggered reset, and keep the SMP functionality untouched.
In order to tell if the code had been called due to the WDT overflowing
we are testing WOVF from register RWTCSRA.
The new function shmobile_boot_vector_gen2 isn't replacing
shmobile_boot_vector for backward compatibility reasons. The kernel
will install the best option (either shmobile_boot_vector or
shmobile_boot_vector_gen2) to ICRAM1 after parsing the device tree,
according to the amount of memory available.
Since shmobile_boot_vector has become bigger, "reg" property of nodes
compatible with "renesas,smp-sram" now need to be set to a value
greater or equal to "<0 0x60>".
Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Signed-off-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
[simon: dropped #ifdef from common.h]
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'Documentation/pcmcia')
0 files changed, 0 insertions, 0 deletions