Hi everyone,
I have a doubt about the logic of implementation for the reference-ril.c of the Android telephony stack.
In particular, the mainloop() function seems to be running forever to keep the port of communication with the baseband opened (codeline 3291 at https://github.com/android/platform_...eference-ril.c). There is indeed a for( ; ; ) loop that seems not having beaks, so I assume it runs forever (correct me if I am wrong). However, in theory the communications between the baseband and the application processor where android and reference-ril are running should be interrupt based. This means that when the baseband needs to communicate something, an interrupt is raised.
Why android does not wake up the mainloop() function only when this interrupt is raised rather than keeping the port always open?
Could be something related to the fact the the port of communication is USB (HSIC) based?
Thanks for any help in clarifying this doubt!
I have a doubt about the logic of implementation for the reference-ril.c of the Android telephony stack.
In particular, the mainloop() function seems to be running forever to keep the port of communication with the baseband opened (codeline 3291 at https://github.com/android/platform_...eference-ril.c). There is indeed a for( ; ; ) loop that seems not having beaks, so I assume it runs forever (correct me if I am wrong). However, in theory the communications between the baseband and the application processor where android and reference-ril are running should be interrupt based. This means that when the baseband needs to communicate something, an interrupt is raised.
Why android does not wake up the mainloop() function only when this interrupt is raised rather than keeping the port always open?
Could be something related to the fact the the port of communication is USB (HSIC) based?
Thanks for any help in clarifying this doubt!
Aucun commentaire:
Enregistrer un commentaire