* bestcomm and i2c
@ 2004-07-05 21:23 iida
2004-07-05 21:59 ` Sylvain Munaut
0 siblings, 1 reply; 2+ messages in thread
From: iida @ 2004-07-05 21:23 UTC (permalink / raw)
To: linuxppc-embedded
I am to use the bestcomm API with 2.4.25 denx to control the i2c
Someone already used it ?
Could provide a example /
Thanks
Iida
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: bestcomm and i2c
2004-07-05 21:23 bestcomm and i2c iida
@ 2004-07-05 21:59 ` Sylvain Munaut
0 siblings, 0 replies; 2+ messages in thread
From: Sylvain Munaut @ 2004-07-05 21:59 UTC (permalink / raw)
To: iida; +Cc: linuxppc-embedded
iida wrote:
>
> I am to use the bestcomm API with 2.4.25 denx to control the i2c
Are you really sure you want to do that ?
Your peripheral really require such I2C bandwidth that you just can't
use the actual code ?
> Someone already used it ? Could provide a example /
Well, my last attempt was just to use interrupt to know when a
transfer was done instead of busy waiting. And I never got any
interrupts for the second I2C controller ( the one wired on the
lite5200 board ) unless I init both I2C controllers. I haven't yet
figured why ...
To get back at your original question, IIRC the BestCommAPI
package(Some big zip freescale will send you if you ask several times
;) ) has some code example of all devices, somewhere in a "validation"
directory. I can't send it, it's (c) Freescale.
Sylvain
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-07-05 21:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-05 21:23 bestcomm and i2c iida
2004-07-05 21:59 ` Sylvain Munaut
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).