From: Zumeng Chen <zumeng.chen@windriver.com>
To: <shubhrajyoti@ti.com>, <wim@iguana.be>
Cc: <linux-watchdog@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <tony@atomide.com>,
<paul.gortmaker@windriver.com>
Subject: Re: [PATCH v2 0/2] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework
Date: Mon, 9 Jul 2012 12:46:30 +0800 [thread overview]
Message-ID: <4FFA6226.9010605@windriver.com> (raw)
In-Reply-To: <1341808779-25532-1-git-send-email-zumeng.chen@windriver.com>
The changes have been validated on omap3530evm
Normal reboot
root@ti-omap3:~# dmesg|grep WDT
omap_wdt: OMAP WDTimer Rev 0x31: Initial timeout 0sec status= 0x0
root@ti-omap3:~#
root@ti-omap3:~# echo 1 >/dev/watchdog
Boot from WDT
root@ti-omap3:~# dmesg|grep WDT
omap_wdt: OMAP WDTimer Rev 0x31: Initial timeout 0sec status= 0x1
root@ti-omap3:~#
Regards,
zumeng
于 2012年07月09日 12:39, Zumeng Chen 写道:
> Hello,
>
> The following patches based on the 3.5-rc6 from Wim, which
> are based on:
>
> 1 ) bootstatus fix for omap3,
>
> 2 ) omap-wdt framework update cater for the current framework
> as Shubhrajyoti comments mentioned.
>
> Regards,
> Zumeng
>
> Linux 3.5-rc6 (2012-07-07 17:23:56 -0700)
>
> Zumeng Chen (3):
> Watchdog: Omap: Changes for the new watchdog framework
> Watchdog: Omap: select watchdog core for framework change
> Watchdog: Omap: get the bootstatus for OMAP2Plus
>
> arch/arm/mach-omap2/prcm.c | 5 +-
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/omap_wdt.c | 338 ++++++++++++++++---------------------------
> drivers/watchdog/omap_wdt.h | 5 +
> 4 files changed, 133 insertions(+), 216 deletions(-)
>
> --
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Zumeng Chen <zumeng.chen@windriver.com>
To: shubhrajyoti@ti.com, wim@iguana.be
Cc: linux-watchdog@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, tony@atomide.com,
paul.gortmaker@windriver.com
Subject: Re: [PATCH v2 0/2] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework
Date: Mon, 9 Jul 2012 12:46:30 +0800 [thread overview]
Message-ID: <4FFA6226.9010605@windriver.com> (raw)
In-Reply-To: <1341808779-25532-1-git-send-email-zumeng.chen@windriver.com>
The changes have been validated on omap3530evm
Normal reboot
root@ti-omap3:~# dmesg|grep WDT
omap_wdt: OMAP WDTimer Rev 0x31: Initial timeout 0sec status= 0x0
root@ti-omap3:~#
root@ti-omap3:~# echo 1 >/dev/watchdog
Boot from WDT
root@ti-omap3:~# dmesg|grep WDT
omap_wdt: OMAP WDTimer Rev 0x31: Initial timeout 0sec status= 0x1
root@ti-omap3:~#
Regards,
zumeng
于 2012年07月09日 12:39, Zumeng Chen 写道:
> Hello,
>
> The following patches based on the 3.5-rc6 from Wim, which
> are based on:
>
> 1 ) bootstatus fix for omap3,
>
> 2 ) omap-wdt framework update cater for the current framework
> as Shubhrajyoti comments mentioned.
>
> Regards,
> Zumeng
>
> Linux 3.5-rc6 (2012-07-07 17:23:56 -0700)
>
> Zumeng Chen (3):
> Watchdog: Omap: Changes for the new watchdog framework
> Watchdog: Omap: select watchdog core for framework change
> Watchdog: Omap: get the bootstatus for OMAP2Plus
>
> arch/arm/mach-omap2/prcm.c | 5 +-
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/omap_wdt.c | 338 ++++++++++++++++---------------------------
> drivers/watchdog/omap_wdt.h | 5 +
> 4 files changed, 133 insertions(+), 216 deletions(-)
>
> --
> 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
--
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
WARNING: multiple messages have this Message-ID (diff)
From: zumeng.chen@windriver.com (Zumeng Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework
Date: Mon, 9 Jul 2012 12:46:30 +0800 [thread overview]
Message-ID: <4FFA6226.9010605@windriver.com> (raw)
In-Reply-To: <1341808779-25532-1-git-send-email-zumeng.chen@windriver.com>
The changes have been validated on omap3530evm
Normal reboot
root at ti-omap3:~# dmesg|grep WDT
omap_wdt: OMAP WDTimer Rev 0x31: Initial timeout 0sec status= 0x0
root at ti-omap3:~#
root at ti-omap3:~# echo 1 >/dev/watchdog
Boot from WDT
root at ti-omap3:~# dmesg|grep WDT
omap_wdt: OMAP WDTimer Rev 0x31: Initial timeout 0sec status= 0x1
root at ti-omap3:~#
Regards,
zumeng
? 2012?07?09? 12:39, Zumeng Chen ??:
> Hello,
>
> The following patches based on the 3.5-rc6 from Wim, which
> are based on:
>
> 1 ) bootstatus fix for omap3,
>
> 2 ) omap-wdt framework update cater for the current framework
> as Shubhrajyoti comments mentioned.
>
> Regards,
> Zumeng
>
> Linux 3.5-rc6 (2012-07-07 17:23:56 -0700)
>
> Zumeng Chen (3):
> Watchdog: Omap: Changes for the new watchdog framework
> Watchdog: Omap: select watchdog core for framework change
> Watchdog: Omap: get the bootstatus for OMAP2Plus
>
> arch/arm/mach-omap2/prcm.c | 5 +-
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/omap_wdt.c | 338 ++++++++++++++++---------------------------
> drivers/watchdog/omap_wdt.h | 5 +
> 4 files changed, 133 insertions(+), 216 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-09 4:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 4:39 [PATCH v2 0/2] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` [PATCH 1/3] Watchdog: Omap: Changes for the new " Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` [PATCH 2/3] Watchdog: Omap: select watchdog core for framework change Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` [PATCH 3/3] Watchdog: Omap: get the bootstatus for OMAP2Plus Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 4:39 ` Zumeng Chen
2012-07-09 16:40 ` Kevin Hilman
2012-07-09 16:40 ` Kevin Hilman
2012-07-09 16:40 ` Kevin Hilman
2012-07-10 0:34 ` Zumeng Chen
2012-07-10 0:34 ` Zumeng Chen
2012-07-10 0:34 ` Zumeng Chen
2012-07-09 4:46 ` Zumeng Chen [this message]
2012-07-09 4:46 ` [PATCH v2 0/2] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework Zumeng Chen
2012-07-09 4:46 ` Zumeng Chen
2012-07-09 6:02 ` Vaibhav Hiremath
2012-07-09 6:02 ` Vaibhav Hiremath
2012-07-09 6:02 ` Vaibhav Hiremath
2012-07-09 6:00 ` Zumeng Chen
2012-07-09 6:00 ` Zumeng Chen
2012-07-09 6:00 ` Zumeng Chen
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=4FFA6226.9010605@windriver.com \
--to=zumeng.chen@windriver.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=shubhrajyoti@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.