linux-kernel - Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5772F6A7.9080304@broadcom.com>
Date:	Tue, 28 Jun 2016 15:13:59 -0700
From:	Scott Branden <scott.branden@...adcom.com>
To:	Jon Mason <jon.mason@...adcom.com>, Arnd Bergmann <arnd@...db.de>
Cc:	Florian Fainelli <f.fainelli@...il.com>,
	bcm-kernel-feedback-list@...adcom.com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Jon Mason <jonmason@...adcom.com>
Subject: Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT



On 16-06-28 03:10 PM, Jon Mason wrote:
> From: Jon Mason <jonmason@...adcom.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@...adcom.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@...0c184 {
> +		compatible = "brcm,bcm53010-cru", "syscon";
> +		reg = <0x1800c184 0x4>;
> +	};
> +
> +	reboot@...0c184 {
> +		compatible ="syscon-reboot";
> +		regmap = <&cru>;
> +		offset = <0>;
> +		mask = <0x39>;
> +	};
> +
>   	nand: nand@...28000 {
>   		compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1", "brcm,brcmnand";
>   		reg = <0x18028000 0x600>, <0x1811a408 0x600>, <0x18028f00 0x20>;
>