From: Lokesh Vutla <lokeshvutla@ti.com>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: <arm@kernel.org>, <arnd@arndb.de>, <olof@lixom.net>,
<khilman@kernel.org>,
Hartley Sweeten <hsweeten@visionengravers.com>,
Ryan Mallon <rmallon@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"moderated list:ARM/CIRRUS LOGIC EP93XX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] ARM: ep93xx: Disable TS-72xx watchdog before uncompressing
Date: Mon, 13 Feb 2017 09:08:12 +0530 [thread overview]
Message-ID: <d7f36fd2-bc44-9339-d296-b3fc6dfb0531@ti.com> (raw)
In-Reply-To: <20170208122354.GA5912@afzalpc>
On Wednesday 08 February 2017 05:53 PM, Afzal Mohammed wrote:
> Hi,
>
> On Thu, Feb 02, 2017 at 12:12:26PM -0800, Florian Fainelli wrote:
>> The TS-72xx/73xx boards have a CPLD watchdog which is configured to
>> reset the board after 8 seconds, if the kernel is large enough that this
>> takes about this time to decompress the kernel, we will encounter a
>> spurious reboot.
>
> so once it reaches Kernel proper, that dog is being killed, right ?
>
> iirc, TI AM335x's & AM43x's ROM code too leaves the on-chip watchdog
> enabled & the bootloader disables it (else once it boots to prompt, it
> reboots always unless watchdog driver [if present] takes care of it),
> Lokesh, right ?
Yes, that's right. Watchdog is disabled in U-Boot.
Thanks and regards,
Lokesh
prev parent reply other threads:[~2017-02-13 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 20:12 Florian Fainelli
2017-02-02 20:43 ` Hartley Sweeten
2017-02-07 15:05 ` Arnd Bergmann
2017-02-08 12:23 ` Afzal Mohammed
2017-02-13 3:38 ` Lokesh Vutla [this message]
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=d7f36fd2-bc44-9339-d296-b3fc6dfb0531@ti.com \
--to=lokeshvutla@ti.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
--cc=rmallon@gmail.com \
/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
all inboxes | Powered by JetHome®