From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CPU Wachtog for P2041
Date: Wed, 16 Jul 2014 08:29:36 -0700 [thread overview]
Message-ID: <53C69A60.40503@freescale.com> (raw)
In-Reply-To: <B7AC17D946CFB9489B0C4EEDFEE0C8EC1028986C14@SRVDEHAN1MX1.keymile.net>
They came in after the merging window was closed. They will be reviewed and
considered for next release.
York
On 07/16/2014 04:20 AM, Boschung, Rainer wrote:
> Hi,
>
> obviously my patches concerning the CPU Watchdog for the kmp204x have not been added to the latest u-boot release.
>
> Could you please review my patches and add them for the next release of u-boot.
> Thanks you.
>
> Best regards
>
> Rainer Boschung
> KEYMILE AG
>
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de [mailto:u-boot-
>> bounces at lists.denx.de] On Behalf Of Rainer Boschung
>> Sent: Tuesday, June 3, 2014 9:05 AM
>> To: u-boot at lists.denx.de
>> Subject: [U-Boot] CPU Wachtog for P2041
>>
>> I am using the core watchdog of the P2041 on the kmp204x board.
>>
>> For the watchdog initialization I use the mpc85xx framework and the
>> powerpc register definitions. However, I had to modify both for the
>> following reasons (Patches 1 to 4):
>> -the e500mc register implementation differs from other ppc -the
>> watchdog init function was missing
>>
>> Additional function was added to the kmp204x board to use the core WD
>> reset in conjunction with the board specific reset controller (Patches
>> 5 to 9):
>> -trigger a core reset flow upon core WD reset request -check for core
>> WD reset occurance and set the reset reason
>> register accordingly.
>>
>> Regards
>> Rainer
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2014-07-16 15:29 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
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 [this message]
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=53C69A60.40503@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 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.