Hi Geert,
On Monday, February 13, 2017, Geert Uytterhoeven wrote:
> On Fri, Feb 10, 2017 at 8:46 PM, Chris Brandt
> wrote:
> > On Friday, February 10, 2017, Geert Uytterhoeven wrote:
> >> Alternatively, you can write a restart driver (cfr.
> >>
Hi Chris,
On Fri, Feb 10, 2017 at 8:46 PM, Chris Brandt wrote:
> On Friday, February 10, 2017, Geert Uytterhoeven wrote:
>> Alternatively, you can write a restart driver (cfr.
>> drivers/power/reset/rmobile-reset.c) that binds against a
>> "renesas,r7s72100-wdt" device
Hi Chris,
On Fri, Feb 10, 2017 at 3:59 PM, Chris Brandt wrote:
> On Friday, February 10, 2017, Geert Uytterhoeven wrote:
>> > static const char *const r7s72100_boards_compat_dt[] __initconst = {
>> > "renesas,r7s72100",
>> > NULL,
>> > @@ -29,4 +58,5 @@
> > #1 and #3 look like they are the same thing (except #3 is enabled on power
> > on reset). The renesas_wdt.c uses the register names from #1.
> > Is the idea that you only use #3 to make sure your systems boots and get
> > into
> > Linux, then from there you use #1 and stop #3 (hence no
Hi Geert,
On Friday, February 10, 2017, Geert Uytterhoeven wrote:
> > static const char *const r7s72100_boards_compat_dt[] __initconst = {
> > "renesas,r7s72100",
> > NULL,
> > @@ -29,4 +58,5 @@ DT_MACHINE_START(R7S72100_DT, "Generic R7S72100
> (Flattened Device Tree)")
> >
Add a simple restart handler which enables the watchdog timer with the
device reset option enabled. This is the only way SW can cause a reset on
this SoC.
If someone has a board that needs more specific operations to be done
first, they can override this function in another file.
Signed-off-by: