All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zumeng Chen <zumeng.chen@windriver.com>
To: shubhrajyoti@ti.com, hvaibhav@ti.com, wim@iguana.be, "Hilman,
	Kevin" <khilman@ti.com>
Cc: linux-watchdog@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	paul.gortmaker@windriver.com, tony@atomide.com
Subject: Re: [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework
Date: Wed, 11 Jul 2012 16:10:12 +0800	[thread overview]
Message-ID: <4FFD34E4.7060505@windriver.com> (raw)
In-Reply-To: <4FFBACE4.80901@windriver.com>

The same case works well on am335xevm but with a new patch in
mach-omap2/prcm.c

I'll send it later.

root@ti-omap3:~# uname -a
Linux ti-omap3 3.4.3-00635-g82d1d26-dirty #32 Wed Jul 11 16:02:12 CST
2012 armv7l GNU/Linux
root@ti-omap3:~# dmesg|grep WDT
[ 1.921173] omap_wdt: OMAP WDTimer Rev 0x01: Initial timeout 0sec
status= 0x1
root@ti-omap3:~# ./a.out -i 20; for i in `seq 1 20`; do echo $i ; sleep
1;done
Set watchdog interval to 20
Current watchdog interval is 20
Last boot is caused by : Watchdog
Use:
<w> to kick through writing over device file
<i> to kick through IOCTL
<x> to exit the program
x

1
2
[snip]
U-Boot SPL 2011.09 (Feb 09 2012 - 15:38:59)
Texas Instruments Revision detection unimplemented


U-Boot 2011.09 (Feb 09 2012 - 15:11:31)

I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
Found a daughter card connected
NAND: HW ECC Hamming Code selected
256 MiB
MMC: OMAP SD/MMC: 0
Net: cpsw
Hit any key to stop autoboot: 0
U-Boot#

Regards,
Zumeng

于 2012年07月10日 12:17, Zumeng Chen 写道:
> 于 2012年07月09日 15:35, Zumeng Chen 写道:
>> 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.
> I compiled a test case from the following website,
> http://www.lpclinux.com/Blogs/Testing_LPC313x_Linux_Watchdog_Driver
>
> It works well.
>
> root@ti-omap3:/tmp# ./a.out -h
> Usage: ./a.out [options]
> -h --help Display this usage information.
> -d --dev <device_file> Use <device_file> as watchdog device file.
> The default device file is '/dev/watchdog'
> -i --interval <interval> Change the watchdog interval time
> root@ti-omap3:/tmp# ./a.out -i 40;
> Set watchdog interval to 40
> Current watchdog interval is 40
> Last boot is caused by : Watchdog
> Use:
> <w> to kick through writing over device file
> <i> to kick through IOCTL
> <x> to exit the program
> x
> Goodbye !
> watchdog: Omap Watchdog: nowayout prevents watchdog to be stopped!
> watchdog: Omap Watchdog: watchdog did not stop!
> root@ti-omap3:/tmp# for i in `seq 1 30`; do echo $i; sleep 1;done
> 1
> 2
>
> [snip]
>
> I built NOWAYOUT in driver, so it doesn't stop, still going until the
> following
> information:
>
> Texas Instruments X-Loader 1.42
> Starting OS Bootloader...
> No OOB scheme defined for oobsize 0
> OneNAND: 0 kB
> 256 MiB
>
> Regards,
> Zumeng
>> 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 OMAP2Plus
>>
>>  arch/arm/mach-omap2/prcm.c  |    5 +-
>>  drivers/watchdog/Kconfig    |    1 +
>>  drivers/watchdog/omap_wdt.c |  342 ++++++++++++++++---------------------------
>>  drivers/watchdog/omap_wdt.h |    5 +
>>  4 files changed, 133 insertions(+), 220 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 <zumeng.chen@windriver.com>
To: <shubhrajyoti@ti.com>, <hvaibhav@ti.com>, <wim@iguana.be>,
	"Hilman, Kevin" <khilman@ti.com>
Cc: <linux-watchdog@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<paul.gortmaker@windriver.com>, <tony@atomide.com>
Subject: Re: [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework
Date: Wed, 11 Jul 2012 16:10:12 +0800	[thread overview]
Message-ID: <4FFD34E4.7060505@windriver.com> (raw)
In-Reply-To: <4FFBACE4.80901@windriver.com>

The same case works well on am335xevm but with a new patch in
mach-omap2/prcm.c

I'll send it later.

root@ti-omap3:~# uname -a
Linux ti-omap3 3.4.3-00635-g82d1d26-dirty #32 Wed Jul 11 16:02:12 CST
2012 armv7l GNU/Linux
root@ti-omap3:~# dmesg|grep WDT
[ 1.921173] omap_wdt: OMAP WDTimer Rev 0x01: Initial timeout 0sec
status= 0x1
root@ti-omap3:~# ./a.out -i 20; for i in `seq 1 20`; do echo $i ; sleep
1;done
Set watchdog interval to 20
Current watchdog interval is 20
Last boot is caused by : Watchdog
Use:
<w> to kick through writing over device file
<i> to kick through IOCTL
<x> to exit the program
x

1
2
[snip]
U-Boot SPL 2011.09 (Feb 09 2012 - 15:38:59)
Texas Instruments Revision detection unimplemented


U-Boot 2011.09 (Feb 09 2012 - 15:11:31)

I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
Found a daughter card connected
NAND: HW ECC Hamming Code selected
256 MiB
MMC: OMAP SD/MMC: 0
Net: cpsw
Hit any key to stop autoboot: 0
U-Boot#

Regards,
Zumeng

于 2012年07月10日 12:17, Zumeng Chen 写道:
> 于 2012年07月09日 15:35, Zumeng Chen 写道:
>> 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.
> I compiled a test case from the following website,
> http://www.lpclinux.com/Blogs/Testing_LPC313x_Linux_Watchdog_Driver
>
> It works well.
>
> root@ti-omap3:/tmp# ./a.out -h
> Usage: ./a.out [options]
> -h --help Display this usage information.
> -d --dev <device_file> Use <device_file> as watchdog device file.
> The default device file is '/dev/watchdog'
> -i --interval <interval> Change the watchdog interval time
> root@ti-omap3:/tmp# ./a.out -i 40;
> Set watchdog interval to 40
> Current watchdog interval is 40
> Last boot is caused by : Watchdog
> Use:
> <w> to kick through writing over device file
> <i> to kick through IOCTL
> <x> to exit the program
> x
> Goodbye !
> watchdog: Omap Watchdog: nowayout prevents watchdog to be stopped!
> watchdog: Omap Watchdog: watchdog did not stop!
> root@ti-omap3:/tmp# for i in `seq 1 30`; do echo $i; sleep 1;done
> 1
> 2
>
> [snip]
>
> I built NOWAYOUT in driver, so it doesn't stop, still going until the
> following
> information:
>
> Texas Instruments X-Loader 1.42
> Starting OS Bootloader...
> No OOB scheme defined for oobsize 0
> OneNAND: 0 kB
> 256 MiB
>
> Regards,
> Zumeng
>> 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 OMAP2Plus
>>
>>  arch/arm/mach-omap2/prcm.c  |    5 +-
>>  drivers/watchdog/Kconfig    |    1 +
>>  drivers/watchdog/omap_wdt.c |  342 ++++++++++++++++---------------------------
>>  drivers/watchdog/omap_wdt.h |    5 +
>>  4 files changed, 133 insertions(+), 220 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@windriver.com (Zumeng Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework
Date: Wed, 11 Jul 2012 16:10:12 +0800	[thread overview]
Message-ID: <4FFD34E4.7060505@windriver.com> (raw)
In-Reply-To: <4FFBACE4.80901@windriver.com>

The same case works well on am335xevm but with a new patch in
mach-omap2/prcm.c

I'll send it later.

root at ti-omap3:~# uname -a
Linux ti-omap3 3.4.3-00635-g82d1d26-dirty #32 Wed Jul 11 16:02:12 CST
2012 armv7l GNU/Linux
root at ti-omap3:~# dmesg|grep WDT
[ 1.921173] omap_wdt: OMAP WDTimer Rev 0x01: Initial timeout 0sec
status= 0x1
root at ti-omap3:~# ./a.out -i 20; for i in `seq 1 20`; do echo $i ; sleep
1;done
Set watchdog interval to 20
Current watchdog interval is 20
Last boot is caused by : Watchdog
Use:
<w> to kick through writing over device file
<i> to kick through IOCTL
<x> to exit the program
x

1
2
[snip]
U-Boot SPL 2011.09 (Feb 09 2012 - 15:38:59)
Texas Instruments Revision detection unimplemented


U-Boot 2011.09 (Feb 09 2012 - 15:11:31)

I2C: ready
DRAM: 256 MiB
WARNING: Caches not enabled
Found a daughter card connected
NAND: HW ECC Hamming Code selected
256 MiB
MMC: OMAP SD/MMC: 0
Net: cpsw
Hit any key to stop autoboot: 0
U-Boot#

Regards,
Zumeng

? 2012?07?10? 12:17, Zumeng Chen ??:
> ? 2012?07?09? 15:35, Zumeng Chen ??:
>> 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.
> I compiled a test case from the following website,
> http://www.lpclinux.com/Blogs/Testing_LPC313x_Linux_Watchdog_Driver
>
> It works well.
>
> root at ti-omap3:/tmp# ./a.out -h
> Usage: ./a.out [options]
> -h --help Display this usage information.
> -d --dev <device_file> Use <device_file> as watchdog device file.
> The default device file is '/dev/watchdog'
> -i --interval <interval> Change the watchdog interval time
> root at ti-omap3:/tmp# ./a.out -i 40;
> Set watchdog interval to 40
> Current watchdog interval is 40
> Last boot is caused by : Watchdog
> Use:
> <w> to kick through writing over device file
> <i> to kick through IOCTL
> <x> to exit the program
> x
> Goodbye !
> watchdog: Omap Watchdog: nowayout prevents watchdog to be stopped!
> watchdog: Omap Watchdog: watchdog did not stop!
> root at ti-omap3:/tmp# for i in `seq 1 30`; do echo $i; sleep 1;done
> 1
> 2
>
> [snip]
>
> I built NOWAYOUT in driver, so it doesn't stop, still going until the
> following
> information:
>
> Texas Instruments X-Loader 1.42
> Starting OS Bootloader...
> No OOB scheme defined for oobsize 0
> OneNAND: 0 kB
> 256 MiB
>
> Regards,
> Zumeng
>> 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 OMAP2Plus
>>
>>  arch/arm/mach-omap2/prcm.c  |    5 +-
>>  drivers/watchdog/Kconfig    |    1 +
>>  drivers/watchdog/omap_wdt.c |  342 ++++++++++++++++---------------------------
>>  drivers/watchdog/omap_wdt.h |    5 +
>>  4 files changed, 133 insertions(+), 220 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

  reply	other threads:[~2012-07-11  8:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  7:35 [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework Zumeng Chen
2012-07-09  7:35 ` Zumeng Chen
2012-07-09  7:35 ` Zumeng Chen
2012-07-09  7:35 ` [PATCH v2 1/3] Watchdog: Omap: Changes for the new " Zumeng Chen
2012-07-09  7:35   ` Zumeng Chen
2012-07-09  7:35   ` Zumeng Chen
2012-07-09  7:35 ` [PATCH v2 2/3] Watchdog: Omap: select watchdog core for framework change Zumeng Chen
2012-07-09  7:35   ` Zumeng Chen
2012-07-09  7:35   ` Zumeng Chen
2012-07-09  7:35 ` [PATCH v2 3/3] Watchdog: Omap: get the bootstatus for OMAP2Plus Zumeng Chen
2012-07-09  7:35   ` Zumeng Chen
2012-07-09  7:35   ` Zumeng Chen
2012-07-10  4:17 ` [PATCH v2 RESEND 0/3] Watchdog: OMAP: bootstatus fix for omap3 and changes for the current watchdog framework Zumeng Chen
2012-07-10  4:17   ` Zumeng Chen
2012-07-10  4:17   ` Zumeng Chen
2012-07-11  8:10   ` Zumeng Chen [this message]
2012-07-11  8:10     ` Zumeng Chen
2012-07-11  8:10     ` 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=4FFD34E4.7060505@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.