* i2c Issues
@ 2010-12-24 11:23 Murali K. Vemuri
2011-01-10 14:33 ` Jean Delvare
0 siblings, 1 reply; 2+ messages in thread
From: Murali K. Vemuri @ 2010-12-24 11:23 UTC (permalink / raw)
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: i2c Issues
2010-12-24 11:23 i2c Issues Murali K. Vemuri
@ 2011-01-10 14:33 ` Jean Delvare
0 siblings, 0 replies; 2+ messages in thread
From: Jean Delvare @ 2011-01-10 14:33 UTC (permalink / raw)
To: murali-p1q9eIIu2y1Wk0Htik3J/w; +Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA
On Fri, 24 Dec 2010 20:23:23 +0900, Murali K. Vemuri wrote:
> 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?
Check with i2cdetect and then i2cdump if you can talk to the device in
question from user-space (using the i2c-dev driver). If you can't, it's
a hardware issue. If you can, it's a driver issue.
--
Jean Delvare
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-01-10 14:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-24 11:23 i2c Issues Murali K. Vemuri
2011-01-10 14:33 ` Jean Delvare
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).