Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upstream ofono d4 patches #722

Open
freemangordon opened this issue Feb 15, 2024 · 0 comments
Open

upstream ofono d4 patches #722

freemangordon opened this issue Feb 15, 2024 · 0 comments
Assignees

Comments

@freemangordon
Copy link

( 9,38,27) tmlind: freemangordon: i could never get the notifications to trigger on qmi, they seem to be forced to uart ts27.010 only
( 9,38,53) tmlind: sure if you figure out a way to make things work with qmi that would simplify things :)
( 9,39,51) tmlind: seems to be a modem firmware specific configuration
( 9,53,37) freemangordon: I see
( 9,54,33) tmlind: who knows, maybe the modem configuration could be updated with some commands
( 9,55,02) freemangordon: well, either ways we don;t have qmi calls working (in upstream)
( 9,55,10) freemangordon: so I will spend some time on it
( 9,56,12) tmlind: ok cool. so for now we've been mostly using qmi commands, and just kick the modem on uart pdu notifications so the qmimodem sees the event
( 9,56,18) tmlind: let me find the commit for you
( 9,57,38) freemangordon: tmlind: in the meanwhile https://git.kernel.org/pub/scm/network/ofono/ofono.git/commit/?id=8af8136f61742be963b67b88f18e85c12509e0f9, https://lore.kernel.org/all/[email protected]/ and https://lore.kernel.org/all/[email protected]/ :)
( 9,57,56) freemangordon: perhaps I should have cc-ed you
( 9,57,58) freemangordon: next time
( 9,58,58) freemangordon: I guess that should work on d4 as well
(10,01,18) tmlind: ok great
(10,01,39) tmlind: so for kicking the qmimodem on uart notifications, see mot_qmi_trigger_events()
(10,02,04) tmlind: ideally we'd find a way to re-route notifications back to the qmimodem by using some at or qmi commands..
(10,02,16) tmlind: and then plain qmimodem should just work
(10,02,28) freemangordon: and it lacks voice calls suppoer :D
(10,02,34) freemangordon: but, yeah, that's the plan
(10,03,15) freemangordon: will take a while though, I want to finish what I was doing initially before jumping to qmimodem (cpl phone applet)
(10,03,25) tmlind: and i think right now if a qmimodem data connection gets disconnected, qmimodem driver won't notice that and modem consumes extra 80 mW of power until the data connection is shut down
(10,04,00) freemangordon: and then will jump to d4 driver
(10,04,04) tmlind: so at least disconnect notification using mot_qmi_trigger_events() is currently missing and causing poor power consumption when moving around and getting disconnected by the cell network
(10,04,13) tmlind: ok
(10,04,16) freemangordon: oh
(10,04,29) freemangordon: ok, lets save that somewhere
(10,04,51) tmlind: yeah we get some 0 ending uart notfication, but should call mot_qmi_trigger_events()
(10,05,03) Pali left the room (quit: Ping timeout: 256 seconds).
(10,05,08) tmlind: so uart knows data got disconnected, qmimodem driver does not
(10,05,49) tmlind: probably easy to reproduce with some tin foil over the phone :)
(10,06,28) freemangordon: already did that when I was playing with signal strength iirc :)
(10,06,39) tmlind: hehe ok :)
(10,07,00) freemangordon: I think it is some 'enable event' command that's missing

@freemangordon freemangordon self-assigned this Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant