| Message ID | 1467151833-20767-2-git-send-email-jon.mason@broadcom.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 16-06-28 03:10 PM, Jon Mason wrote: > From: Jon Mason <jonmason@broadcom.com> > > Add the ability to reboot via a reset of the processor. This is > achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, > this only resets the core and not the other IP blocks. So if possible, > other methods should be used on the individual boards. Is it possible to force a watchdog reset instead for reboot? > > Signed-off-by: Jon Mason <jonmason@broadcom.com> > --- > arch/arm/boot/dts/bcm5301x.dtsi | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/arch/arm/boot/dts/bcm5301x.dtsi b/arch/arm/boot/dts/bcm5301x.dtsi > index 7d4d29b..f878d0d 100644 > --- a/arch/arm/boot/dts/bcm5301x.dtsi > +++ b/arch/arm/boot/dts/bcm5301x.dtsi > @@ -260,6 +260,18 @@ > "sata2"; > }; > > + cru: system-controller@1800c184 { > + compatible = "brcm,bcm53010-cru", "syscon"; > + reg = <0x1800c184 0x4>; > + }; > + > + reboot@1800c184 { > + compatible ="syscon-reboot"; > + regmap = <&cru>; > + offset = <0>; > + mask = <0x39>; > + }; > + > nand: nand@18028000 { > compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1", "brcm,brcmnand"; > reg = <0x18028000 0x600>, <0x1811a408 0x600>, <0x18028f00 0x20>; >
On Tue, Jun 28, 2016 at 6:13 PM, Scott Branden <scott.branden@broadcom.com> wrote: > > > On 16-06-28 03:10 PM, Jon Mason wrote: >> >> From: Jon Mason <jonmason@broadcom.com> >> >> Add the ability to reboot via a reset of the processor. This is >> achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, >> this only resets the core and not the other IP blocks. So if possible, >> other methods should be used on the individual boards. > > Is it possible to force a watchdog reset instead for reboot? There is a "Power Watchdog" in both NS and NSP (and possibly others). This isn't a working driver to test, but it might be possible to use that to reset the system if the syscon and a unique NS/NSP reset driver are not acceptable solutions. >> >> Signed-off-by: Jon Mason <jonmason@broadcom.com> >> --- >> arch/arm/boot/dts/bcm5301x.dtsi | 12 ++++++++++++ >> 1 file changed, 12 insertions(+) >> >> diff --git a/arch/arm/boot/dts/bcm5301x.dtsi >> b/arch/arm/boot/dts/bcm5301x.dtsi >> index 7d4d29b..f878d0d 100644 >> --- a/arch/arm/boot/dts/bcm5301x.dtsi >> +++ b/arch/arm/boot/dts/bcm5301x.dtsi >> @@ -260,6 +260,18 @@ >> "sata2"; >> }; >> >> + cru: system-controller@1800c184 { >> + compatible = "brcm,bcm53010-cru", "syscon"; >> + reg = <0x1800c184 0x4>; >> + }; >> + >> + reboot@1800c184 { >> + compatible ="syscon-reboot"; >> + regmap = <&cru>; >> + offset = <0>; >> + mask = <0x39>; >> + }; >> + >> nand: nand@18028000 { >> compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1", >> "brcm,brcmnand"; >> reg = <0x18028000 0x600>, <0x1811a408 0x600>, <0x18028f00 >> 0x20>; >> >
diff --git a/arch/arm/boot/dts/bcm5301x.dtsi b/arch/arm/boot/dts/bcm5301x.dtsi index 7d4d29b..f878d0d 100644 --- a/arch/arm/boot/dts/bcm5301x.dtsi +++ b/arch/arm/boot/dts/bcm5301x.dtsi @@ -260,6 +260,18 @@ "sata2"; }; + cru: system-controller@1800c184 { + compatible = "brcm,bcm53010-cru", "syscon"; + reg = <0x1800c184 0x4>; + }; + + reboot@1800c184 { + compatible ="syscon-reboot"; + regmap = <&cru>; + offset = <0>; + mask = <0x39>; + }; + nand: nand@18028000 { compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1", "brcm,brcmnand"; reg = <0x18028000 0x600>, <0x1811a408 0x600>, <0x18028f00 0x20>;