From: Wolfgang Denk <wd@denx.de>
To: Miku Jha <jha_miku@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc440 and i2c
Date: Tue, 18 Nov 2003 09:09:02 +0100 [thread overview]
Message-ID: <20031118080907.7438BC5F59@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 17 Nov 2003 23:18:29 PST." <20031118071829.43116.qmail@web40301.mail.yahoo.com>
In message <20031118071829.43116.qmail@web40301.mail.yahoo.com> you wrote:
>
> I am running ppc440 with linux kernel version 2.4
Grrrghh... You sent the same message twice to the (dead)
PPCBoot-Users list and another time to linuxppc-embedded???
Grrrrghhh!!!! Please fix your posting habits.
> >From the i2c bus trace it looks like in this
> situation ppc440 keeps issuing the clock pulses
> until the data line SDL is released by the slave
> but following that the SCL line is held low
> by ppc440 and is never released or set to IDLE?
>
> Is this the expected behaviour if the SDL is held
> low when the ppc440 comes up.
This is an expected and documented problem. See "doc/I2C_Edge_Conditions" in
the U-Boot / PPCBoot sources.
> Is there anyway I can fix this in the ppcboot code.
Yes. You could back-port the fixes that went into U-Boot. But it
probably makes more sense to switch to U-Boot instead.
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
A meeting is an event at which the minutes are kept and the hours are
lost.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-11-18 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 7:18 ppc440 and i2c Miku Jha
2003-11-18 8:08 ` Eugene Surovegin
2003-11-18 8:22 ` Wolfgang Denk
2003-11-18 8:42 ` Eugene Surovegin
2003-11-18 8:55 ` Robert Berger
2003-11-18 8:09 ` Wolfgang Denk [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=20031118080907.7438BC5F59@atlas.denx.de \
--to=wd@denx.de \
--cc=jha_miku@yahoo.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 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.