From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: mx5: Add support for USB armory board
Date: Tue, 17 Mar 2015 09:51:57 -0700 [thread overview]
Message-ID: <55085BAD.4020907@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5DGOmsGsHCYgnA9nwkwKXpSj-s--FfQZPi-XMW9DXGubg@mail.gmail.com>
Hi Fabio,
On 03/17/2015 09:30 AM, Fabio Estevam wrote:
> On Mon, Mar 16, 2015 at 1:50 PM, Chris Kuethe <chris.kuethe@gmail.com> wrote:
>
>> U-Boot 2015.04-rc3-00209-ga74ef40-dirty (Mar 15 2015 - 22:04:22)
>>
>> CPU: Freescale i.MX53 rev2.1 at 800 MHz
>> Reset cause: WDOG
>
> Here the reset cause is printed correctly.
>
>> Board: Inverse Path USB armory MkI
>> I2C: ready
>> DRAM: 512 MiB
>> MMC: FSL_SDHC: 0
>> In: serial
>> Out: serial
>> Err: serial
>> CPU: Freescale i.MX53 rev2.1 at 800 MHz
>> Reset cause: unknown reset
>
> ,but here it fails.
>
> Why does CPU version and reset cause are printed twice?
>
It appears that get_reset_cause() is being called twice,
and since it's destructive, the second will say "unknown reset".
This patch will fix the value of the return value:
http://patchwork.ozlabs.org/patch/439934/
> Is this happening with all mx53 boards or only with this one?
>
I have no idea about this, but there appear to be multiple
calls to print_cpuinfo().
Regards,
Eric
next prev parent reply other threads:[~2015-03-17 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 9:03 [U-Boot] [PATCH] arm: mx5: Add support for USB armory board andrej at inversepath.com
2015-03-05 19:06 ` Chris Kuethe
2015-03-16 16:50 ` Chris Kuethe
2015-03-17 5:27 ` Chris Kuethe
2015-03-17 16:30 ` Fabio Estevam
2015-03-17 16:49 ` Chris Kuethe
2015-03-17 16:51 ` Eric Nelson [this message]
2015-03-17 17:09 ` Stefano Babic
2015-03-17 17:27 ` Fabio Estevam
2015-03-18 23:00 ` Andrej Rosano
2015-03-19 16:55 ` [U-Boot] " Vagrant Cascadian
2015-03-19 17:03 ` Otavio Salvador
2015-03-19 19:18 ` Andrej Rosano
2015-03-21 15:12 ` Vagrant Cascadian
2015-03-24 13:32 ` Andrej Rosano
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=55085BAD.4020907@boundarydevices.com \
--to=eric.nelson@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox