logo       

pulse/space length detection: msg#00078

hardware.lirc

Subject: pulse/space length detection

Hi,

I just ran into trouble with lirc on a new charge of mainboards I got.
Everything works fine, until the system goes to suspend to ram-mode. When it
comes back and I reload the lirc_serial module, I still get data, which I can
see with mode2. But the pulse- and space-length are not recognized correctly
anymore. Some are too long and some too short. This makes the succesfull
decoding impossible.
Now I'm thinking about what could be the reason for it (we have several of
these Mainboards, one charge earlier, but with the same bios, that work
pefectly after suspend).
Therefore I need to know how the length-detection works. Is it just like this:
Everytime an interrupt on the data-pin occurs a counter is started, which is
incremented by every system-clock-event, when the next interrupt occurs the
value of the counter is checked and translated into a us timevalue.
Is that correct?

If it is I could imagine two reasons for the problem: Either the interrupt is
not driven correctly after suspend or the system-clock does not work properly
after suspend.

Maybe someone else has some further thoughts on this topic?

Cheers,
Julian


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise