All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: joakim.tjernlund@lumentis.se
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PWM on the MPC850
Date: Wed, 11 Dec 2002 15:54:24 +0100	[thread overview]
Message-ID: <20021211145429.18D5BC613A@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 11 Dec 2002 14:55:42 +0100." <IGEFJKJNHJDCBKALBJLLAELKFIAA.joakim.tjernlund@lumentis.se>


In message <IGEFJKJNHJDCBKALBJLLAELKFIAA.joakim.tjernlund@lumentis.se> you wrote:
>
> > But be warned: do NOT use any of the port B pins for I/O  in  such  a
> > setup. There is a race condition within all MPC8xx CPUs.
>
> hmm, we access a few port B I/O pins from user space. What/where is the
> race in kernel?

I should add that it is non-trivial to work around this issue. We had
a case where even the short spikes on the output caused by this  race
condition  were not acceptable. The only way to make this work was to
disable the PWM timers (and wait for them to shut  down  -  which  is
another  issue)  before moifying the port B data, and then start them
up again. Of course this is unacceptable when you need high precision
PWM signals (but the you would not use a MPC8xx RISC timer anyway).

My recommendation is: never, ever use the RISC timers if you need  to
know hwat's going on on port B.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"Free markets select for winning solutions."        - Eric S. Raymond

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-12-11 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <IGEFJKJNHJDCBKALBJLLAELKFIAA.joakim.tjernlund@lumentis.se>
2002-12-11 14:50 ` PWM on the MPC850 Wolfgang Denk
2002-12-11 14:54 ` Wolfgang Denk [this message]
2002-12-11 13:31 Donald MacArthur
2002-12-11 13:43 ` 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=20021211145429.18D5BC613A@atlas.denx.de \
    --to=wd@denx.de \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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.