From: Florian Fainelli <f.fainelli@gmail.com>
To: Hartley Sweeten <HartleyS@visionengravers.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
arm@kernel.org
Cc: Ryan Mallon <rmallon@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
olof@lixom.net, arnd@arndb.de, khilman@kernel.org
Subject: Re: [PATCH] ARM: ep93xx: Disable TS-72xx watchdog before uncompressing
Date: Thu, 19 Jan 2017 17:05:29 -0800 [thread overview]
Message-ID: <633e3405-c66d-0503-2626-36ebb0cfb756@gmail.com> (raw)
In-Reply-To: <SN1PR0101MB1565EBACEA749241E3FC3169D0910@SN1PR0101MB1565.prod.exchangelabs.com>
On 12/19/2016 08:08 AM, Hartley Sweeten wrote:
> On Sunday, December 18, 2016 7:08 PM, Florian Fainelli wrote:
>> Le 12/11/16 à 11:16, Florian Fainelli a écrit :
>>> 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.
>>>
>>> Do not pull ts72xx.h, but instead locally define what we need to disable
>>> the watchdog.
>>>
>>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>>
>> Hartley, Ryan, do you guys maintain a git tree with EP93xx patches, or
>> should I submit them through RMK's patch system once you are okay with them?
>
> Ryan has an old tree on github but it has not been updated since Oct 14, 2013. I'm
> not sure if he is doing any active development at this time.
>
> This patch will have to go through RMK's patch system or some other tree.
Olof, Arnd, Kevin, should I just resent this patch to arm@kernel.org for
you to pick it?
Thanks
--
Florian
next prev parent reply other threads:[~2017-01-20 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 19:16 Florian Fainelli
2016-12-19 2:08 ` Florian Fainelli
2016-12-19 16:08 ` Hartley Sweeten
2017-01-20 1:05 ` Florian Fainelli [this message]
2017-01-27 16:27 ` Arnd Bergmann
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=633e3405-c66d-0503-2626-36ebb0cfb756@gmail.com \
--to=f.fainelli@gmail.com \
--cc=HartleyS@visionengravers.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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®