All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] fsl_qspi: Pet the watchdog while reading/writing
Date: Fri, 4 Dec 2015 18:54:15 -0200	[thread overview]
Message-ID: <CAOMZO5AByJw9E73t83PcN8_K4hT1aSLe=Zv25v5ZrJ-BDHbUtg@mail.gmail.com> (raw)
In-Reply-To: <1446625150-5677-1-git-send-email-alexander.stein@systec-electronic.com>

On Wed, Nov 4, 2015 at 6:19 AM, Alexander Stein
<alexander.stein@systec-electronic.com> wrote:
> When reading a large blob. e.g. a linux kernel (several MiBs) a watchdog
> timeout might occur meanwhile. So pet the watchdog while operating on
> the flash.

I guess the same problem would occur when you do long file transfers
via TFTP, via USB, via eMMC, right?

Shouldn't you fix the watchdog timeout value instead? If I read this
thread correctly you set the watchdog timeout to be 1.5 s, which seems
to be too low.

Regards,

Fabio Estevam

  parent reply	other threads:[~2015-12-04 20:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04  8:19 [U-Boot] [PATCH 1/1] fsl_qspi: Pet the watchdog while reading/writing Alexander Stein
2015-11-23 18:51 ` York Sun
2015-11-24  7:19   ` Alexander Stein
2015-11-24 20:44     ` York Sun
2015-11-25  2:20       ` Huan Wang
2015-11-25  9:33         ` Alexander Stein
2015-12-03  9:49           ` Huan Wang
2015-12-03 10:04             ` Alexander Stein
2015-12-04  1:38               ` Huan Wang
2015-12-03 16:06             ` York Sun
2015-12-04  1:56               ` Huan Wang
2015-12-04 20:10                 ` York Sun
2015-12-07  6:39                   ` Alexander Stein
2015-12-02 17:49         ` York Sun
2015-12-04 20:54 ` Fabio Estevam [this message]
2015-12-04 21:00   ` York Sun
2015-12-07  6:35   ` Alexander Stein
2015-12-15  1:06 ` York Sun

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='CAOMZO5AByJw9E73t83PcN8_K4hT1aSLe=Zv25v5ZrJ-BDHbUtg@mail.gmail.com' \
    --to=festevam@gmail.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 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.