From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ulrik Bech Hald <ubh@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] OMAP3:WDT:Enable IVA, SECURE and minor bugfixes
Date: Tue, 09 Jun 2009 07:45:19 -0700 [thread overview]
Message-ID: <87r5xtzcsg.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1244495293-17244-1-git-send-email-ubh@ti.com> (Ulrik Bech Hald's message of "Mon\, 8 Jun 2009 16\:08\:10 -0500")
Ulrik Bech Hald <ubh@ti.com> writes:
> This patch series enables support for IVA and SECURE
> WDTs, available on omap34xx.
> For omap34xx devices the WDT will be accessible
> (when present) through:
> SECURE: /dev/watchdog1
> MPU: /dev/watchdog2
> IVA: /dev/watchdog3
>
> For devices older than omap34xx only MPU WDT is present
> and will be accessible through /dev/watchdog
I think you should make the MPU WDT the first one since it will always
be present.
> The series also fixes two bugs:
>
> 1) Correct timeout value is not loaded upon opening the
> watchdog device.
>
> 2) clks are not enabled when accessing registers in probe
Can you fix these existing bugs in a separate patch before you add the
new features.
Kevin
next prev parent reply other threads:[~2009-06-09 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 21:08 [PATCH 0/3] OMAP3:WDT:Enable IVA, SECURE and minor bugfixes Ulrik Bech Hald
2009-06-08 21:08 ` [PATCH 1/3] OMAP3:WDT:Register IVA,SECURE, make clks accessible Ulrik Bech Hald
2009-06-08 21:08 ` [PATCH 2/3] OMAP3:WDT:Enable support for IVA and SECURE Ulrik Bech Hald
2009-06-08 21:08 ` [PATCH 3/3] OMAP3:WDT:Enable clk in probe, trigger timer reload Ulrik Bech Hald
2009-06-09 14:47 ` [PATCH 2/3] OMAP3:WDT:Enable support for IVA and SECURE Kevin Hilman
2009-06-09 19:28 ` Hald, Ulrik Bech
2009-06-09 21:10 ` Kevin Hilman
2009-06-15 16:19 ` Hald, Ulrik Bech
2009-06-15 16:26 ` Kevin Hilman
2009-06-09 14:45 ` Kevin Hilman [this message]
2009-06-09 18:02 ` [PATCH 0/3] OMAP3:WDT:Enable IVA, SECURE and minor bugfixes Hald, Ulrik Bech
2009-06-09 18:16 ` Kevin Hilman
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=87r5xtzcsg.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=ubh@ti.com \
/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.