All of lore.kernel.org
 help / color / mirror / Atom feed
From: scott.branden@broadcom.com (Scott Branden)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT
Date: Tue, 28 Jun 2016 15:13:59 -0700	[thread overview]
Message-ID: <5772F6A7.9080304@broadcom.com> (raw)
In-Reply-To: <1467151833-20767-2-git-send-email-jon.mason@broadcom.com>



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 at 1800c184 {
> +		compatible = "brcm,bcm53010-cru", "syscon";
> +		reg = <0x1800c184 0x4>;
> +	};
> +
> +	reboot at 1800c184 {
> +		compatible ="syscon-reboot";
> +		regmap = <&cru>;
> +		offset = <0>;
> +		mask = <0x39>;
> +	};
> +
>   	nand: nand at 18028000 {
>   		compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1", "brcm,brcmnand";
>   		reg = <0x18028000 0x600>, <0x1811a408 0x600>, <0x18028f00 0x20>;
>

WARNING: multiple messages have this Message-ID (diff)
From: Scott Branden <scott.branden@broadcom.com>
To: Jon Mason <jon.mason@broadcom.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Jon Mason <jonmason@broadcom.com>
Subject: Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT
Date: Tue, 28 Jun 2016 15:13:59 -0700	[thread overview]
Message-ID: <5772F6A7.9080304@broadcom.com> (raw)
In-Reply-To: <1467151833-20767-2-git-send-email-jon.mason@broadcom.com>



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>;
>

  reply	other threads:[~2016-06-28 22:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 22:10 [PATCH 0/2] arm: dts: syscon based reboot in DT Jon Mason
2016-06-28 22:10 ` Jon Mason
2016-06-28 22:10 ` [PATCH 1/2] arm: dts: bcm5301x: Add " Jon Mason
2016-06-28 22:10   ` Jon Mason
2016-06-28 22:13   ` Scott Branden [this message]
2016-06-28 22:13     ` Scott Branden
2016-06-28 22:28     ` Jon Mason
2016-06-28 22:28       ` Jon Mason
2016-06-28 22:10 ` [PATCH 2/2] arm: dts: nsp: " Jon Mason
2016-06-28 22:10   ` Jon Mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5772F6A7.9080304@broadcom.com \
    --to=scott.branden@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.