From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/9] mpc85xx: watchdog initialisation added
Date: Wed, 13 Aug 2014 18:49:50 -0500 [thread overview]
Message-ID: <1407973790.7427.205.camel@snotra.buserror.net> (raw)
In-Reply-To: <1401779120-20306-4-git-send-email-rainer.boschung@keymile.com>
On Tue, 2014-06-03 at 09:05 +0200, Rainer Boschung wrote:
> Function to inititialize the cpu watchdog added.
>
> Signed-off-by: Rainer Boschung <rainer.boschung@keymile.com>
> ---
> arch/powerpc/cpu/mpc85xx/cpu.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/powerpc/cpu/mpc85xx/cpu.c b/arch/powerpc/cpu/mpc85xx/cpu.c
> index 684d400..6274f92 100644
> --- a/arch/powerpc/cpu/mpc85xx/cpu.c
> +++ b/arch/powerpc/cpu/mpc85xx/cpu.c
> @@ -310,6 +310,14 @@ __weak unsigned long get_tbclk (void)
>
>
> #if defined(CONFIG_WATCHDOG)
> +#define WATCHDOG_MASK (TCR_WP(63) | TCR_WRC(3) | TCR_WIE)
> +void
> +init_85xx_watchdog(void)
> +{
> + mtspr(SPRN_TCR, (mfspr(SPRN_TCR) & ~WATCHDOG_MASK) |
> + TCR_WP(CONFIG_WATCHDOG_PRESC) | TCR_WRC(CONFIG_WATCHDOG_RC));
> +}
These config symbols require documentation, and defaults to avoid
breaking the build of existing mpc85xx boards that enable
CONFIG_WATCHDOG (even if you add this later in the patchset, you're
breaking bisectability).
-Scott
next prev parent reply other threads:[~2014-08-13 23:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 7:05 [U-Boot] CPU Wachtog for P2041 Rainer Boschung
2014-06-03 7:05 ` [U-Boot] [PATCH 1/9] mpc85xx: fix interrupt init to not affect watchdog Rainer Boschung
2014-08-13 23:45 ` Scott Wood
2014-06-03 7:05 ` [U-Boot] [PATCH 2/9] powerpc: macros for e500mc timer regs added Rainer Boschung
2014-08-13 23:47 ` Scott Wood
2014-06-03 7:05 ` [U-Boot] [PATCH 3/9] mpc85xx: watchdog initialisation added Rainer Boschung
2014-08-13 23:49 ` Scott Wood [this message]
2014-08-13 23:51 ` Scott Wood
2014-06-03 7:05 ` [U-Boot] [PATCH 4/9] powerpc: mpc85xx watchdog init added to init_func Rainer Boschung
2014-08-13 23:52 ` Scott Wood
2014-06-03 7:05 ` [U-Boot] [PATCH 5/9] kmp204x: CPU watchdog enabled Rainer Boschung
2014-07-18 22:21 ` York Sun
2014-07-23 21:34 ` York Sun
2014-07-28 19:29 ` York Sun
2014-06-03 7:05 ` [U-Boot] [PATCH 6/9] kmp204x/qrio: prepare support for the CPU watchdog reset reason Rainer Boschung
2014-06-03 7:05 ` [U-Boot] [PATCH 7/9] kmp204x: set CPU watchdog reset reason flag Rainer Boschung
2014-06-03 7:05 ` [U-Boot] [PATCH 8/9] kmp204x/qrio: support for setting the CPU reset request mode Rainer Boschung
2014-06-03 7:05 ` [U-Boot] [PATCH 9/9] kmp204x: prepare to use CPU watchdog Rainer Boschung
2014-07-16 11:20 ` [U-Boot] CPU Wachtog for P2041 Boschung, Rainer
2014-07-16 15:29 ` York Sun
2014-07-18 21:45 ` York Sun
2014-08-12 9:19 ` Valentin Longchamp
2014-08-04 18:25 ` York Sun
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=1407973790.7427.205.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox