From: Peter Korsgaard <jacmet@sunsite.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] soft_i2c/i2c_probe(): Perform reads instead of writes
Date: Sat, 11 Jun 2005 16:41:43 +0200 [thread overview]
Message-ID: <87hdg5c5w8.fsf@p4.48ers.dk> (raw)
In-Reply-To: <42964F22.60600@orkun.us> (Tolunay Orkun's message of "Thu, 26 May 2005 17:35:14 -0500")
>>>>> "Tolunay" == Tolunay Orkun <listmember@orkun.us> writes:
Hi, and sorry for the slow response!
Tolunay> Peter, I believe the implementation was correct but the
Tolunay> comment was wrong. It should be a write transaction with
Tolunay> just address byte. After the address byte is transmitted the
Tolunay> I2C slave will acknowledge (if present) and we finish the
Tolunay> transaction by generating the stop condition. i.e. fake
Tolunay> write.
Why write? Wouldn't a zero byte read transaction be safer?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2005-06-11 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 20:06 [U-Boot-Users] [PATCH] soft_i2c/i2c_probe(): Perform reads instead of writes Peter Korsgaard
2005-05-26 22:35 ` Tolunay Orkun
2005-06-11 14:41 ` Peter Korsgaard [this message]
2005-06-14 21:34 ` Tolunay Orkun
2005-06-15 3:16 ` Eugene Surovegin
2005-06-15 6:25 ` Peter Korsgaard
2006-03-12 0:31 ` 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=87hdg5c5w8.fsf@p4.48ers.dk \
--to=jacmet@sunsite.dk \
--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