All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zumeng Chen <zumeng.chen@windriver.com>
To: <khilman@ti.com>, <shubhrajyoti@ti.com>,
	<linux-watchdog@vger.kernel.org>, <hvaibhav@ti.com>
Cc: <wim@iguana.be>, <linux-omap@vger.kernel.org>, <tony@atomide.com>,
	<paul.gortmaker@windriver.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH RESEND V3 0/3] Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework
Date: Sun, 15 Jul 2012 15:44:03 +0800	[thread overview]
Message-ID: <1342338246-29101-1-git-send-email-zumeng.chen@windriver.com> (raw)

Hello,

The following patches based on the 3.5-rc6 from Wim, which
focus on:

1. bootstatus fix for omap3,

2. omap-wdt framework update cater for the current framework
   as Shubhrajyoti comments mentioned.

V3 changes:

1. New comments updated as Kevin mentioned in the third patch;
2. 3530evm works well,
   AM33xx seems work well with the following changes:
	+   if (cpu_is_am335x())
	+       return omap2_prm_read_mod_reg(AM33XX_PRM_DEVICE_MOD,
	+           AM33XX_PRM_RSTST_OFFSET) & 0x7f;
   But since some definitions not ready for am33xx, so I don't
   give the patch, if they have been updated, feel free to take these. 

Regards,

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 OMAP34xx

 arch/arm/mach-omap2/prcm.c  |    9 +-
 drivers/watchdog/Kconfig    |    1 +
 drivers/watchdog/omap_wdt.c |  342 ++++++++++++++++---------------------------
 drivers/watchdog/omap_wdt.h |    5 +
 4 files changed, 136 insertions(+), 221 deletions(-)

-- 
1.7.5.4


WARNING: multiple messages have this Message-ID (diff)
From: Zumeng Chen <zumeng.chen@windriver.com>
To: khilman@ti.com, shubhrajyoti@ti.com,
	linux-watchdog@vger.kernel.org, hvaibhav@ti.com
Cc: wim@iguana.be, linux-omap@vger.kernel.org, tony@atomide.com,
	paul.gortmaker@windriver.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND V3 0/3] Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework
Date: Sun, 15 Jul 2012 15:44:03 +0800	[thread overview]
Message-ID: <1342338246-29101-1-git-send-email-zumeng.chen@windriver.com> (raw)

Hello,

The following patches based on the 3.5-rc6 from Wim, which
focus on:

1. bootstatus fix for omap3,

2. omap-wdt framework update cater for the current framework
   as Shubhrajyoti comments mentioned.

V3 changes:

1. New comments updated as Kevin mentioned in the third patch;
2. 3530evm works well,
   AM33xx seems work well with the following changes:
	+   if (cpu_is_am335x())
	+       return omap2_prm_read_mod_reg(AM33XX_PRM_DEVICE_MOD,
	+           AM33XX_PRM_RSTST_OFFSET) & 0x7f;
   But since some definitions not ready for am33xx, so I don't
   give the patch, if they have been updated, feel free to take these. 

Regards,

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 OMAP34xx

 arch/arm/mach-omap2/prcm.c  |    9 +-
 drivers/watchdog/Kconfig    |    1 +
 drivers/watchdog/omap_wdt.c |  342 ++++++++++++++++---------------------------
 drivers/watchdog/omap_wdt.h |    5 +
 4 files changed, 136 insertions(+), 221 deletions(-)

-- 
1.7.5.4


WARNING: multiple messages have this Message-ID (diff)
From: zumeng.chen@windriver.com (Zumeng Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND V3 0/3] Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework
Date: Sun, 15 Jul 2012 15:44:03 +0800	[thread overview]
Message-ID: <1342338246-29101-1-git-send-email-zumeng.chen@windriver.com> (raw)

Hello,

The following patches based on the 3.5-rc6 from Wim, which
focus on:

1. bootstatus fix for omap3,

2. omap-wdt framework update cater for the current framework
   as Shubhrajyoti comments mentioned.

V3 changes:

1. New comments updated as Kevin mentioned in the third patch;
2. 3530evm works well,
   AM33xx seems work well with the following changes:
	+   if (cpu_is_am335x())
	+       return omap2_prm_read_mod_reg(AM33XX_PRM_DEVICE_MOD,
	+           AM33XX_PRM_RSTST_OFFSET) & 0x7f;
   But since some definitions not ready for am33xx, so I don't
   give the patch, if they have been updated, feel free to take these. 

Regards,

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 OMAP34xx

 arch/arm/mach-omap2/prcm.c  |    9 +-
 drivers/watchdog/Kconfig    |    1 +
 drivers/watchdog/omap_wdt.c |  342 ++++++++++++++++---------------------------
 drivers/watchdog/omap_wdt.h |    5 +
 4 files changed, 136 insertions(+), 221 deletions(-)

-- 
1.7.5.4

             reply	other threads:[~2012-07-15  7:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15  7:44 Zumeng Chen [this message]
2012-07-15  7:44 ` [PATCH RESEND V3 0/3] Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework Zumeng Chen
2012-07-15  7:44 ` Zumeng Chen
2012-07-15  7:44 ` [PATCH RESEND v3 1/3] Watchdog: Omap: Changes for the new " Zumeng Chen
2012-07-15  7:44   ` Zumeng Chen
2012-07-15  7:44   ` Zumeng Chen
2012-07-16 13:10   ` Hiremath, Vaibhav
2012-07-16 13:10     ` Hiremath, Vaibhav
2012-07-16 13:10     ` Hiremath, Vaibhav
2012-07-15  7:44 ` [PATCH RESEND v3 2/3] Watchdog: Omap: select watchdog core for framework change Zumeng Chen
2012-07-15  7:44   ` Zumeng Chen
2012-07-15  7:44   ` Zumeng Chen
2012-07-15  7:44 ` [PATCH RESEND v3 3/3] Watchdog: Omap: get the bootstatus for OMAP34xx Zumeng Chen
2012-07-15  7:44   ` Zumeng Chen
2012-07-15  7:44   ` Zumeng Chen
2012-07-16 13:10 ` [PATCH RESEND V3 0/3] Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework Hiremath, Vaibhav
2012-07-16 13:10   ` Hiremath, Vaibhav
2012-07-16 13:10   ` Hiremath, Vaibhav
2012-07-16 14:55   ` zumeng.chen
2012-07-16 14:55     ` zumeng.chen
2012-07-16 14:55     ` 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=1342338246-29101-1-git-send-email-zumeng.chen@windriver.com \
    --to=zumeng.chen@windriver.com \
    --cc=hvaibhav@ti.com \
    --cc=khilman@ti.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.