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 v8 0/6] OMAP: WDT: Implement WDT in hwmod way
Date: Tue, 28 Sep 2010 18:05:36 -0700 [thread overview]
Message-ID: <877hi5740v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285252363-3630-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 23 Sep 2010 20:02:37 +0530")
Hi Charu,
"Varadarajan, Charulatha" <charu@ti.com> writes:
> Series of patches to port watchdog module to use hwmod APIs
> for OMAP2PLUS chips and use runtime APIs for all OMAP chips.
> For this hwmod database for OMAP2PLUS watchdog instances are
> populated and implements watchdog module to use PM runtime APIs.
>
> This patch series is generated on "origin/pm-core" which
> has Kevin's pm-next series, the runtime PM core patch series,
> and a collection of hwmod fixes that Paul/Benoit have lined up
> for 2.6.37.
>
> Tested on OMAP2430, OMAP4430 (ES1.0 & ES2.0), OMAP3430 SDP boards
> and zoom3 board. Also verified that this patch series does not
> break the OMAP1 build.
I found a little snag with this series. Try testing with
omap2plus_defconfig and changing CONFIG_OMAP_WATCHDOG=n.
If CONFIG_OMAP_WATCHDOG is not enabled in the kernel config, the system
will reboot soon after bootup. One of the things the bootloader
historically has done was disable the watchdog so a driver wasn't needed.
With a reset of the IP triggered by the hwmod init, we lose this setting
and the watchog is armed by default.
I think we need to handle this case when CONFIG_OMAP_WATCHDOG=n in the
device init code by disabling the watchdog.
Kevin
> This series is tested on OMAP4430 ES2 using the below series
> (dependency series for ES2.0 silicon)
> http://www.spinics.net/lists/linux-omap/msg36023.html
>
> Version History:
> ---------------
> Version v8:
> *Enable wd_timer3 in the hwmod list
>
> Version v7:
> *Use EN_*SHIFT macros for module_bit and ST_*SHIFT macros for
> idlest_idle_bit in OMAP2&3 hwmod database
> (based on suggestions given by Paul for I2C hwmod series)
> *Remove new definitions of EN_*SHIFT macros as they already exist
> Some of the v7 links:
> https://patchwork.kernel.org/patch/197022/
>
> Version v6:
> *Split omap_init_wdt() into separate omap_init_wdt functions
> under mach-omap1 and mach-omap2 and set them up with
> subsys_initcall
> *Include wd_timer3 database for OMAP4
> *In hwmod database follow naming convention "wd_timerX"
> Some of the v6 links:
> http://www.spinics.net/lists/linux-omap/msg36678.html
> https://patchwork.kernel.org/patch/188242/
> https://patchwork.kernel.org/patch/188222/
>
> Version v5:
> *Delete wdt_runtime_resume and wdt_runtime_suspend
> functions as the fix for the return values in the generic
> runtime PM calls has been queued for 2.6.37 (see below link)
> https://lists.linux-foundation.org/pipermail/linux-pm/2010-September/028466.html
> Some of the v5 links:
> https://patchwork.kernel.org/patch/181812/
> https://patchwork.kernel.org/patch/181782/
> https://patchwork.kernel.org/patch/181772/
> https://patchwork.kernel.org/patch/181792/
>
> Version v4:
> *Implement hwmod adapdation first and then PM runtime adaptation
> as two different patches in the series
> *Remove inclusion of omap_device.h in the driver file.
> Some of the v4 links:
> https://patchwork.kernel.org/patch/174672/
> https://patchwork.kernel.org/patch/174662/
>
> Version v3:
> *Fix Minor comments like renaming omap1 watchdog structures
> with an omap1_ prefix
> Some of the v3 links:
> https://patchwork.kernel.org/patch/119698/
> https://patchwork.kernel.org/patch/119696/
>
> Version v2:
> *Rebase to latest kernel
> Some of the v2 links:
> http://www.spinics.net/lists/linux-omap/msg34741.html
> http://www.spinics.net/lists/linux-omap/msg34673.html
>
> Version v1:
> *Initial series
> Some of the v1 links:
> http://www.spinics.net/lists/linux-omap/msg30628.html
> http://www.spinics.net/lists/linux-omap/msg30625.html
>
> Benoit Cousson (1):
> OMAP4: hwmod data: Add watchdog timer
>
> Varadarajan, Charulatha (5):
> OMAP3: hwmod data: Add watchdog timer
> OMAP2420: hwmod data: Add watchdog timer
> OMAP2430: hwmod data: Add watchdog timer
> OMAP2PLUS: WDT: use omap_device_build for device registration
> OMAP: WDT: Use PM runtime APIs instead of clk FW APIs
>
> arch/arm/mach-omap1/devices.c | 27 ++++++
> arch/arm/mach-omap2/devices.c | 39 ++++++++
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 64 +++++++++++++
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 64 +++++++++++++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 66 ++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 135 ++++++++++++++++++++++++++++
> arch/arm/plat-omap/devices.c | 41 ---------
> drivers/watchdog/omap_wdt.c | 42 ++-------
> 8 files changed, 402 insertions(+), 76 deletions(-)
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 v8 0/6] OMAP: WDT: Implement WDT in hwmod way
Date: Tue, 28 Sep 2010 18:05:36 -0700 [thread overview]
Message-ID: <877hi5740v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285252363-3630-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 23 Sep 2010 20:02:37 +0530")
Hi Charu,
"Varadarajan, Charulatha" <charu@ti.com> writes:
> Series of patches to port watchdog module to use hwmod APIs
> for OMAP2PLUS chips and use runtime APIs for all OMAP chips.
> For this hwmod database for OMAP2PLUS watchdog instances are
> populated and implements watchdog module to use PM runtime APIs.
>
> This patch series is generated on "origin/pm-core" which
> has Kevin's pm-next series, the runtime PM core patch series,
> and a collection of hwmod fixes that Paul/Benoit have lined up
> for 2.6.37.
>
> Tested on OMAP2430, OMAP4430 (ES1.0 & ES2.0), OMAP3430 SDP boards
> and zoom3 board. Also verified that this patch series does not
> break the OMAP1 build.
I found a little snag with this series. Try testing with
omap2plus_defconfig and changing CONFIG_OMAP_WATCHDOG=n.
If CONFIG_OMAP_WATCHDOG is not enabled in the kernel config, the system
will reboot soon after bootup. One of the things the bootloader
historically has done was disable the watchdog so a driver wasn't needed.
With a reset of the IP triggered by the hwmod init, we lose this setting
and the watchog is armed by default.
I think we need to handle this case when CONFIG_OMAP_WATCHDOG=n in the
device init code by disabling the watchdog.
Kevin
> This series is tested on OMAP4430 ES2 using the below series
> (dependency series for ES2.0 silicon)
> http://www.spinics.net/lists/linux-omap/msg36023.html
>
> Version History:
> ---------------
> Version v8:
> *Enable wd_timer3 in the hwmod list
>
> Version v7:
> *Use EN_*SHIFT macros for module_bit and ST_*SHIFT macros for
> idlest_idle_bit in OMAP2&3 hwmod database
> (based on suggestions given by Paul for I2C hwmod series)
> *Remove new definitions of EN_*SHIFT macros as they already exist
> Some of the v7 links:
> https://patchwork.kernel.org/patch/197022/
>
> Version v6:
> *Split omap_init_wdt() into separate omap_init_wdt functions
> under mach-omap1 and mach-omap2 and set them up with
> subsys_initcall
> *Include wd_timer3 database for OMAP4
> *In hwmod database follow naming convention "wd_timerX"
> Some of the v6 links:
> http://www.spinics.net/lists/linux-omap/msg36678.html
> https://patchwork.kernel.org/patch/188242/
> https://patchwork.kernel.org/patch/188222/
>
> Version v5:
> *Delete wdt_runtime_resume and wdt_runtime_suspend
> functions as the fix for the return values in the generic
> runtime PM calls has been queued for 2.6.37 (see below link)
> https://lists.linux-foundation.org/pipermail/linux-pm/2010-September/028466.html
> Some of the v5 links:
> https://patchwork.kernel.org/patch/181812/
> https://patchwork.kernel.org/patch/181782/
> https://patchwork.kernel.org/patch/181772/
> https://patchwork.kernel.org/patch/181792/
>
> Version v4:
> *Implement hwmod adapdation first and then PM runtime adaptation
> as two different patches in the series
> *Remove inclusion of omap_device.h in the driver file.
> Some of the v4 links:
> https://patchwork.kernel.org/patch/174672/
> https://patchwork.kernel.org/patch/174662/
>
> Version v3:
> *Fix Minor comments like renaming omap1 watchdog structures
> with an omap1_ prefix
> Some of the v3 links:
> https://patchwork.kernel.org/patch/119698/
> https://patchwork.kernel.org/patch/119696/
>
> Version v2:
> *Rebase to latest kernel
> Some of the v2 links:
> http://www.spinics.net/lists/linux-omap/msg34741.html
> http://www.spinics.net/lists/linux-omap/msg34673.html
>
> Version v1:
> *Initial series
> Some of the v1 links:
> http://www.spinics.net/lists/linux-omap/msg30628.html
> http://www.spinics.net/lists/linux-omap/msg30625.html
>
> Benoit Cousson (1):
> OMAP4: hwmod data: Add watchdog timer
>
> Varadarajan, Charulatha (5):
> OMAP3: hwmod data: Add watchdog timer
> OMAP2420: hwmod data: Add watchdog timer
> OMAP2430: hwmod data: Add watchdog timer
> OMAP2PLUS: WDT: use omap_device_build for device registration
> OMAP: WDT: Use PM runtime APIs instead of clk FW APIs
>
> arch/arm/mach-omap1/devices.c | 27 ++++++
> arch/arm/mach-omap2/devices.c | 39 ++++++++
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 64 +++++++++++++
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 64 +++++++++++++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 66 ++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 135 ++++++++++++++++++++++++++++
> arch/arm/plat-omap/devices.c | 41 ---------
> drivers/watchdog/omap_wdt.c | 42 ++-------
> 8 files changed, 402 insertions(+), 76 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/6] OMAP: WDT: Implement WDT in hwmod way
Date: Tue, 28 Sep 2010 18:05:36 -0700 [thread overview]
Message-ID: <877hi5740v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285252363-3630-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 23 Sep 2010 20:02:37 +0530")
Hi Charu,
"Varadarajan, Charulatha" <charu@ti.com> writes:
> Series of patches to port watchdog module to use hwmod APIs
> for OMAP2PLUS chips and use runtime APIs for all OMAP chips.
> For this hwmod database for OMAP2PLUS watchdog instances are
> populated and implements watchdog module to use PM runtime APIs.
>
> This patch series is generated on "origin/pm-core" which
> has Kevin's pm-next series, the runtime PM core patch series,
> and a collection of hwmod fixes that Paul/Benoit have lined up
> for 2.6.37.
>
> Tested on OMAP2430, OMAP4430 (ES1.0 & ES2.0), OMAP3430 SDP boards
> and zoom3 board. Also verified that this patch series does not
> break the OMAP1 build.
I found a little snag with this series. Try testing with
omap2plus_defconfig and changing CONFIG_OMAP_WATCHDOG=n.
If CONFIG_OMAP_WATCHDOG is not enabled in the kernel config, the system
will reboot soon after bootup. One of the things the bootloader
historically has done was disable the watchdog so a driver wasn't needed.
With a reset of the IP triggered by the hwmod init, we lose this setting
and the watchog is armed by default.
I think we need to handle this case when CONFIG_OMAP_WATCHDOG=n in the
device init code by disabling the watchdog.
Kevin
> This series is tested on OMAP4430 ES2 using the below series
> (dependency series for ES2.0 silicon)
> http://www.spinics.net/lists/linux-omap/msg36023.html
>
> Version History:
> ---------------
> Version v8:
> *Enable wd_timer3 in the hwmod list
>
> Version v7:
> *Use EN_*SHIFT macros for module_bit and ST_*SHIFT macros for
> idlest_idle_bit in OMAP2&3 hwmod database
> (based on suggestions given by Paul for I2C hwmod series)
> *Remove new definitions of EN_*SHIFT macros as they already exist
> Some of the v7 links:
> https://patchwork.kernel.org/patch/197022/
>
> Version v6:
> *Split omap_init_wdt() into separate omap_init_wdt functions
> under mach-omap1 and mach-omap2 and set them up with
> subsys_initcall
> *Include wd_timer3 database for OMAP4
> *In hwmod database follow naming convention "wd_timerX"
> Some of the v6 links:
> http://www.spinics.net/lists/linux-omap/msg36678.html
> https://patchwork.kernel.org/patch/188242/
> https://patchwork.kernel.org/patch/188222/
>
> Version v5:
> *Delete wdt_runtime_resume and wdt_runtime_suspend
> functions as the fix for the return values in the generic
> runtime PM calls has been queued for 2.6.37 (see below link)
> https://lists.linux-foundation.org/pipermail/linux-pm/2010-September/028466.html
> Some of the v5 links:
> https://patchwork.kernel.org/patch/181812/
> https://patchwork.kernel.org/patch/181782/
> https://patchwork.kernel.org/patch/181772/
> https://patchwork.kernel.org/patch/181792/
>
> Version v4:
> *Implement hwmod adapdation first and then PM runtime adaptation
> as two different patches in the series
> *Remove inclusion of omap_device.h in the driver file.
> Some of the v4 links:
> https://patchwork.kernel.org/patch/174672/
> https://patchwork.kernel.org/patch/174662/
>
> Version v3:
> *Fix Minor comments like renaming omap1 watchdog structures
> with an omap1_ prefix
> Some of the v3 links:
> https://patchwork.kernel.org/patch/119698/
> https://patchwork.kernel.org/patch/119696/
>
> Version v2:
> *Rebase to latest kernel
> Some of the v2 links:
> http://www.spinics.net/lists/linux-omap/msg34741.html
> http://www.spinics.net/lists/linux-omap/msg34673.html
>
> Version v1:
> *Initial series
> Some of the v1 links:
> http://www.spinics.net/lists/linux-omap/msg30628.html
> http://www.spinics.net/lists/linux-omap/msg30625.html
>
> Benoit Cousson (1):
> OMAP4: hwmod data: Add watchdog timer
>
> Varadarajan, Charulatha (5):
> OMAP3: hwmod data: Add watchdog timer
> OMAP2420: hwmod data: Add watchdog timer
> OMAP2430: hwmod data: Add watchdog timer
> OMAP2PLUS: WDT: use omap_device_build for device registration
> OMAP: WDT: Use PM runtime APIs instead of clk FW APIs
>
> arch/arm/mach-omap1/devices.c | 27 ++++++
> arch/arm/mach-omap2/devices.c | 39 ++++++++
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 64 +++++++++++++
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 64 +++++++++++++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 66 ++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 135 ++++++++++++++++++++++++++++
> arch/arm/plat-omap/devices.c | 41 ---------
> drivers/watchdog/omap_wdt.c | 42 ++-------
> 8 files changed, 402 insertions(+), 76 deletions(-)
next prev parent reply other threads:[~2010-09-29 1:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 14:32 [PATCH v8 0/6] OMAP: WDT: Implement WDT in hwmod way Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-23 14:32 ` [PATCH v8 1/6] OMAP3: hwmod data: Add watchdog timer Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-23 14:32 ` [PATCH v8 2/6] OMAP2420: " Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-23 14:32 ` [PATCH v8 3/6] OMAP2430: " Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-23 15:25 ` Russell King - ARM Linux
2010-09-23 15:25 ` Russell King - ARM Linux
2010-09-23 17:07 ` Paul Walmsley
2010-09-23 17:07 ` Paul Walmsley
2010-09-23 14:32 ` [PATCH v8 4/6] OMAP4: " Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-23 14:32 ` [PATCH v8 5/6] OMAP: WDT: Split OMAP1 and OMAP2PLUS device registration Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-23 14:32 ` [PATCH v8 6/6] OMAP: WDT: Use PM runtime APIs instead of clk FW APIs Varadarajan, Charulatha
2010-09-23 14:32 ` Varadarajan, Charulatha
2010-09-29 1:05 ` Kevin Hilman [this message]
2010-09-29 1:05 ` [PATCH v8 0/6] OMAP: WDT: Implement WDT in hwmod way Kevin Hilman
2010-09-29 1:05 ` Kevin Hilman
2010-09-29 13:14 ` Varadarajan, Charulatha
2010-09-29 13:14 ` Varadarajan, Charulatha
2010-09-29 14:37 ` Kevin Hilman
2010-09-29 14:37 ` Kevin Hilman
2010-09-29 14:46 ` Varadarajan, Charulatha
2010-09-29 14:46 ` Varadarajan, Charulatha
2010-09-29 15:43 ` Kevin Hilman
2010-09-29 15:43 ` Kevin Hilman
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=877hi5740v.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.