From: "Murali K. Vemuri" <murali-p1q9eIIu2y1Wk0Htik3J/w@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: i2c Issues
Date: Fri, 24 Dec 2010 20:23:23 +0900 [thread overview]
Message-ID: <002101cba35c$fba6ea50$f2f4bef0$@com> (raw)
Hi there,
I am working on OMAP 3530 , Linux Kernel version 2.6.32.
On OMAP I connected Audio Codec WM8993 as I2C (bus3) slave, with slave
address 0x1A.
I am able to initialize the I2C Bus correctly, and I successfully bound the
device to the driver. By adding a few debug messages, I get like this.
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400
kHz
i2c i2c-3: adapter [OMAP I2C adapter]
registered
i2c i2c-3: client [AK8859] registered with bus id
3-0044
i2c i2c-3: client [wm8993] registered with bus id 3-001a
This is what I exactly intend to happen. After this step, I get the
i2c_probe triggered into the device, and at that time, HW read fails,
constantly.
I checked the physical address that is being read from. This address is
correct as well.
Any pointers to how I can resolve this?
Thanks & regards
Murali
next reply other threads:[~2010-12-24 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 11:23 Murali K. Vemuri [this message]
2011-01-10 14:33 ` i2c Issues Jean Delvare
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='002101cba35c$fba6ea50$f2f4bef0$@com' \
--to=murali-p1q9eiiu2y1wk0htik3j/w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.