public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: ep93xx: Disable TS-72xx watchdog before uncompressing
Date: Tue, 07 Feb 2017 16:05:08 +0100	[thread overview]
Message-ID: <2082981.zMc11d8l12@wuerfel> (raw)
In-Reply-To: <SN1PR0101MB1565DDD368EF9D0F9F9ACD9DD04C0@SN1PR0101MB1565.prod.exchangelabs.com>

On Thursday, February 2, 2017 8:43:52 PM CET Hartley Sweeten wrote:
> On Thursday, February 02, 2017 1:12 PM, 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.
> >
> > 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>
> > ---
> > Arnd, this is a recent, so you can queue this up, thanks!
> 
> Reviewed-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> 
> or Tested-by/Acked-by as appropriate...
> 

Too bad, this really gets in the way of a future multiplatform
ep93xx configuration as that doesn't easily allow us to have
board specific hacks in the decompressor.

Applied to next/soc with Hartley's reviewed-by tag.

It's not clear from your description if this is needed for stable
backports. If it is, please write to stable at vger.kernel.org
once it is merged upstream.

	Arnd

  reply	other threads:[~2017-02-07 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 20:12 [PATCH RESEND] ARM: ep93xx: Disable TS-72xx watchdog before uncompressing Florian Fainelli
2017-02-02 20:43 ` Hartley Sweeten
2017-02-07 15:05   ` Arnd Bergmann [this message]
2017-02-08 12:23 ` Afzal Mohammed
2017-02-13  3:38   ` Lokesh Vutla

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=2082981.zMc11d8l12@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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