From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ulrik Bech Hald <ubh@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1] OMAP3:WDT:Enable clk in probe, trigger timer reload
Date: Fri, 12 Jun 2009 09:13:13 -0700 [thread overview]
Message-ID: <87my8dig6e.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1244822737-20446-1-git-send-email-ubh@ti.com> (Ulrik Bech Hald's message of "Fri\, 12 Jun 2009 11\:05\:37 -0500")
Ulrik Bech Hald <ubh@ti.com> writes:
> This patch contains two bugfixes:
>
> 1)In omap_wdt_probe() the watchdog is reset and disabled. This
> requires register access and the clks needs to be enabled temporarily
>
> 2)In omap_wdt_open() the timer register needs to be reloaded
> to trigger a new timer value (the default of 60s)
>
> Signed-off-by: Ulrik Bech Hald <ubh@ti.com>
Can you change the subject slightly to something like:
watchdog: OMAP fixes: enable clock in probe, trigger timer reload
Also add which OMAP platforms you have tested on since this affects
OMAP2, OMAP3 and presuably OMAP4.
After that, you can add
Reviewed-by: Kevin Hilman <khilman@ti.deeprootsystems.com>
And sent to watchdog maintiner, and CC linux-omap, here's excerpt from
MAINTAINERS:
WATCHDOG DEVICE DRIVERS
P: Wim Van Sebroeck
M: wim@iguana.be
T: git git://git.kernel.org/pub/scm/linux/kernel/git/wim/linux-2.6-watchdog.git
S: Maintained
F: Documentation/watchdog/
F: drivers/watchdog/
F: include/linux/watchdog.h
> ---
> drivers/watchdog/omap_wdt.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
> mode change 100644 => 100755 drivers/watchdog/omap_wdt.c
>
> diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
> old mode 100644
> new mode 100755
> index f271385..3ed571a
> --- a/drivers/watchdog/omap_wdt.c
> +++ b/drivers/watchdog/omap_wdt.c
> @@ -159,6 +159,7 @@ static int omap_wdt_open(struct inode *inode, struct file *file)
> file->private_data = (void *) wdev;
>
> omap_wdt_set_timeout(wdev);
> + omap_wdt_ping(wdev); /* trigger loading of new timeout value */
> omap_wdt_enable(wdev);
>
> return nonseekable_open(inode, file);
> @@ -313,6 +314,9 @@ static int __devinit omap_wdt_probe(struct platform_device *pdev)
>
> platform_set_drvdata(pdev, wdev);
>
> + clk_enable(wdev->ick);
> + clk_enable(wdev->fck);
> +
> omap_wdt_disable(wdev);
> omap_wdt_adjust_timeout(timer_margin);
>
> @@ -332,6 +336,9 @@ static int __devinit omap_wdt_probe(struct platform_device *pdev)
> /* autogate OCP interface clock */
> __raw_writel(0x01, wdev->base + OMAP_WATCHDOG_SYS_CONFIG);
>
> + clk_disable(wdev->ick);
> + clk_disable(wdev->fck);
> +
> omap_wdt_dev = pdev;
>
> return 0;
> --
> 1.5.4.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-12 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 16:05 [PATCH 1/1] OMAP3:WDT:Enable clk in probe, trigger timer reload Ulrik Bech Hald
2009-06-12 16:13 ` Kevin Hilman [this message]
2009-06-13 3:57 ` Hugo Vincent
2009-06-16 13:01 ` Premi, Sanjeev
2009-06-16 14:13 ` Hald, Ulrik Bech
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=87my8dig6e.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox