public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chris Packham <cp.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PPC] get_timer without CONFIG_INTERRUPTS
Date: Mon, 30 Sep 2013 21:22:01 +1300	[thread overview]
Message-ID: <524934A9.8000309@gmail.com> (raw)

Hi,

Has anyone looked at a way of implementing get_timer for PowerPC without
using interrupts.

We appear to be having a problem with common/usb_hub.c where
occasionally (1 in ~150 reboots) we seem to get stuck in the do/while
loop in usb_hub_configure. It looks like this should timeout but because
we don't define CONFIG_INTERRUPTS get_timer() will only ever return 0.

I'm being a little paranoid (perhaps too paranoid) about turning on
CONFIG_INTERRUPTS. Looking at the code I can't see too much that would
cause problems but I want to avoid a rogue LBC or PCI-e interrupt
locking up the CPU.

Thanks,
Chris

             reply	other threads:[~2013-09-30  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30  8:22 Chris Packham [this message]
2013-10-02  7:36 ` [U-Boot] [PPC] get_timer without CONFIG_INTERRUPTS Chris Packham
2013-10-02  9:01   ` Wolfgang Denk

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=524934A9.8000309@gmail.com \
    --to=cp.packham@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