From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: paul@pwsan.com, linux-watchdog@vger.kernel.org, tony@atomide.com,
rnayak@ti.com, p-basak2@ti.com, wim@iguana.be,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
b-cousson@ti.com
Subject: Re: [PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init
Date: Thu, 30 Sep 2010 06:57:47 -0700 [thread overview]
Message-ID: <87k4m3jpus.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285834270-32766-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 30 Sep 2010 13:41:10 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> With OMAP2PLUS watchdog implemented in hwmod fw way, the
> module is reset during init.
Please drop this sentence, as it's not directly related to hwmod, but
related to hardware reset, and was previously masked by most bootloaders.
> After a watchdog timer module reset, the WDTs are enabled. The
> default time for a system reset after a watchdog module reset
> is ~10s as per the default value of the WDT registers. Hence
> the system would be reset after 10s, if watchdog is not disabled
> within 10s.
>
> This patch fixes the above issue by disabling the watchdog timer
> after reset during initialization of devices.
Should also describe what happends if/when the watchdog driver is
loaded.
Kevin
> Signed-off-by: Charulatha V <charu@ti.com>
> Reported-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> This patch is dependent on the below patch series (wdt hwmod) and
> is created on top of pm-core branch.
> http://www.spinics.net/lists/linux-omap/msg37043.html
>
> arch/arm/mach-omap2/devices.c | 44 +++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 44 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 8e2f0aa..9f44fc6 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -916,11 +916,55 @@ static inline void omap_init_vout(void) {}
>
> /*-------------------------------------------------------------------------*/
>
> +/*
> + * WDT mdoule is reset during init which enables the watchdog.
> + * Hence it is required to disable the watchdog after the WDT reset
> + * during init. Otherwise the system would reboot as per the default
> + * watchdog timer registers settings.
> + */
> +#define OMAP_WDT_WPS (0x34)
> +#define OMAP_WDT_SPR (0x48)
> +
> +static int omap2_disable_wdt(struct omap_hwmod *oh, void *user)
> +{
> + void __iomem *base;
> +
> + if (!oh)
> + pr_err("Could not look up wdtimer_hwmod\n");
> +
> + base = oh->_mpu_rt_va;
> +
> + /* Enable the clocks before accessing the WDT registers */
> + omap_hwmod_enable(oh);
> +
> + /* sequence required to disable watchdog */
> + __raw_writel(0xAAAA, base + OMAP_WDT_SPR); /* TIMER_MODE */
> + while (__raw_readl(base + OMAP_WDT_WPS) & 0x10)
> + cpu_relax();
> +
> + __raw_writel(0x5555, base + OMAP_WDT_SPR); /* TIMER_MODE */
> + while (__raw_readl(base + OMAP_WDT_WPS) & 0x10)
> + cpu_relax();
> +
> + omap_hwmod_idle(oh);
> +
> + return 0;
> +}
> +
> +static void __init omap_disable_wdt(void)
> +{
> + if (cpu_class_is_omap2())
> + omap_hwmod_for_each_by_class("wd_timer",
> + omap2_disable_wdt, NULL);
> + return;
> +}
> +
> static int __init omap2_init_devices(void)
> {
> /* please keep these calls, and their implementations above,
> * in alphabetical order so they're easier to sort through.
> */
> + omap_disable_wdt();
> omap_hsmmc_reset();
> omap_init_camera();
> omap_init_mbox();
WARNING: multiple messages have this Message-ID (diff)
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, p-basak2@ti.com
Subject: Re: [PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init
Date: Thu, 30 Sep 2010 06:57:47 -0700 [thread overview]
Message-ID: <87k4m3jpus.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285834270-32766-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 30 Sep 2010 13:41:10 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> With OMAP2PLUS watchdog implemented in hwmod fw way, the
> module is reset during init.
Please drop this sentence, as it's not directly related to hwmod, but
related to hardware reset, and was previously masked by most bootloaders.
> After a watchdog timer module reset, the WDTs are enabled. The
> default time for a system reset after a watchdog module reset
> is ~10s as per the default value of the WDT registers. Hence
> the system would be reset after 10s, if watchdog is not disabled
> within 10s.
>
> This patch fixes the above issue by disabling the watchdog timer
> after reset during initialization of devices.
Should also describe what happends if/when the watchdog driver is
loaded.
Kevin
> Signed-off-by: Charulatha V <charu@ti.com>
> Reported-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> This patch is dependent on the below patch series (wdt hwmod) and
> is created on top of pm-core branch.
> http://www.spinics.net/lists/linux-omap/msg37043.html
>
> arch/arm/mach-omap2/devices.c | 44 +++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 44 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 8e2f0aa..9f44fc6 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -916,11 +916,55 @@ static inline void omap_init_vout(void) {}
>
> /*-------------------------------------------------------------------------*/
>
> +/*
> + * WDT mdoule is reset during init which enables the watchdog.
> + * Hence it is required to disable the watchdog after the WDT reset
> + * during init. Otherwise the system would reboot as per the default
> + * watchdog timer registers settings.
> + */
> +#define OMAP_WDT_WPS (0x34)
> +#define OMAP_WDT_SPR (0x48)
> +
> +static int omap2_disable_wdt(struct omap_hwmod *oh, void *user)
> +{
> + void __iomem *base;
> +
> + if (!oh)
> + pr_err("Could not look up wdtimer_hwmod\n");
> +
> + base = oh->_mpu_rt_va;
> +
> + /* Enable the clocks before accessing the WDT registers */
> + omap_hwmod_enable(oh);
> +
> + /* sequence required to disable watchdog */
> + __raw_writel(0xAAAA, base + OMAP_WDT_SPR); /* TIMER_MODE */
> + while (__raw_readl(base + OMAP_WDT_WPS) & 0x10)
> + cpu_relax();
> +
> + __raw_writel(0x5555, base + OMAP_WDT_SPR); /* TIMER_MODE */
> + while (__raw_readl(base + OMAP_WDT_WPS) & 0x10)
> + cpu_relax();
> +
> + omap_hwmod_idle(oh);
> +
> + return 0;
> +}
> +
> +static void __init omap_disable_wdt(void)
> +{
> + if (cpu_class_is_omap2())
> + omap_hwmod_for_each_by_class("wd_timer",
> + omap2_disable_wdt, NULL);
> + return;
> +}
> +
> static int __init omap2_init_devices(void)
> {
> /* please keep these calls, and their implementations above,
> * in alphabetical order so they're easier to sort through.
> */
> + omap_disable_wdt();
> omap_hsmmc_reset();
> omap_init_camera();
> omap_init_mbox();
WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init
Date: Thu, 30 Sep 2010 06:57:47 -0700 [thread overview]
Message-ID: <87k4m3jpus.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285834270-32766-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 30 Sep 2010 13:41:10 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> With OMAP2PLUS watchdog implemented in hwmod fw way, the
> module is reset during init.
Please drop this sentence, as it's not directly related to hwmod, but
related to hardware reset, and was previously masked by most bootloaders.
> After a watchdog timer module reset, the WDTs are enabled. The
> default time for a system reset after a watchdog module reset
> is ~10s as per the default value of the WDT registers. Hence
> the system would be reset after 10s, if watchdog is not disabled
> within 10s.
>
> This patch fixes the above issue by disabling the watchdog timer
> after reset during initialization of devices.
Should also describe what happends if/when the watchdog driver is
loaded.
Kevin
> Signed-off-by: Charulatha V <charu@ti.com>
> Reported-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> This patch is dependent on the below patch series (wdt hwmod) and
> is created on top of pm-core branch.
> http://www.spinics.net/lists/linux-omap/msg37043.html
>
> arch/arm/mach-omap2/devices.c | 44 +++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 44 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 8e2f0aa..9f44fc6 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -916,11 +916,55 @@ static inline void omap_init_vout(void) {}
>
> /*-------------------------------------------------------------------------*/
>
> +/*
> + * WDT mdoule is reset during init which enables the watchdog.
> + * Hence it is required to disable the watchdog after the WDT reset
> + * during init. Otherwise the system would reboot as per the default
> + * watchdog timer registers settings.
> + */
> +#define OMAP_WDT_WPS (0x34)
> +#define OMAP_WDT_SPR (0x48)
> +
> +static int omap2_disable_wdt(struct omap_hwmod *oh, void *user)
> +{
> + void __iomem *base;
> +
> + if (!oh)
> + pr_err("Could not look up wdtimer_hwmod\n");
> +
> + base = oh->_mpu_rt_va;
> +
> + /* Enable the clocks before accessing the WDT registers */
> + omap_hwmod_enable(oh);
> +
> + /* sequence required to disable watchdog */
> + __raw_writel(0xAAAA, base + OMAP_WDT_SPR); /* TIMER_MODE */
> + while (__raw_readl(base + OMAP_WDT_WPS) & 0x10)
> + cpu_relax();
> +
> + __raw_writel(0x5555, base + OMAP_WDT_SPR); /* TIMER_MODE */
> + while (__raw_readl(base + OMAP_WDT_WPS) & 0x10)
> + cpu_relax();
> +
> + omap_hwmod_idle(oh);
> +
> + return 0;
> +}
> +
> +static void __init omap_disable_wdt(void)
> +{
> + if (cpu_class_is_omap2())
> + omap_hwmod_for_each_by_class("wd_timer",
> + omap2_disable_wdt, NULL);
> + return;
> +}
> +
> static int __init omap2_init_devices(void)
> {
> /* please keep these calls, and their implementations above,
> * in alphabetical order so they're easier to sort through.
> */
> + omap_disable_wdt();
> omap_hsmmc_reset();
> omap_init_camera();
> omap_init_mbox();
next prev parent reply other threads:[~2010-09-30 13:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 8:11 [PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init Varadarajan, Charulatha
2010-09-30 8:11 ` Varadarajan, Charulatha
2010-09-30 9:07 ` Cousson, Benoit
2010-09-30 9:07 ` Cousson, Benoit
2010-09-30 13:55 ` Kevin Hilman
2010-09-30 13:55 ` Kevin Hilman
2010-09-30 14:12 ` Cousson, Benoit
2010-09-30 14:12 ` Cousson, Benoit
2010-09-30 14:51 ` Kevin Hilman
2010-09-30 14:51 ` Kevin Hilman
2010-09-30 15:07 ` Tony Lindgren
2010-09-30 15:07 ` Tony Lindgren
2010-09-30 15:55 ` Varadarajan, Charulatha
2010-09-30 15:55 ` Varadarajan, Charulatha
2010-09-30 16:32 ` Varadarajan, Charulatha
2010-09-30 16:32 ` Varadarajan, Charulatha
2010-09-30 16:43 ` Paul Walmsley
2010-09-30 16:43 ` Paul Walmsley
2010-09-30 16:51 ` Tony Lindgren
2010-09-30 16:51 ` Tony Lindgren
2010-09-30 16:46 ` Cousson, Benoit
2010-09-30 16:46 ` Cousson, Benoit
2010-09-30 16:57 ` Cousson, Benoit
2010-09-30 16:57 ` Cousson, Benoit
2010-09-30 17:06 ` Varadarajan, Charulatha
2010-09-30 17:06 ` Varadarajan, Charulatha
2010-09-30 17:05 ` Shilimkar, Santosh
2010-09-30 17:05 ` Shilimkar, Santosh
2010-09-30 17:11 ` Kevin Hilman
2010-09-30 17:11 ` Kevin Hilman
2010-10-01 7:26 ` Shilimkar, Santosh
2010-10-01 7:26 ` Shilimkar, Santosh
2010-10-01 13:33 ` Varadarajan, Charulatha
2010-10-01 13:33 ` Varadarajan, Charulatha
2010-10-01 14:43 ` Kevin Hilman
2010-10-01 14:43 ` Kevin Hilman
2010-10-01 17:12 ` Cousson, Benoit
2010-10-01 17:12 ` Cousson, Benoit
2010-09-30 13:57 ` Kevin Hilman [this message]
2010-09-30 13:57 ` Kevin Hilman
2010-09-30 13:57 ` Kevin Hilman
2010-09-30 16:36 ` Varadarajan, Charulatha
2010-09-30 16:36 ` Varadarajan, Charulatha
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=87k4m3jpus.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=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 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.