public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/9] kmp204x: CPU watchdog enabled
Date: Wed, 23 Jul 2014 14:34:33 -0700	[thread overview]
Message-ID: <53D02A69.4060102@freescale.com> (raw)
In-Reply-To: <53C99E04.2050907@freescale.com>

Rainer,

Did you get a chance to fix your patch?

York


On 07/18/2014 03:21 PM, York Sun wrote:
> Rainer,
> 
> Once this patch is enabled, we have
> 
> warning: implicit declaration of function 'init_85xx_watchdog'
> [-Wimplicit-function-declaration]
> 
> Please fix.
> 
> York
> 
> 
> On 06/03/2014 12:05 AM, Rainer Boschung wrote:
>> The booting of the board is now protected by the CPU watchdog.
>> A failure during the boot phase will end up in board reset.
>>
>> Signed-off-by: Rainer Boschung <rainer.boschung@keymile.com>
>> ---
>>  include/configs/km/kmp204x-common.h | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/include/configs/km/kmp204x-common.h b/include/configs/km/kmp204x-common.h
>> index efd9635..a0f9d29 100644
>> --- a/include/configs/km/kmp204x-common.h
>> +++ b/include/configs/km/kmp204x-common.h
>> @@ -377,6 +377,14 @@ int get_scl(void);
>>  #define CONFIG_SYS_LOADS_BAUD_CHANGE	/* allow baudrate change */
>>  
>>  /*
>> + * Hardware Watchdog
>> + */
>> +#define CONFIG_WATCHDOG			/* enable CPU watchdog */
>> +#define CONFIG_WATCHDOG_PRESC 34	/* wdog prescaler 2^(64-34) (~10min) */
>> +#define CONFIG_WATCHDOG_RC WRC_CHIP	/* reset chip on watchdog event */
>> +
>> +
>> +/*
>>   * additionnal command line configuration.
>>   */
>>  #define CONFIG_CMD_PCI
>>
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 

  reply	other threads:[~2014-07-23 21:34 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
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 [this message]
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=53D02A69.4060102@freescale.com \
    --to=yorksun@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