From: Sergey Lapin <slapin@ossfans.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Hardware watchdog support for AT91SAM9260 CPU
Date: Thu, 23 Oct 2008 03:22:53 +0400 [thread overview]
Message-ID: <20081022232253.GA6694@build.ossfans.org> (raw)
In-Reply-To: <20081022214944.GE15487@game.jcrosoft.org>
On Wed, Oct 22, 2008 at 11:49:44PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 02:29 Fri 15 Aug , Sergey Lapin wrote:
Dear Jean-Christophe,
thanks a lot for your review.
> >
> Are you from ADI?
No, but this file structure is a lot based on blackfin watchdog
and I have too little code to make it int full intellectual
property, IMHO.
> > + *
> > + * Licensed under the GPL-2 or later.
> > + */
> > +
> > +#include <common.h>
> > +#include <watchdog.h>
> > +#include <asm/arch/hardware.h>
> > +#include <asm/arch/io.h>
> > +
> > +#ifdef CONFIG_HW_WATCHDOG
> no need please remove
Ok,
> > +#define AT91_WDT_CR (AT91_WDT+0x00)
> ^
> please add space arround '+'
Ok.
> > +#define AT91_WDT_MR (AT91_WDT+0x04)
> > +#define AT91_WDT_SR (AT91_WDT+0x08)
> > +
> > +void hw_watchdog_reset(void)
> > +{
> > + at91_sys_write(AT91_WDT_CR, 0xa5000001);
> ^^^^
> please use macro you can import them
> from Linux
Is this kind of watchdog supported in Linux already? When I submitted
this file it was not yet.
All the best,
S.
prev parent reply other threads:[~2008-10-22 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 22:29 [U-Boot] [PATCH] Hardware watchdog support for AT91SAM9260 CPU Sergey Lapin
2008-08-14 22:29 ` [U-Boot] [PATCH] Custom AFEB9260 board support Sergey Lapin
2008-10-12 22:07 ` Wolfgang Denk
2008-10-24 7:44 ` Jean-Christophe PLAGNIOL-VILLARD
2008-08-14 22:32 ` [U-Boot] [PATCH] Hardware watchdog support for AT91SAM9260 CPU Sergey Lapin
2008-10-22 21:49 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-22 23:22 ` Sergey Lapin [this message]
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=20081022232253.GA6694@build.ossfans.org \
--to=slapin@ossfans.org \
--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