From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Varadarajan\, Charulatha" <charu@ti.com>
Cc: tony@atomide.com, wim@iguana.be, linux-omap@vger.kernel.org,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, paul@pwsan.com,
b-cousson@ti.com, rnayak@ti.com, santosh.shilimkar@ti.com,
p-basak2@ti.com
Subject: Re: [PATCH v2] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init
Date: Tue, 05 Oct 2010 09:35:08 -0700 [thread overview]
Message-ID: <87fwwktx6r.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1286015771-22041-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Sat, 2 Oct 2010 16:06:11 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> Inorder to avoid any assumptions from bootloader, the watchdog
> timer module is reset during init. This enables the watchdog
> timer.
>
> Therefore, it is required to disable WDT after it is reset
> during init. Otherwise the system would reboot as per the default
> watchdog timer registers settings.
>
> Later, when the watchdog driver is loaded, the watchdog timer settings
> is adjusted as per the default timer_margin set in the driver and the
> driver would supports the normal operations supported by OMAP watchdog
> timer.
>
> Link to related discussions:
> https://patchwork.kernel.org/patch/219072/
>
> Issue reported by Kevin can be found at:
> https://patchwork.kernel.org/patch/217262/
>
> Signed-off-by: Charulatha V <charu@ti.com>
> Reported-by: Kevin Hilman <khilman@deeprootsystems.com>
Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
Tony, this should queue up for .37 on top of my pm-hwmods branch.
It applies cleanly to current l-o master.
Kevin
next prev parent reply other threads:[~2010-10-05 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 10:36 [PATCH v2] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init Varadarajan, Charulatha
2010-10-05 16:35 ` Kevin Hilman [this message]
2010-10-05 22:16 ` Tony Lindgren
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=87fwwktx6r.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
--cc=wim@iguana.be \
/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