From: nbowler@elliptictech.com (Nick Bowler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] SP805 updates for Versatile Express
Date: Fri, 15 Jul 2011 11:03:59 -0400 [thread overview]
Message-ID: <1310742242-14647-1-git-send-email-nbowler@elliptictech.com> (raw)
Here are some updates to get the SP805 watchdog working on the ARM
Versatile Express. The first two patches fix observed issues; the
third fixes a potential (but not observed) issue with asynchronous
posted writes.
All three patches are independent and should be applicable in any
order, with some fuzz on the third.
next reply other threads:[~2011-07-15 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 15:03 Nick Bowler [this message]
2011-07-15 15:04 ` [PATCH 1/3] ARM: vexpress: Add clock definition for the SP805 Nick Bowler
2011-07-15 15:04 ` [PATCH 2/3] watchdog: sp805: Don't write 0 to the load value register Nick Bowler
2011-07-15 15:04 ` [PATCH 3/3] watchdog: sp805: Flush posted writes in enable/disable Nick Bowler
2011-07-15 20:59 ` [PATCH 0/3] SP805 updates for Versatile Express Wim Van Sebroeck
2011-07-18 9:44 ` Russell King - ARM Linux
2011-07-19 13:15 ` Nick Bowler
2011-07-22 18:31 ` Wim Van Sebroeck
2011-07-22 19:01 ` Nick Bowler
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=1310742242-14647-1-git-send-email-nbowler@elliptictech.com \
--to=nbowler@elliptictech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).