From: Wolfgang Denk <wd@denx.de>
To: "Stephan Linke" <Stephan.Linke@epygi.de>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: parallel I/O ports & opend darin pins on MPC8xx
Date: Tue, 08 Jul 2003 23:36:57 +0200 [thread overview]
Message-ID: <20030708213702.030BEC6D82@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 08 Jul 2003 17:31:35 +0200." <FCEAKDJJAPHPLJFINDAJOEFEDEAA.Stephan.Linke@epygi.de>
Dear Stephan,
in message <FCEAKDJJAPHPLJFINDAJOEFEDEAA.Stephan.Linke@epygi.de> you 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
Please don't use such long lines, they are hard to read.
> 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.
This is a feature. It allows you to detect the the state of the pin
which can be pretty useful.
> Did anyone run into that problem in the past? What was your solution? Any thing else but NOT using open drain pins?
It is _not_ a problem, it is a feature, and a useful one.
Solution? What is so difficult about latching your output value in a
variable?
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
It is practically impossible to teach good programming style to stu-
dents that have had prior exposure to BASIC: as potential programmers
they are mentally mutilated beyond hope of regeneration. - Dijkstra
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-08 21:36 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
2003-07-08 21:36 ` Wolfgang Denk [this message]
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=20030708213702.030BEC6D82@atlas.denx.de \
--to=wd@denx.de \
--cc=Stephan.Linke@epygi.de \
--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).