[linux-dvb] i2c problems

[Marlec Olivier <marleco@thmulti.com>]

Here are the kernel messages I have with the last CVS driver :
	
	...
DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 00012502
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_reset: busy_state detected
saa7146: ==> i2c_status_check:0x00000142
saa7146: i2c_reset: error_state detected, status:0x00000142
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_reset: busy_state detected
saa7146: ==> i2c_status_check:0x00000142
saa7146: i2c_reset: error_state detected, status:0x00000142
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_reset: busy_state detected
saa7146: ==> i2c_status_check:0x00000142
saa7146: i2c_reset: error_state detected, status:0x00000142
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_reset: busy_state detected
saa7146: ==> i2c_status_check:0x00000142
saa7146: i2c_reset: error_state detected, status:0x00000142
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_reset: busy_state detected
saa7146: ==> i2c_status_check:0x00000142
saa7146: i2c_reset: error_state detected, status:0x00000142
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
saa7146_core.o: master_xfer called, num:1
saa7146: ==> i2c_reset
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_reset: busy_state detected
saa7146: ==> i2c_status_check:0x00000142
saa7146: i2c_reset: error_state detected, status:0x00000142
saa7146: ==> i2c_status_check:0x00000100
saa7146: ==> writeout: 0x200000e4 (before) (to:100)
saa7146: ==> i2c_busy_rise_and_fall
saa7146: i2c_busy_rise_and_fall; rise wait 5
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall; fall wait 100
saa7146: ==> i2c_status_check:0x00000123
saa7146: i2c_busy_rise_and_fall: error in address phase
saa7146: i2c_write_out; error in address phase
saa7146_core.o: i2c error in address phase
		...

Does anybody know this problem ?


Olivier Marlec 
Research & Innovation
Corporate Research Rennes
Multimedia Streaming & Storage Lab
mailto:olivier.marlec@thomson.net
phone :(33)(0)2.99.27.33.64
fax: (33)(0)2.99.27.30.15




-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.