From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] fsl_qspi: Pet the watchdog while reading/writing
Date: Wed, 2 Dec 2015 09:49:14 -0800 [thread overview]
Message-ID: <565F2F1A.4070409@freescale.com> (raw)
In-Reply-To: <BN3PR0301MB08678AD934C426B186439334FE050@BN3PR0301MB0867.namprd03.prod.outlook.com>
On 11/24/2015 06:20 PM, Wang Huan-B18965 wrote:
>> On 11/23/2015 11:19 PM, Alexander Stein wrote:
>>> On Monday 23 November 2015 10:51:49, York Sun wrote:
>>>> On 11/04/2015 12:19 AM, Alexander Stein 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.
>>>>
>>>> Alexander,
>>>>
>>>> On which platform was this watchdog issue found?
>>>
>>> On a custom board based on LS1021A. The (GPIO based) watchdog timeout
>>> is about 1.5s
>>>
>>>
>> Thanks.
>>
>> Alison,
>>
>> Please test on your boards to see if you suffer the same. I wonder how
>> fast QSPI runs and why we didn't see this issue.
>>
> [Alison Wang] I didn't meet any issue when using sf commands to write and
> read the serial flash.
>
> Hi, Alexander,
>
> Could you show me the detail commands and process when you meet
> such issue? Then I can try to reproduce on my board.
>
Alison,
Were you able to reproduce it?
York
next prev parent reply other threads:[~2015-12-02 17:49 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 [this message]
2015-12-04 20:54 ` Fabio Estevam
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=565F2F1A.4070409@freescale.com \
--to=yorksun@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 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.