public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tabi Timur-B04825 <B04825@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2
Date: Thu, 3 Mar 2011 04:20:52 +0000	[thread overview]
Message-ID: <4D6F1723.4040205@freescale.com> (raw)
In-Reply-To: <45903308677306428B6EE7E6FF5A52040EDA82@039-SN1MPN1-004.039d.mgd.msft.net>

I don't think anyone here has ever turned on watchdog support on an 85xx board.  I think it works on 86xx boards, though.

Aggrwal Poonam-B10812 wrote:
> Hello Felix
>
> We have not used watchdog feature in u-boot as such.
>
> Timur, do you have any idea about this? Can you give some pointers here.
>
> I will also try to explore it more.
>
> Regards
> Poonam
>
>> -----Original Message-----
>> From: Felix Radensky [mailto:felix at embedded-sol.com]
>> Sent: Thursday, March 03, 2011 5:41 AM
>> To: U-Boot-Denx; Kumar Gala; Aggrwal Poonam-B10812
>> Subject: CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2
>>
>> Hi,
>>
>> I'm trying to enable watchdog in u-boot on P1011 based platform.
>> I've noticed that all 85XX platforms have CONFIG_WATCHDOG disabled.
>> There's a definition of reset_85xx_watchdog() in cpu/mpc85xx/cpu.c but no
>> code that actually enables the watchdog.
>>
>> What should be done to make this feature working on these platforms ?
>>
>> Thanks a lot.
>>
>> Felix.
>>
>>
>>
>>
>


-- 
Timur Tabi
Linux kernel developer

  reply	other threads:[~2011-03-03  4:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  0:10 [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2 Felix Radensky
2011-03-03  4:18 ` Aggrwal Poonam-B10812
2011-03-03  4:20   ` Tabi Timur-B04825 [this message]
2011-03-03  4:27     ` Dudhat Dipen-B09055
2011-03-03  7:41       ` Felix Radensky
2011-03-03  7:49         ` Albert ARIBAUD
2011-03-03 12:33         ` Tabi Timur-B04825
2011-03-03 13:08           ` Felix Radensky
2011-03-03 13:11             ` Tabi Timur-B04825
2011-03-07  9:38               ` Felix Radensky

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=4D6F1723.4040205@freescale.com \
    --to=b04825@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox