From: Andre Heider <a.heider@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: bcm2835: fix mailbox timeout
Date: Mon, 16 Dec 2013 08:59:30 +0100 [thread overview]
Message-ID: <20131216075930.GA7085@localhost> (raw)
In-Reply-To: <1386992926-17895-1-git-send-email-swarren@wwwdotorg.org>
On Fri, Dec 13, 2013 at 08:48:46PM -0700, Stephen Warren wrote:
> My original intention was to have a 100ms timeout. However, the timer
> operations used return values in ms not us, so we ended up with a 100s
> timeout instead. Fixing this exposes that some operations need longer
> to operate than 100ms, so bump the timeout up to a whole second.
>
> Reported-by: Andre Heider <a.heider@gmail.com>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Andre Heider <a.heider@gmail.com>
Btw, the "get timing" mbox call I mentioned the other day is not what
I thought it is. I tried it and it doesn't describe how long the "power on"
call would take. I get "1" for every device except UART, for which 40000
was returned iirc.
Thanks,
Andre
prev parent reply other threads:[~2013-12-16 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 3:48 [U-Boot] [PATCH] ARM: bcm2835: fix mailbox timeout Stephen Warren
2013-12-16 7:59 ` Andre Heider [this message]
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=20131216075930.GA7085@localhost \
--to=a.heider@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox