Thread: Accessory port
View Single Post
Old 07-30-2012, 09:44 AM   #14
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by mmatej View Post
Can you tell me a reference to the code file where is it being controlled? I think for the real data output it would be necessary to implement data sending code in the kernel, because small delays would seriously damage output too, if one wanted to get high transfer rates.
Also, there are 5 ticks per second, not tick every 5 seconds.
I searched the code for "ACCESSORY". It was found in a bunch of source modules. Most of it was mixed into USB code, and it controlled a voltage regulator ("Apollo" device?). It was not clear that this was the accessory port for LED reading lights. To see what I saw, just search the source code for "accessory" (without case matching).

Last edited by geekmaster; 07-30-2012 at 10:05 AM.
geekmaster is offline   Reply With Quote