linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Craig Hollabaugh <craig@hollabaugh.com>
To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: parallel I/O ports & opend darin pins on MPC8xx
Date: 08 Jul 2003 09:49:37 -0600	[thread overview]
Message-ID: <1057679377.870.18.camel@gibson> (raw)
In-Reply-To: <FCEAKDJJAPHPLJFINDAJOEFEDEAA.Stephan.Linke@epygi.de>


On Tue, 2003-07-08 at 09:31, Stephan Linke wrote:
> on one of our boards we are using one of the I/O pins in open drain mode. This leads to some problems in combination with other
> drivers that write to the ports data register. Since they can not detect the current output value of the open drain pin. They only
> see the status of the I/O pin no matter who forces the value the CPM or another device connected to the open drain pin. After
> writing back the value read from the I/O data register this value is forced by CPM which is normaly wrong.

Stephan,

What you are explaining, I beleive, is the reason why developers use
open drain in the first place. Multiple devices connected to control a
single signal giving bidirectional data flow.

>
> Did anyone run into that problem in the past? What was your solution? Any thing else but NOT using open drain pins?

Have you grepped the kernel source to find the other drivers affecting
that specific port control register? What did you look for and what did
you find?

Craig



>
--
------------------------------------------------------------
Dr. Craig Hollabaugh, craig@hollabaugh.com
Author of Embedded Linux: Hardware, Software and Interfacing
www.embeddedlinuxinterfacing.com


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

  reply	other threads:[~2003-07-08 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 15:31 parallel I/O ports & opend darin pins on MPC8xx Stephan Linke
2003-07-08 15:49 ` Craig Hollabaugh [this message]
2003-07-08 21:36 ` Wolfgang Denk
2003-07-09  4:57 ` None Atall
     [not found] <FCEAKDJJAPHPLJFINDAJCEGCDEAA.Stephan.Linke@epygi.de>
2003-07-09 10:24 ` Wolfgang Denk
     [not found] <FCEAKDJJAPHPLJFINDAJEEGGDEAA.Stephan.Linke@epygi.de>
2003-07-09 12:09 ` Wolfgang Denk
     [not found] <3F0C6C0C.8040306@earthlink.net>
2003-07-09 19:57 ` Wolfgang Denk
     [not found]   ` <3F0C7782.3060704@earthlink.net>
2003-07-09 20:17     ` Wolfgang Denk
2003-07-09 20:20     ` Dean Matsen

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=1057679377.870.18.camel@gibson \
    --to=craig@hollabaugh.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).